LibreWolf: Failing to open links

xjdwc

Hi all

I need help with the following:

I use the AppImage version of LibreWolf as my default web browser on plasma.
The browser works fine, except for in one area.

When I try to open links that are outside of the browser, e.g. within native applications, other AppImages etc.
Clicking on a link triggers LibreWolf to open and display the site, but instead of it being the working webpage it displays an offline/static/dead end page (not sure how to describe it).

Loads the site but not the full version. Content seems to be relevant and even up to date in most cases, but links are broken for the most part, but some links will open to a working webpage.

I've noticed the address bar doesn't have the correct url displayed, it will be something like this:
file:///home/user/.cache/kioexec/krun/numbers/unnamed

Here is a screenshot of an attempt to open this forum from a link located on Element (Native Application)

Any help is appreciated 🙂

pomon

Show which browser is the default xdg-mime query default x-scheme-handler/https
Show which browser is on file ~/.config/mimeapps.list. If other than LibreWolf then change to /path/to/LibreWolf.appimage

xjdwc

pomon

After entering the command xdg-mime query default x-scheme-handler/https the result is:

LibreWolf.desktop

Upon checking the document mimeapps.list the Default Applications section with all x-scheme-handler http/https related lines were already set to:

LibreWolf.desktop;

With some also showing both LibreWolf.desktop and firefox.desktop
Firefox entries since deleted. After following your instructions, I tested some links and still have the same issue.

Not sure what it could be.... Is it an AppImage limitation? Is it a security feature of LibreWolf? Some setting I am missing?

Either way, thanks for your input, I appreciate it. If you have any other ideas, feel free to send them my way.

🙂

brent

xjdwc I've seen this solus forum screen before in Libre but I've refrained from comment. It was in the Flatpak. Over a year ago when I spent a month with LW (before learning I could make regular FF more hardened than LW).
Digital memory after a year for me is fuzzy...but it was the only browser that did that. It wasn't because of the plugins, I tried. It was something they did in about:config as I remember it. Something to do with dom.
I didn't really spend a lot of time (usually I do) making Forum work because I simply viewed it from another browser.

long story short: it's a nifty browser. keep using it. read solus from another one.

pomon

xjdwc I tested some links and still have the same issue.

Can you show the apps that are causing the error? I will check at my place.

xjdwc

pomon

That's the thing, all apps, whether, preinstalled, native, AppImage etc. Any application that has a link to a webpage results in the site not being loaded correctly. LibreWolf triggers as it should but the page isn't loaded correctly, it is more a document/offline/static/dead end page.

brent

To clarify. The browser functions as normal. Works fine. I don't have any issues with the browser if I launch it as normal. My issue is when I try to open links outside of LibreWolf, e.g. another application (Element, RSS Reader etc), it will trigger the browser to load the requested webpage but it fails to do so correctly, giving me the weird file/text/offline version.

A minor hiccup, and to be honest I can ignore the issue, but was just hoping there was a fix for it. But I appreciate the input regardless 🙂

Axios

If you have to use libre use the flatpak and Open Flatseal, sellect Librewolf and setting the D-Bus session bus to true
See if this works for you.
I think its just that dreaded sandbox That (Brent knows all to well to) its loading from cache instead of
communicating properly.
From what i can tell v96.0.1-1 they should have fixed it (I would try flatpak first if that doesnt work do the flatseal)
But with appimage its prob a no go
(Above reference is to Flatpak only)

pomon

With me, LibreWolf.appimage opens links from element. thunderbird, discord correctly. All installed from the repo.

Axios

I would think they would i downloaded the appimage from librewolf but havent tested it yet havent had time
External apps is broad statement.
LIke I said they said they fixed it back on release 96 and at 112 or something. (So it was a known issue to them at the time and that was from there webpage)
It was just something to try and if it worked thats the issue can speculate all day
Its good to know it works for you so we know its poss.

xjdwc

That's helpful to know that it does work on your system.
I'll stick with the AppImage and if it doesn't magically fix itself through updates etc, then I'll just live with it until I do a clean install in the distant future. Pretty minor in the grand scheme of things.

Thanks for the input everyone 🙂