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
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.
I mean, let’s be honest. Most of people online came running with their pitchforks whenever someone said anything good about xorg or forked it. So, I guess most of them got what they deserved. Not you, of course 😂
That’s awesome.
50% of what I use doesn’t work and I will respond to the Wayland knife with C4.
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
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.
I mean, let’s be honest. Most of people online came running with their pitchforks whenever someone said anything good about xorg or forked it. So, I guess most of them got what they deserved. Not you, of course 😂