You mean I’ve been doing everything, from work through CGI to gaming (with 120 FPS mind you) on a display that doesn’t work?
Wayland has many issues, sure, but it’s not even close to the point where “it works” can be used to distinguish it from other display protocols. We (and by we I mean anyone willing to dedicate their life to it) could do a lot to bring X11 up to modern expectations, but it’s just not worth the effort. X11 will outlive the cockroaches, but claiming that Wayland is not a functional display protocol is incorrect and uninformed.
I installed a fresh copy of, I believe, Debian. Wayland, for some reason, couldn’t handle 4 monitors, with one above the other three.
Not the issue I expected on a fresh install. Oh, and the biggest issue I had with Windows was copied straight into Linux. I want my (single) taskbar on a monitor that isn’t my primary.
I’m currently back to Windows. It was already going to be a rough transition, and missing the ideas I was looking for while also adding complications just hasn’t made it worth it.
… is not something you should ever use on a desktop PC. Due to its eternally very outdated nature and not even shipping bugfix updates**** it is not a good fit for anything but servers.
Wayland, for some reason, couldn’t handle 4 monitors, with one above the other three.
“Wayland” doesn’t handle monitors at all. What (because of Debian, wildly outdated) desktop did you use?
Oh, and the biggest issue I had with Windows was copied straight into Linux. I want my (single) taskbar on a monitor that isn’t my primary.
Not a Linux issue, but a problem with the desktop environment you chose. KDE Plasma allows you to configure panels in any way you want.
Its Ubuntu 24.04. When I started it, it took quite awhile and then said “there as a problem, please log out”.
Now that I’ve got it started (where I’m posting from now), it still refuses to arrange my monitors. And I have no idea what this 5th, 13.3" monitor is supposed to be.
It looks like my issues are related to this hardware. I guess that’s understandable. I thought this hardware would be transparent to the OS, and apparently it’s not.
If I hit apply here, it will fail and put them back in a line. I’ll also get around 4 fps and no cursor on the additional monitors.
what desktop environment? what you described works perfectly on KDE. i have 3 monitors here and they work flawless in any arbitrary combination or orientation under wayland. side-by-side or on top of each other or even diagonal. with different resolutions and different refresh rates. with taskbars on any number of monitors and any orientation. maybe Debians KDE version is just very outdated. the 6+ versions work fantastic.
But Wayland isn’t a thing on its own, there’s no “Wayland server” or anything else equivalent to the X server. The compositors like Kwin or GNOME’s Mutter are Wayland implementations fully responsible for handling the display output.
You can blame Wayland for the lack of universally supported global hotkeys or for issues with apps that need to know exactly where on the screen they are - these are issues with the protocol - but not for bugs in one compositor’s implementation of display management.
That’s exactly the problem. Wayland is a set of standards, more akin to FreeDesktop.Org than to X. It lives and dies by its implementations, and it’s so utterly dependent on them that “KDE Wayland” has started to become its own thing. KDE are pretty much forging ahead alone nowadays and when they make changes it becomes the way to do it. Also what they do can’t be shared with other desktops because they’d have to use KDE’s own subsystems and become dependent on its whims.
It wasn’t supposed to be “Kdeland” and “Gnomeland” but that’s what it’s slowly becoming. We’re looking at major fragmentation of the Linux desktop because desktop teams have and do stop seeing eye to eye on major issues all the time. And because there’s no central implementation to keep them working together they’re free to do their own thing.
My setup is two screens side by side and one above. KDE Plasma 6.1 can handle it without issues, and you can make panels on any screen.
One of the most significant drawbacks of Wayland is feature fragmentation between compositors. Unlike the X11 stack of X.Org server + window manager + compositor, Wayland compositors have to implement all of Wayland in themselves. They have to serve as the display servers, plus manage window positioning, plus render the clients, and all of that within the confines of Wayland-protocols. Building a compositor is a massive task, which is why middleware like wlroots is such a big deal. It also means that WM-agnostic tools like xrandr and xdotool are more difficult, sometimes impossible to implement.
Consider that Wayland is still heavily under development, and that new protocols have to be implemented by every compositor separately, and that the development of wayland-protocols is an ongoing fucking trainwreck – fragmentation is inevitable, and some compositors will not have the same functionality as others (GNOME being a particularly nasty sandbag). Similarly, things that don’t work as expected in one compositor might work perfectly fine in another.
Right now I would consider KDE Plasma to be the most feature-complete compositor that is also beginner-friendly.
You mean I’ve been doing everything, from work through CGI to gaming (with 120 FPS mind you) on a display that doesn’t work?
Wayland has many issues, sure, but it’s not even close to the point where “it works” can be used to distinguish it from other display protocols. We (and by we I mean anyone willing to dedicate their life to it) could do a lot to bring X11 up to modern expectations, but it’s just not worth the effort. X11 will outlive the cockroaches, but claiming that Wayland is not a functional display protocol is incorrect and uninformed.
I installed a fresh copy of, I believe, Debian. Wayland, for some reason, couldn’t handle 4 monitors, with one above the other three.
Not the issue I expected on a fresh install. Oh, and the biggest issue I had with Windows was copied straight into Linux. I want my (single) taskbar on a monitor that isn’t my primary.
I’m currently back to Windows. It was already going to be a rough transition, and missing the ideas I was looking for while also adding complications just hasn’t made it worth it.
… is not something you should ever use on a desktop PC. Due to its eternally very outdated nature and not even shipping bugfix updates**** it is not a good fit for anything but servers.
“Wayland” doesn’t handle monitors at all. What (because of Debian, wildly outdated) desktop did you use?
Not a Linux issue, but a problem with the desktop environment you chose. KDE Plasma allows you to configure panels in any way you want.
Its Ubuntu 24.04. When I started it, it took quite awhile and then said “there as a problem, please log out”.
Now that I’ve got it started (where I’m posting from now), it still refuses to arrange my monitors. And I have no idea what this 5th, 13.3" monitor is supposed to be.
It looks like my issues are related to this hardware. I guess that’s understandable. I thought this hardware would be transparent to the OS, and apparently it’s not.
If I hit apply here, it will fail and put them back in a line. I’ll also get around 4 fps and no cursor on the additional monitors.
what desktop environment? what you described works perfectly on KDE. i have 3 monitors here and they work flawless in any arbitrary combination or orientation under wayland. side-by-side or on top of each other or even diagonal. with different resolutions and different refresh rates. with taskbars on any number of monitors and any orientation. maybe Debians KDE version is just very outdated. the 6+ versions work fantastic.
Ok but it’s not called Kdeland.
OK but Wayland is not responsible for arranging monitors
If Wayland is so fragile as to only work with KDE, and is not responsible for anything, how long until it’s relegated to a KDE internal subsystem?
But Wayland isn’t a thing on its own, there’s no “Wayland server” or anything else equivalent to the X server. The compositors like Kwin or GNOME’s Mutter are Wayland implementations fully responsible for handling the display output.
You can blame Wayland for the lack of universally supported global hotkeys or for issues with apps that need to know exactly where on the screen they are - these are issues with the protocol - but not for bugs in one compositor’s implementation of display management.
That’s exactly the problem. Wayland is a set of standards, more akin to FreeDesktop.Org than to X. It lives and dies by its implementations, and it’s so utterly dependent on them that “KDE Wayland” has started to become its own thing. KDE are pretty much forging ahead alone nowadays and when they make changes it becomes the way to do it. Also what they do can’t be shared with other desktops because they’d have to use KDE’s own subsystems and become dependent on its whims.
It wasn’t supposed to be “Kdeland” and “Gnomeland” but that’s what it’s slowly becoming. We’re looking at major fragmentation of the Linux desktop because desktop teams have and do stop seeing eye to eye on major issues all the time. And because there’s no central implementation to keep them working together they’re free to do their own thing.
My setup is two screens side by side and one above. KDE Plasma 6.1 can handle it without issues, and you can make panels on any screen.
One of the most significant drawbacks of Wayland is feature fragmentation between compositors. Unlike the X11 stack of X.Org server + window manager + compositor, Wayland compositors have to implement all of Wayland in themselves. They have to serve as the display servers, plus manage window positioning, plus render the clients, and all of that within the confines of Wayland-protocols. Building a compositor is a massive task, which is why middleware like wlroots is such a big deal. It also means that WM-agnostic tools like
xrandrandxdotoolare more difficult, sometimes impossible to implement.Consider that Wayland is still heavily under development, and that new protocols have to be implemented by every compositor separately, and that the development of wayland-protocols is an ongoing fucking trainwreck – fragmentation is inevitable, and some compositors will not have the same functionality as others (GNOME being a particularly nasty sandbag). Similarly, things that don’t work as expected in one compositor might work perfectly fine in another.
Right now I would consider KDE Plasma to be the most feature-complete compositor that is also beginner-friendly.