> What looks like "typical Linux geeks being geeks" with this situation:
I call systems like this CADT-compliant after Jamie Zawinski's Cascade of Attention-Deficit Teenagers idea.
Wayland is a system for which CADT-compliance (and maybe security) trumps nearly all other concerns. No surprise, the primary use case for Wayland is and was always GNOME -- the very system for which Zawinski coined CADT.
I mean... having used both X and Wayland as daily drivers, you're fucking insane if you think you can EVER get me back on X.
On Wayland I get excellent multi-monitor support (mixed scaling ratios, much better automatic detection and configuration, much better plug-and-play). I also have a touchpad on my XPS that feels just as good as a Mac.
To boot, I haven't had to touch a config file related to input devices or output devices a single time using Arch/GDE/Wayland.
Honestly, I'd probably still be running linux in a VM on my laptop if it weren't for Wayland.
If X is your opinion of "stable and working" then I don't want any part of your systems.
Cannot say Wayland works smoothly on my triple-monitor setup. One of the monitors sometimes stops working randomly, and wakes up to display Plymouth screen when I reboot the thing.
Dell Precision 7520 with an AMD GPU. The degree of flakiness is different depending on whether you're on Plasma or GNOME, but it's there nonetheless.
I mean, my data point of one isn't all that helpful if you're having issues, but triple monitors do indeed work on my end.
I switch between a station that has a 4k display next to a standard 1920x1080 display as well as my laptop display (3200x1800) and my home setup with the laptop and 2 4k displays.
I had an issue on the 4k displays when I attempted to run two displays and a usb hub on a single thunderbolt line, but that wasn't Wayland, that was me being dumb: The thunderbolt protocol only support 40Gb/s and each monitor uses 20Gb/s and the hub eats another 10Gb/s. If the hub got detected last, it dropped to usb 2, if one of the monitors came online last, it would drop to 30hz refresh rate. Frankly - I was a little floored when I realized that I was the one being dumb and the system was mostly still just making things work. Just for shits and giggles I booted up an x-session after to see what it does. The answer is lots of black screen.
I'm guessing that's an AMD GPU thing and not a Wayland thing. I run a triple-monitor setup with an AMD GPU on X.org and I have a similar problem: every once in a while when I boot my PC one of the monitors just doesn't come to life. Restarting X usually fixes it.
On Kubuntu 20.04, and honestly ever since I first tried it from Kubuntu 16.04 on up, multi-monitor support has been terrific for me. Maybe Gnome has problems, but not KDE on X.
X works for me on systems with multi-month uptimes (dictated by software updates that have nothing to do with X) and networking windows over the Internet, something RDP (and, to the best of my knowledge, Wayland) is incapable of. Meanwhile, Wayland doesn't run the software I want to run and doesn't run on the hardware I own.
Well, not your typical end user routine I guess. I’d like that in mainstream distros please, without having to edit .desktop files to shove in all the commandline flags.
I mean, could it help if we mercilessly threw away all the code from Xorg that is there to support all the Unixes from the 80s and 90s, all the code paths for kernel-bypassing direct hardware access, and reimplemented the protocol on the same stack Wayland compositors live? Wouldn't it have solved the problems that were not about the protocol design?
Sure if someone wrote it in Rust it would be also safe and secure /s
I call systems like this CADT-compliant after Jamie Zawinski's Cascade of Attention-Deficit Teenagers idea.
Wayland is a system for which CADT-compliance (and maybe security) trumps nearly all other concerns. No surprise, the primary use case for Wayland is and was always GNOME -- the very system for which Zawinski coined CADT.