firefox becomes unusable after adding an external monitor (linux, gnome x11)
Categories
(Core :: Widget: Gtk, defect, P3)
Tracking
()
People
(Reporter: serge, Unassigned, NeedInfo)
Details
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:88.0) Gecko/20100101 Firefox/88.0
Steps to reproduce:
OS: Ubuntu 18.04, Gnome X11
I use firefox on laptop (Lenovo X1 Yoga 2nd gen). When
- I start firefox under Gnome X11 session without an external monitor plugged in
- add external monitor after
Actual results:
Firefox almost freezes (not completely, but it becomes VERY slow and do not render webpages or at least redraw any content). The menus are also very slow and broken.
The only possible way to continue the work with firefox is to restart firefox.
If I add external monitor and start firefox after, I can dicsconnect and again connect the external monitor later and firefox works in a correct way.
The problem is reproducible with and without hardware acceleration enabled.
Expected results:
Firefox should continue work flawlessly.
|
||
Comment 1•4 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Widget: Gtk' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.
|
||
Comment 2•4 years ago
|
||
Is this a Firefox version provided by your Linux distribution, or did you manually install Firefox from Mozilla?
I just have checked that the official build from mozilla.org demonstrate the same behavior. Perhaps, it is necessary to open several tabs and then add monitor (in both cases). The bug is not reproducible in 100% cases, but very often.
Again firefox is not completely freezes, e.g. closing the window yields to correct dialog box (close tabs). But webcontent is not draw anymore and the browser is very slow. I will try to submit a screencast.
I just have checked that the official build from mozilla.org demonstrate the same behavior. Perhaps, it is necessary to open several tabs and then add monitor (in both cases). The bug is not reproducible in 100% cases, but very often.
Again firefox is not completely freezes, e.g. closing the window yields to correct dialog box (close tabs). But webcontent is not draw anymore and the browser is very slow. I will try to submit a screencast.
OK, now I understand the problem a little bit better. When the external monitor is plugged in, I can select in GNOME preferences the primary display. In my case this is the display 2 (the external monitor). To be precise, in my case this display is located over the display 1 (the built-in monitor): in my table the screen of my laptop is below the monitor, therefore I use the same virtual arrangement. When I remove the external monitor GNOME makes built-in monitor the primary screen. Now, when external monitor is absent I start firefox and begin a work. Then I add the external monitor and GNOME makes it the primary monitor restoring the original configuration. In this case, the firefox window stays at the laptop screen and application becomes broken. All other applications works flawlessly in my configuration.
If the primary screen is selected as the built-in monitor, then the bug is NOT reproducible.
|
||
Comment 6•4 years ago
|
||
Hi, Thank you for reporting this issue, I tried to reproduce this issue on a Dell laptop with ubuntu 20.04, I followed the steps from Comment 5 but I couldnt reproduce this issue, even though the Primary monitor is the external 1080p monitor starting firefox before or after the monitor is connected no issues occur on my side however I wonder if this issue could be related to Bug 1535216 ? or maybe thats more of a 4k issue ? maybe when the user connects the monitor Firefox tries to switch focus to a different screen in a similar way Firefox switches focus to a Javascript modal ?
I will change the component to Core XUL but maybe Window management is the more appropriate Component ?
Serge can you please try to reproduce the same issue with our latest nightly build ? you can find it here : https://nightly.mozilla.org/
|
||
Comment 7•4 years ago
|
||
Yes, the multi-monitor setup is PITA on X11. We're moving to Wayland to provide better support there.
|
|
||
Updated•4 years ago
|
The same behavior with the latest nightly.
Another very similar problem happens sometimes when returning from sleep in multi-monitor configuration. Again the browser is slow and does not render any content.
Wayland is unusable itself, and crashes more frequently than any app :(
Reproducible with new firefox 89.
Because of this annoying bug I have been migrated to brave.
|
||
Comment 10•4 months ago
|
||
Do you still experience this? Wayland is shipping for years now so I expect this to be a non issue now.
Description
•