| Slightly tangential, but I recently gave Wayland a try on KDE, as I kept reading how screen tearing is not an issue. On NixOS this is as simple as choosing a Wayland session in SDDM. My setup was one main 4K screen in landscape, and one secondary 1080p screen in portrait. Immediately I noticed several major bugs: - The taskbar panel was stuck at 60% on the Y axis. Unlocking it and moving it manually was not possible. That's the furthest down it would go. - The taskbar panel had very large icons. Much larger than the 64px I configured it with. - Right-clicking on certain parts of the desktop would popup the menu on a different part of the screen. - Hovering over the min/max/close buttons of any window would render the cursor at like 5 FPS. - Scaling in Firefox was way too small. The cursor itself scaled down when hovered over the Firefox window. - Playing a video in Firefox on the portrait screen and making it fullscreen, would rotate the video to landscape. I briefly tried to look into some of these issues, but quickly gave up. I'm sure veteran Wayland users will say that this is an issue with KDE, with Firefox, with Xwayland, or whatever else, but that doesn't help me one bit. The point is that the complexity in the display system is so high, that I have no idea where to look for the culprit. Oh, at least screen tearing wasn't an issue. It's frankly embarrassing that the state-of-the-art in rendering GUIs on Linux is so broken. Wayland is a decade old now, yet it hasn't made multi-monitor support easier, and has only introduced more complexity into the system, by leaving support up to each application. What a clusterfuck. I went back to X, and I'm waiting for the screen tearing fix[1] to be released. [1]: https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests... |