this post was submitted on 28 Jul 2025
91 points (88.9% liked)
Linux
8740 readers
301 users here now
A community for everything relating to the GNU/Linux operating system (except the memes!)
Also, check out:
Original icon base courtesy of lewing@isc.tamu.edu and The GIMP
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Canonical. They had that brilliant idea of wayland-by-default in 2017.
It was a great clusterfuck of frustration for me and other Ubuntu users
Fedora even switched to Wayland by default in 2016 (at least for the GNOME release). I don't know what they were thinking. 8 to 9 years before they were already using Wayland... and it still have some "problems". Can't imagine what you were going through. :D
But compared to Fedora, Ubuntu only did change temporarily to Wayland right? I mean it was not an LTS version. I installed LTS 18.04 and don't remember anything like that by default.
Fedora 42 even eliminated X11 as an option (I think they're reversing that stance now, though), which made it unusable on my (now dead) Nvidia laptop with dual monitors. I thought they really jumped the gun on that one.
I ended up jumping to AMD graphics so I wouldn't have any problems with Wayland, but then discovered there's a nasty bug that causes frequent system freezes on AMD systems. Thankfully I was on Debian, so I could easily switch back to X11. Things have been stable now, but I just feel like I can't win with Wayland 😅
Wayland does seem to work well with Intel graphics, at least.
My girlfriend decided to make a switch to Linux, and I installed Fedora 42.
It immediately broke her workflow as one of her work apps (Omnissa Horizon, previously known as VMware Horizon) explicitly refused to work with Wayland, stating it will only work with X11.
Had to switch to OpenSUSE Tumbleweed.