Firefox launched from X11 app cant be used for links from Wayland app, and vice versa
Categories
(Core :: Widget: Gtk, defect)
Tracking
()
People
(Reporter: el, Unassigned)
References
Details
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:123.0) Gecko/20100101 Firefox/123.0
Steps to reproduce:
Firefox Developer Edition as a portable official mozilla build, when launched initially via clicking a link from an X11 app, cant be used for links from Wayland app where instead the "firefox is already running" popup shows up instead. The same applies the other way around. It also seems to cause faulty messages that firefox was supposedly upgraded in the background and has to be restarted, when I'm fairly certain no upgrade happened.
Actual results:
- Use GNOME 3 Wayland session
- Start Firefox Developer Edition via official mozilla portable build for x64 extracted in some subfolder in your user home, and make it the standard browser such that it will be launched for links opened through xdg-open etc.
- Terminate all firefox processes
- Start both one app that you know uses Wayland natively, and another one you know only uses X11 and will use XWayland.
- Click a link in one of the apps and wait until firefox is started. Then click a link in the other app.
Expected results:
opening the links keeps working in both. it shouldn't matter whether it was opened from an X11 or Wayland app. in practice, instead it seems to cause some weird broken separation of universes where in half of the apps links won't quite work right as a result.
|
||
Comment 1•1 year ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Widget: Gtk' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
|
||
Comment 2•1 year ago
|
||
Thanks for the report!
A workaround is adding export MOZ_DBUS_REMOTE=1 to ~/.bashrc:
https://mastransky.wordpress.com/2020/03/16/wayland-x11-how-to-run-firefox-in-mixed-environment/
Wouldn't it make more sense to make firefox behave like that by default? Or what's the reason that's not the case? Sorry if that's a naive question.
Actually, it seems like my .bashrc already contains that line! I just checked.
|
|
||
Updated•1 year ago
|
|
|
||
Updated•1 year ago
|
I wonder, is there some way the .bashrc maybe sometimes doesn't get applied? E.g. when the links are clicked from inside a flatpak app, although I use firefox just as a regular portable binary sitting in my home dir without flatpak? I could try /etc/environment and see if that helps. Or otherwise I'm not sure what the culprit could be, it feels a bit like #1508803 is the same problem but I suppose I wouldn't really know!
Description
•