Hangs with Xwayland and swaywm and display hotplug
Categories
(Core :: Widget: Gtk, defect)
Tracking
()
People
(Reporter: matthias, Unassigned)
References
Details
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/117.0
Steps to reproduce:
- Wayland run user session with swaywm, two displays
- start firefox
- play with hotplugging displays
Actual results:
Funny display artefacts (obvious memory corruption), UI hangs
Expected results:
Everything works.
To "fix" this problem, set MOZ_ENABLE_WAYLAND=1.
I wonder why this isn't the default in the first place. Running under Xwayland does not make sense any more IMHO. Not in 2023. It also fixes other problems, e.g. with dragging window contents on touchscreens, which also doesn't work without that envvar.
|
||
Comment 1•2 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 correct in case you think the bot is wrong.
Looks like we're going to ship Wayland by default - Bug 1752398. So no need to set MOZ_ENABLE_WAYLAND any more.
Description
•