3 ms·
I also have crashes on sway, but there’s a rough workaround now which prevents the issue totally. I believe there’s a design issue with Firefox and GTK handlin
by TimeBearingDown 3y ago
I also have crashes on sway, but there’s a rough workaround now which prevents the issue totally.
I believe there’s a design issue with Firefox and GTK handling input events; some Wayland compositors have workarounds but others do not.
https://github.com/swaywm/sway/issues/7645 https://github.com/swaywm/sway/issues/7645
https://bugzilla.mozilla.org/show_bug.cgi?id=1743144 https://bugzilla.mozilla.org/show_bug.cgi?id=1743144
Firefox is my preferred browser and I hope we can keep its engine alive in this era of Chrome dominance.
- OfSanguineFire 3y agoI have been using Sway and Firefox for the last three years at least, and have never experienced crashes. Sway and Firefox as packaged by Debian Stable. I really wish people on HN threads complaining about Firefox bugs clearly stated 1) their environment, and 2) who packaged the Firefox, because those are what could make all the difference.
- the8472 3y agoThe bug depends on a few factors that aren't really packaging-specific. A) the default socket buffer size B) the polling rate of your mouse C) whether there's anything on your system or in your firefox profile that can cause enough lag that the buffer overflows D) whether your compositor has any workarounds for that protocol limitation Well, I suppose a packager could have disabled wayland in firefox...