| pulling the concrete friction-report referenced in the reply https://news.ycombinator.com/item?id=35316159 (these are not necessarily the same issues, but at least similar-sounding ones I found by googling) • widgets opening in wrong place: https://bugs.kde.org/show_bug.cgi?id=459188 • ignoring icon size configurations: https://gitlab.freedesktop.org/wayland/wayland-protocols/-/i..., closed as wontfix • on touchscreen menus open wherever you left the cursor: https://bugs.kde.org/show_bug.cgi?id=406025, more info in https://github.com/PeterCxy/evdev-right-click-emulation/issu... • cursor framerate issues: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/1827 maybe, it's in the gnome issue tracker but described as wayland-specific, so might also be happening on KDE • firefox using wrong screen's DPI: https://bugzilla.mozilla.org/show_bug.cgi?id=1632829, resolved by original reporter but last comment is a repro from someone else. also reported in https://github.com/flatpak/flatpak/issues/5300 but closed as "wrong bug tracker" • fullscreening a video rotates it from portrait to landscape: https://bugzilla.mozilla.org/show_bug.cgi?id=1600962 possibly, https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/190522... possibly In general wayland seems too buggy for major software like firefox to use it by default, per https://askubuntu.com/questions/1409389/why-doesnt-firefox-r... Impressive list to hit in only 5 minutes! |
Some of those might be the bugs I experienced, but then again, some of them claim to be fixed years ago, and I was running a fully up-to-date NixOS unstable (rolling release) system.
Reporting an issue in an OSS project is a great freedom that users have, but it involves so many steps, especially in these complex environments, that it's often not worth the effort. Even if you manage to figure out which component is misbehaving, to search if there's an already open bug report, and take the time to create one if not, there's a chance of running into hostility and WONTFIX responses.
> Impressive list to hit in only 5 minutes!
All it took was logging in, launching Firefox and playing a video. If these issues were so obvious in 5 minutes, I couldn't imagine how many there would be had I used the system for longer. Switching back to Xorg was the quickest fix to my workflow. Besides, I figured that since these issues were so obvious that they were already known. I was just befuddled as to why they remain so prominent given that Wayland is already 15 years old, and there are mainstream distros offering it as an alternative, or switching altogether to it.