Could you give some actual examples of the things that don’t work? I hear people say this a lot, but then they basically refuse to answer what’s not working. There was definitely a lot of wailing pain when it first transitioned, but these days, at least on plasma for me, I haven’t found anything that doesn’t work anymore. other than of course perhaps just some vague abandoned software that wants to do something crazy with the display
I use screen sharing and whiteboard software that needs direct drawing over the screen on a daily basis teaching lessons. And I use x2x on a daily basis for kvm on multiple computers.
There is absolutely no functional, reliable replacement for most of these functions. Until there is, Wayland is absolutely useless as far as I’m concerned, and everyone who tries to tell me it’s time to switch gets both enthusiastic middle fingers.
Plasma does solve some problems itself but: screen recording, global hotkeys, clipboard management to name a few. They all have “solutions”, it just sucks to be made to jump through hoops sometimes. There’s a lot of desirable things in x11 that while crusty worked well, like xrandr and being able to script monitor config. It is niche! But if you used it, it’s annoying to be forced off it
What exactly about these three? I’m really curious to understand.
I never used X knowingly: by the time I’ve started understanding Linux more or so, I’ve been on Wayland already. So, in a way, I can say I never used X, even being on Linux on and off for almost two decades.
Say, screen recording. It just works for me on Sway (I use wf-recorder) and it just works on Gnome. I have never thought of it as being broken. I could have missed anything though. Not something I use very often.
What global hotkeys do you mean here? Mine work in all apps. So, I assume they’re global. Or is it something different?
Not sure about clipboard: it just works too. There’s this ‘middle mouse click’ shit that I hate, as I accidentally paste some unnecessary information into, say, email. Upon scrolling, and accidentally pressing the scroll wheel. I’d love to disable it globally, but it just there, working. I assume that’s a feature for some folks, but I passionately hate it and have no use for.
EDIT: I just realized in the linked gist they’re basically complaining Wayland doesn’t have “builtin” support for things like keylogging, and generally uses portals for features. Yes, some DEs may choose not to implement specific features, and apparently that’s Wayland’s fault?
Screen recording works, I think it’s only existing X software that doesn’t. In my experience there’s still some jank and limitations that might or might not be related to Wayland. After a few days of runtime with periods of sleep mode, screencasting through the portal seems to break until pipewire is restarted. I don’t know if there’s a way to capture an application and its audio automatically.
Global hotkeys refer to hotkeys that can be activated while the application isn’t focused. Wayland has global hotkeys, but some people don’t like the implementation and refuse to use it. OBS, for example, has an unofficial plugin implementing them, but the actual project refuses because they can’t display and set hotkeys from their own setting menu, and have no good way to support multiple profiles with separate bindings.
I also don’t know what they mean by clipboard management, but I do know there’s some jank. As a weirdly specific example, when playing Minecraft with patched glfw with native Wayland support, pasting into chat doesn’t work correctly, it seems to always paste the text that was in the clipboard when the game was opened, and not update when copying things from outside the game (but I think it works when copying something inside the game itself). I don’t know if this is an actual Wayland issue, or a case of a broken client implementation, but the lack of software support is still a type of issue.
Yes, some DEs may choose not to implement specific features, and apparently that’s Wayland’s fault?
Kind of. For a long time a mainstream setup like Gnome on Wayland lacked features because they weren’t yet incorporated into Gnome. But more generally, Wayland deliberately didn’t implement a bunch of features that X had, or had external things that accomplished. That pushed the responsibility for implementing it onto each and every window manager. Smaller WMs that would have had all of those features for free on X now have a big burden to achieve the same bar on Wayland, and so many don’t manage it. That’s due to the choices that went into Wayland.
AFAIK all of Wayland is pushed onto the WM, because Wayland is just a set of protocols. It has some libraries, I think official ones, to help with implementing those protocols, but ultimately that’s a design choice that also means WMs don’t have to have those features, especially relevant for atypical WMs where the concept of windows might not exist, displays might not be two dimensional, input might be neither a mouse nor a keyboard.
To my understanding, if somebody wants an unusual setup, on Wayland they might need to figure out implementation of protocols for their ideas. On X11, they might not be able to do anything because it enforces certain ideas of how a graphical environment works.
That’s simply not a failure of Wayland, it’s a tradeoff they chose, and it seems dishonest when people say things “don’t work on Wayland” because the responsibility is deliberately moved to a portal or something.
It is a trade-off they chose yeah, but for people on anything but KDE (really, though hyprland sway and gnome do most too) they’ve forced them to either catch up or die. I don’t know that that’s indicative of a great replacement project. For reference, I use Wayland & KDE fine, but if x11 had HDR I’d switch back to my i3 setup.
I think the “die” part is a bit of an overexaggeration, it’s true that they need to implement protocols if they want the features those protocols exist to provide, but the X way seems to have caused more problems in the long run. Niche projects will attract people who want that niche, hopefully despite missing features, and some people who can help implement those features.
It’s worth noting that DEs can do things like use XDG portal implementations from another DE, I think it might’ve been Niri that does that.
if x11 had HDR I’d switch back to my i3 setup.
Then I can wish you that you get a worthy compositor/DE/whatever to replace i3 on Wayland. Either that or i3 somehow getting a Wayland implementation. I’m lucky in that I was comfortable on plasma with X, so switching to Wayland was mostly painless, though there were significantly more issues back then.
It is an exaggeration in that Wayland isn’t outright killing x, but a lot of the talk surrounding both is that it’s supposed to.
I’m not going to defend the state of X and the problems it’s caused because it’s a fugly old project, just when you look at something like pulse -> pipe wire, there wasn’t a big paradigm shift with it. It did the same job and better (to my knowledge!).
I didn’t know that DEs could use others portal implementations, that seems neat?
Yeah it’s the specifics of that that’s the issue for me though. I tried hyprland and many things are really cool about it but lots of things just break, and maintaining separate configs for what feels like core features was annoying. Then you get things like HDR performing differently between it and plasma, something that I’d hoped Wayland would just own. I’ll probably try niri and sway at some point, they both look cool
@kuberoot@FishFace
Yes, but this makes wayland good for everyrhing except normal desktop. It’s pretty good for VR/spatial desktops (where we do not want to deal with 2d coordinates), for some embedded setups where we only need to manage output to multiple displays or draw some overlays. But on normal desktop we need draw UI (wayland cannot do drawing at all!), position windows (limited), capture screen (actually done outside of wayland???) warp mouse (broken?), inject events for automation (yes, ei exist, but looks like very optional…), set screen resolution and layout (actually made different in every implementation?), manage clipboard (still depends on compositor?)
So, wayland actually does almost nothing for desktop :(
Sure, Wayland “actually does nothing”, if you only and specifically mean things that are built into Wayland and only Wayland, the core project, itself.
Meanwhile, as an actual user of a normal desktop on Wayland I can capture the screen, mouse warping works, I have an autoclicker, my screens have resolution, layout and scaling set, my clipboard and clipboard history work (with individual exceotions, accessible from a command line tool too). Hell, I even have HDR on because I found out it just works nowadays, even though my display is probably ass for HDR, but SDR content seems to look no different with it enabled.
Window positioning is something that’s not finished, because the developers are trying to figure out a good way to do it and are taking a long time.
Not sure what you mean by “drawing”, is it some pedantic bullshit again about how Wayland itself doesn’t dictate how you render stuff? Because I certainly have all kinds of GUIs running on my computer.
So if you want a system that is hardcoded to only support things that are common nowadays and that will start breaking down in the next 10 years as things change and the code becomes impossible to maintain, maybe go contribute to XLibre. I will meanwhile patiently enjoy Wayland getting better, even if it might take years, because I have hope that this approach will work.
Regarding the clipboard - there are practically 2 clipboards, i can paste different things based on whether i used ctrl-c/v or selecting text with the mouse and middle-clicking. I often fall into this trap, anf i would prefer it to be unified.
I recently noticed, that on Fedora Silverblue with Gnome, middle-click-paste does not work. Not sure, how and why it has beend disabled. I am glad it still works on Debian stable with an older version of Gnome.
Thanks for letting me know! I hope there would be some middle ground for this feature at some point, with reliable ways of disabling / enabling it. Personally, I believe that it doesn’t need to be enabled by default, as average users don’t need it. And those who need it wouldn’t have any issues with enabling it once. (Assuming it’s reliable.) But I don’t mind otherwise, if I could just disable it. For some reason, I couldn’t.
I guess those 3 are solved by KDE then. I only know Wayland through KDE and the 3 work perfectly fine for me, I didn’t even have to think about them when I used them.
Try copying to your clipboard in vim without a plugin, or try starting to record without a (very shaky) OBS plugin. I’m not saying Wayland broke into my house and burgled me but their decision to create everything as distant APIs means that all the smaller DE/WMs have to implement it in a certain way. KDE does a great job of this, but I now have to choose between using HDR on KDE and having things that used to work fineon something like i3
Sorry, I meant trigger it with a hot key. Thanks to pipewire, the actual screen recording is in a pretty good place now, providing the permission stuff is implemented correctly
But because OBS hasn’t registered its capacity for hotkeys via Wayland, they don’t work globally. I’m sure it’s not a crazy addition to the codebase, it just feels like a step back to me
I feel like it’s all made more frustrating to me too because it seems so many of the problems are in service of answering a threat vector I just don’t give a shit about.
Yeah… it almost makes me wish for an “unsafe mode” where Wayland allows all the things it didn’t allow for the sake of security, but given there was a way to run x11 rootless and many people didn’t, I’m guessing that would just make everyone use it in that way
However, the security stuff feels so hypothetical to me right now. I’m on Wayland purely because it supports HDR, I can’t easily cite a single other benefit for myself
an issue with Wayland that i have is when i launch a game (Minecraft) from steam, it loses the process and steam doesn’t recognize the game as running. because it’s not recognized, my steam input settings aren’t applied to my controller and I’m stuck in desktop mode.
the exact same setup worked in older Minecraft versions on Wayland.
Running on older nVidia cards causes visual glitches and memory leaks to the point where not even short remote sessions are usable. I have a Quadro K420 in my home server.
Replaced KDE with xfce and everything works perfectly again. Too bad they are forcing Wayland now.
That sounds like an NVIDIA issue though, not a Wayland one. NVIDIA has never really given a flying shit about how the drivers run for non-corporate customers.
Also, no one is forcing Wayland, they are just choosing to not maintain X11.
Sure, it’s not completely on Wayland. What I know is that X11 works fine in this configuration and Wayland does not.
Also, no one is forcing Wayland, they are just choosing to not maintain X11.
That isn’t the same. They forced it on users that were using X11 just fine. With a minor version update! That isn’t right.
Does anything require explicitly removing the choice at this point? It still seems premature and will put an asterisk on Linux reviving any old system.
That’s where out interpretations differ. You can just stay on the old software that ran it fine, or move to a distro that wants the burden of supporting the X11 code as their own series of patches.
No one is forcing you to update to the version where they decided to stop maintaing X11. And removing it is the correct choice if you are not willing to maintain it any longer, otherwise you get bug reports for code you have no intention of fixing.
Could you give some actual examples of the things that don’t work? I hear people say this a lot, but then they basically refuse to answer what’s not working. There was definitely a lot of wailing pain when it first transitioned, but these days, at least on plasma for me, I haven’t found anything that doesn’t work anymore. other than of course perhaps just some vague abandoned software that wants to do something crazy with the display
I use screen sharing and whiteboard software that needs direct drawing over the screen on a daily basis teaching lessons. And I use x2x on a daily basis for kvm on multiple computers.
There is absolutely no functional, reliable replacement for most of these functions. Until there is, Wayland is absolutely useless as far as I’m concerned, and everyone who tries to tell me it’s time to switch gets both enthusiastic middle fingers.
Plasma does solve some problems itself but: screen recording, global hotkeys, clipboard management to name a few. They all have “solutions”, it just sucks to be made to jump through hoops sometimes. There’s a lot of desirable things in x11 that while crusty worked well, like xrandr and being able to script monitor config. It is niche! But if you used it, it’s annoying to be forced off it
Here is a (biased but decent enough) list https://gist.github.com/probonopd/9feb7c20257af5dd915e3a9f2d1f2277
What exactly about these three? I’m really curious to understand.
I never used X knowingly: by the time I’ve started understanding Linux more or so, I’ve been on Wayland already. So, in a way, I can say I never used X, even being on Linux on and off for almost two decades.
Say, screen recording. It just works for me on Sway (I use
wf-recorder) and it just works on Gnome. I have never thought of it as being broken. I could have missed anything though. Not something I use very often.What global hotkeys do you mean here? Mine work in all apps. So, I assume they’re global. Or is it something different?
Not sure about clipboard: it just works too. There’s this ‘middle mouse click’ shit that I hate, as I accidentally paste some unnecessary information into, say, email. Upon scrolling, and accidentally pressing the scroll wheel. I’d love to disable it globally, but it just there, working. I assume that’s a feature for some folks, but I passionately hate it and have no use for.
Not OP, but wanted to address some questions:
EDIT: I just realized in the linked gist they’re basically complaining Wayland doesn’t have “builtin” support for things like keylogging, and generally uses portals for features. Yes, some DEs may choose not to implement specific features, and apparently that’s Wayland’s fault?
Screen recording works, I think it’s only existing X software that doesn’t. In my experience there’s still some jank and limitations that might or might not be related to Wayland. After a few days of runtime with periods of sleep mode, screencasting through the portal seems to break until pipewire is restarted. I don’t know if there’s a way to capture an application and its audio automatically.
Global hotkeys refer to hotkeys that can be activated while the application isn’t focused. Wayland has global hotkeys, but some people don’t like the implementation and refuse to use it. OBS, for example, has an unofficial plugin implementing them, but the actual project refuses because they can’t display and set hotkeys from their own setting menu, and have no good way to support multiple profiles with separate bindings.
I also don’t know what they mean by clipboard management, but I do know there’s some jank. As a weirdly specific example, when playing Minecraft with patched glfw with native Wayland support, pasting into chat doesn’t work correctly, it seems to always paste the text that was in the clipboard when the game was opened, and not update when copying things from outside the game (but I think it works when copying something inside the game itself). I don’t know if this is an actual Wayland issue, or a case of a broken client implementation, but the lack of software support is still a type of issue.
Kind of. For a long time a mainstream setup like Gnome on Wayland lacked features because they weren’t yet incorporated into Gnome. But more generally, Wayland deliberately didn’t implement a bunch of features that X had, or had external things that accomplished. That pushed the responsibility for implementing it onto each and every window manager. Smaller WMs that would have had all of those features for free on X now have a big burden to achieve the same bar on Wayland, and so many don’t manage it. That’s due to the choices that went into Wayland.
AFAIK all of Wayland is pushed onto the WM, because Wayland is just a set of protocols. It has some libraries, I think official ones, to help with implementing those protocols, but ultimately that’s a design choice that also means WMs don’t have to have those features, especially relevant for atypical WMs where the concept of windows might not exist, displays might not be two dimensional, input might be neither a mouse nor a keyboard.
To my understanding, if somebody wants an unusual setup, on Wayland they might need to figure out implementation of protocols for their ideas. On X11, they might not be able to do anything because it enforces certain ideas of how a graphical environment works.
That’s simply not a failure of Wayland, it’s a tradeoff they chose, and it seems dishonest when people say things “don’t work on Wayland” because the responsibility is deliberately moved to a portal or something.
It is a trade-off they chose yeah, but for people on anything but KDE (really, though hyprland sway and gnome do most too) they’ve forced them to either catch up or die. I don’t know that that’s indicative of a great replacement project. For reference, I use Wayland & KDE fine, but if x11 had HDR I’d switch back to my i3 setup.
I think the “die” part is a bit of an overexaggeration, it’s true that they need to implement protocols if they want the features those protocols exist to provide, but the X way seems to have caused more problems in the long run. Niche projects will attract people who want that niche, hopefully despite missing features, and some people who can help implement those features.
It’s worth noting that DEs can do things like use XDG portal implementations from another DE, I think it might’ve been Niri that does that.
Then I can wish you that you get a worthy compositor/DE/whatever to replace i3 on Wayland. Either that or i3 somehow getting a Wayland implementation. I’m lucky in that I was comfortable on plasma with X, so switching to Wayland was mostly painless, though there were significantly more issues back then.
It is an exaggeration in that Wayland isn’t outright killing x, but a lot of the talk surrounding both is that it’s supposed to. I’m not going to defend the state of X and the problems it’s caused because it’s a fugly old project, just when you look at something like pulse -> pipe wire, there wasn’t a big paradigm shift with it. It did the same job and better (to my knowledge!).
I didn’t know that DEs could use others portal implementations, that seems neat?
Yeah it’s the specifics of that that’s the issue for me though. I tried hyprland and many things are really cool about it but lots of things just break, and maintaining separate configs for what feels like core features was annoying. Then you get things like HDR performing differently between it and plasma, something that I’d hoped Wayland would just own. I’ll probably try niri and sway at some point, they both look cool
@kuberoot @FishFace
Yes, but this makes wayland good for everyrhing except normal desktop. It’s pretty good for VR/spatial desktops (where we do not want to deal with 2d coordinates), for some embedded setups where we only need to manage output to multiple displays or draw some overlays. But on normal desktop we need draw UI (wayland cannot do drawing at all!), position windows (limited), capture screen (actually done outside of wayland???) warp mouse (broken?), inject events for automation (yes, ei exist, but looks like very optional…), set screen resolution and layout (actually made different in every implementation?), manage clipboard (still depends on compositor?)
So, wayland actually does almost nothing for desktop :(
Sure, Wayland “actually does nothing”, if you only and specifically mean things that are built into Wayland and only Wayland, the core project, itself.
Meanwhile, as an actual user of a normal desktop on Wayland I can capture the screen, mouse warping works, I have an autoclicker, my screens have resolution, layout and scaling set, my clipboard and clipboard history work (with individual exceotions, accessible from a command line tool too). Hell, I even have HDR on because I found out it just works nowadays, even though my display is probably ass for HDR, but SDR content seems to look no different with it enabled.
Window positioning is something that’s not finished, because the developers are trying to figure out a good way to do it and are taking a long time.
Not sure what you mean by “drawing”, is it some pedantic bullshit again about how Wayland itself doesn’t dictate how you render stuff? Because I certainly have all kinds of GUIs running on my computer.
So if you want a system that is hardcoded to only support things that are common nowadays and that will start breaking down in the next 10 years as things change and the code becomes impossible to maintain, maybe go contribute to XLibre. I will meanwhile patiently enjoy Wayland getting better, even if it might take years, because I have hope that this approach will work.
Regarding the clipboard - there are practically 2 clipboards, i can paste different things based on whether i used ctrl-c/v or selecting text with the mouse and middle-clicking. I often fall into this trap, anf i would prefer it to be unified.
I recently noticed, that on Fedora Silverblue with Gnome, middle-click-paste does not work. Not sure, how and why it has beend disabled. I am glad it still works on Debian stable with an older version of Gnome.
Thanks for letting me know! I hope there would be some middle ground for this feature at some point, with reliable ways of disabling / enabling it. Personally, I believe that it doesn’t need to be enabled by default, as average users don’t need it. And those who need it wouldn’t have any issues with enabling it once. (Assuming it’s reliable.) But I don’t mind otherwise, if I could just disable it. For some reason, I couldn’t.
I guess those 3 are solved by KDE then. I only know Wayland through KDE and the 3 work perfectly fine for me, I didn’t even have to think about them when I used them.
Try copying to your clipboard in vim without a plugin, or try starting to record without a (very shaky) OBS plugin. I’m not saying Wayland broke into my house and burgled me but their decision to create everything as distant APIs means that all the smaller DE/WMs have to implement it in a certain way. KDE does a great job of this, but I now have to choose between using HDR on KDE and having things that used to work fineon something like i3
I can record my wayland session in OBS without any plugins. here it was working fine even in plasma 5
Sorry, I meant trigger it with a hot key. Thanks to pipewire, the actual screen recording is in a pretty good place now, providing the permission stuff is implemented correctly But because OBS hasn’t registered its capacity for hotkeys via Wayland, they don’t work globally. I’m sure it’s not a crazy addition to the codebase, it just feels like a step back to me
I feel like it’s all made more frustrating to me too because it seems so many of the problems are in service of answering a threat vector I just don’t give a shit about.
Yeah… it almost makes me wish for an “unsafe mode” where Wayland allows all the things it didn’t allow for the sake of security, but given there was a way to run x11 rootless and many people didn’t, I’m guessing that would just make everyone use it in that way However, the security stuff feels so hypothetical to me right now. I’m on Wayland purely because it supports HDR, I can’t easily cite a single other benefit for myself
an issue with Wayland that i have is when i launch a game (Minecraft) from steam, it loses the process and steam doesn’t recognize the game as running. because it’s not recognized, my steam input settings aren’t applied to my controller and I’m stuck in desktop mode.
the exact same setup worked in older Minecraft versions on Wayland.
Running on older nVidia cards causes visual glitches and memory leaks to the point where not even short remote sessions are usable. I have a Quadro K420 in my home server.
Replaced KDE with xfce and everything works perfectly again. Too bad they are forcing Wayland now.
That sounds like an NVIDIA issue though, not a Wayland one. NVIDIA has never really given a flying shit about how the drivers run for non-corporate customers.
Also, no one is forcing Wayland, they are just choosing to not maintain X11.
Sure, it’s not completely on Wayland. What I know is that X11 works fine in this configuration and Wayland does not.
That isn’t the same. They forced it on users that were using X11 just fine. With a minor version update! That isn’t right.
Does anything require explicitly removing the choice at this point? It still seems premature and will put an asterisk on Linux reviving any old system.
That’s where out interpretations differ. You can just stay on the old software that ran it fine, or move to a distro that wants the burden of supporting the X11 code as their own series of patches.
No one is forcing you to update to the version where they decided to stop maintaing X11. And removing it is the correct choice if you are not willing to maintain it any longer, otherwise you get bug reports for code you have no intention of fixing.