As a person who doesn’t really give a shit. I’ve even forgotten that I’m on Wayland. Everything I need works and that’s all that matters to me. Y’all can keep your wars to yourselves
It’s a text editor with a lisp interpreter built in. The lisp interpreter means it can do basically anything from file management, to IRC, to email, to git. There are a bunch of addons and a virtuous interaction between good text editing and using the functionality to do other things. So if you improve say spell checking you magically get better and more ergonomic spell checking not only in your text editor but on IRC and email etc.
Lisp is very very malleable and relatively easy to use so it has a fairly massive ecosystem compared to its relatively tiny userbase. It’s design and conservation of functionality for 30 years that you could have made a tiny workflow improvement 20 years ago and still benefit from it because your little tweak remains compatible with modern day emacs with little to no effort. Emacs users often disproportionately value it because over the years their environment has years of such little improvements particular to their usage.
AAAAAGHHH! MY EYES!! WHAT HAVE YOU DONE?! I had spent YEARS blissfully ignorant of what Emacs does and you just destroyed all that in a single comment! MY BRAIN IS BURNING! I DIDN’T CONSENT TO THIS KNOWLEDGE! I WAS HAPPY NOT KNOWING! 😭
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 😂
I’m not an obstructionist but having been forced in to Wayland by plasma 6.8 it is frustrating that orcaslicer just crashes unless I tell it to run in xwayland and desk flow requires being on unstable to work with my clipboard and discord canary just shares audio from my whole desktop instead of from just my game and AGHHH I just want my things to work! So frustrating
It’s usually not as simple as is Wayland the issue or not in my experience. Wayland and the wm/DE and the application all have to get along and it gets along better with some than others. For a variety of reasons. I had an issue with gtk on niri where specific applications would not open up and I had to do a bunch of tweaking. It did eventually work, but it really should have just worked automatically. Wayland was getting instructions from the app that it didn’t know what to do with and instead of it trying to use xwayland instead it was just failing. A lot of the problems come from the fact that X11 is OLD and because its OLD it has taken the time to work out so many random little potential issues. Wayland is new enough that sometimes it just runs into stuff that it hasn’t been tweaked to work around yet. We’re in the polishing phase now tho so these will start to get worked out I think. It’ll just take time. X11 does need replacing as its convoluted as fuck but there’s a reason some people swear by it, and that is largely for this reason. It’s just got a lot of niche functionality that takes decades of dev time to fully flesh out.
The only variable I changed in testing was switching between the x11 and Wayland versions of plasma while I still could. Discord no longer prompts to provide an audio source, desktop will but the screen share won’t work once I actually start it. Orca crashes the moment I hit slice unless I add an environment variable to make it use x11 compatibility mode.
Global keybinds on Wayland were a long-standing pain point. Wayland (rightly) doesn’t let apps listen to your keyboard in the background. Instead, it provides a GlobalShortcuts API, but the implementation can be a little tricky. The spec says a shortcut looks like “<Control>z”, but KDE expects “CTRL+z”, so Discord figures out which desktop you’re on and speaks its dialect (send the wrong one and the portal session can fall over entirely). And since every bind request can pop up an approval dialog, we only ask again when your keybinds actually change, instead of nagging you every time Discord starts. Now, features like push-to-talk work on Linux, even when Discord isn’t focused.
What’s Next: More Control of Sound Sharing
We’ve covered a lot of Linux improvements, but there’s more to do before we reach parity with the other desktop platforms. That means changing to the Wayland infrastructure itself. We use xdg-desktop-portal for screenshare, but that doesn’t provide a handle to capture app audio. Linux users have to choose between sharing audio for their whole desktop or sharing no audio at all. That’s not an experience we can accept long term, so we’re building per-app audio sharing on Wayland and giving it to the Linux community.
We’ve once again teamed up with Igalia to implement per-app audio sharing in xdg-desktop-portal, letting you pick exactly which app’s audio is shared. We’re even implementing it on GNOME and KDE ourselves to get it to users faster. This will take some time to reach critical mass across Linux desktops, but it’s a long-term investment to make a great Linux screenshare experience for both Discord and all screensharing apps. Stay tuned!
I’m not saying audio doesn’t work, I’m saying it doesn’t narrow down to just the application I’m sharing, this is a known regression with the discord client to the best of my knowledge, and as far as I know the orcaslicer crash is a mesa issue affecting just Wayland for whatever reason
I’ve had a bunch of issues with Orcaslicer and Wayland. Thankfully it’s currently working for me but the last year or so I kept having to switch back to X a lot for it.
A lot of people just use Windows and everything they need works. And a lot of people like to customize things and use non-standard tools (quite common among Linux users, actually). It’s a bit silly to say “my setup works, I don’t know what people are complaining about”. Well, different people have different setups.
I don’t even know what I’m using. Whatever is default on Mint. It just works, I don’t want to think about my tools, I just want them to work. And, Mint does, for me.
How dare you say that on a meme community. This is very silly and inconsiderate of you. You HAVE to cry because someone else’s computer has issues because of decisions you had absolutely nothing to do with.
As a person who doesn’t really give a shit. I’ve even forgotten that I’m on Wayland. Everything I need works and that’s all that matters to me. Y’all can keep your wars to yourselves
Wayland is awesome, I believe that the whiners whine because of nostalgia.
Same as you, but I’m on X11
More power to you, friend. I honestly will never understand all the wars and politics in software, but it is what it is I guess.
Yeah, no need to make a religion out of sofware. With the exception of our lord and savior
EmacsI’m going to tell you a secret and please don’t tell anyone:
Tap for spoiler
I don’t know what emacs does, and I’ve never cared to even look it up.
It’s a text editor with a lisp interpreter built in. The lisp interpreter means it can do basically anything from file management, to IRC, to email, to git. There are a bunch of addons and a virtuous interaction between good text editing and using the functionality to do other things. So if you improve say spell checking you magically get better and more ergonomic spell checking not only in your text editor but on IRC and email etc.
Lisp is very very malleable and relatively easy to use so it has a fairly massive ecosystem compared to its relatively tiny userbase. It’s design and conservation of functionality for 30 years that you could have made a tiny workflow improvement 20 years ago and still benefit from it because your little tweak remains compatible with modern day emacs with little to no effort. Emacs users often disproportionately value it because over the years their environment has years of such little improvements particular to their usage.
AAAAAGHHH! MY EYES!! WHAT HAVE YOU DONE?! I had spent YEARS blissfully ignorant of what Emacs does and you just destroyed all that in a single comment! MY BRAIN IS BURNING! I DIDN’T CONSENT TO THIS KNOWLEDGE! I WAS HAPPY NOT KNOWING! 😭
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 😂
I’m not an obstructionist but having been forced in to Wayland by plasma 6.8 it is frustrating that orcaslicer just crashes unless I tell it to run in xwayland and desk flow requires being on unstable to work with my clipboard and discord canary just shares audio from my whole desktop instead of from just my game and AGHHH I just want my things to work! So frustrating
Both orcaslicer and discord audio sharing work properly for me on Wayland. Are you sure Wayland is the issue?
It’s usually not as simple as is Wayland the issue or not in my experience. Wayland and the wm/DE and the application all have to get along and it gets along better with some than others. For a variety of reasons. I had an issue with gtk on niri where specific applications would not open up and I had to do a bunch of tweaking. It did eventually work, but it really should have just worked automatically. Wayland was getting instructions from the app that it didn’t know what to do with and instead of it trying to use xwayland instead it was just failing. A lot of the problems come from the fact that X11 is OLD and because its OLD it has taken the time to work out so many random little potential issues. Wayland is new enough that sometimes it just runs into stuff that it hasn’t been tweaked to work around yet. We’re in the polishing phase now tho so these will start to get worked out I think. It’ll just take time. X11 does need replacing as its convoluted as fuck but there’s a reason some people swear by it, and that is largely for this reason. It’s just got a lot of niche functionality that takes decades of dev time to fully flesh out.
The only variable I changed in testing was switching between the x11 and Wayland versions of plasma while I still could. Discord no longer prompts to provide an audio source, desktop will but the screen share won’t work once I actually start it. Orca crashes the moment I hit slice unless I add an environment variable to make it use x11 compatibility mode.
That’s very strange, they both work OOTB for me on Fedora with Plasma
They’re actually talking about this in the blog post they released this week. https://discord.com/blog/discord-linux-a-year-of-upgrades
Push-to-Talk etc. on Wayland
Global keybinds on Wayland were a long-standing pain point. Wayland (rightly) doesn’t let apps listen to your keyboard in the background. Instead, it provides a GlobalShortcuts API, but the implementation can be a little tricky. The spec says a shortcut looks like “<Control>z”, but KDE expects “CTRL+z”, so Discord figures out which desktop you’re on and speaks its dialect (send the wrong one and the portal session can fall over entirely). And since every bind request can pop up an approval dialog, we only ask again when your keybinds actually change, instead of nagging you every time Discord starts. Now, features like push-to-talk work on Linux, even when Discord isn’t focused. What’s Next: More Control of Sound Sharing
We’ve covered a lot of Linux improvements, but there’s more to do before we reach parity with the other desktop platforms. That means changing to the Wayland infrastructure itself. We use xdg-desktop-portal for screenshare, but that doesn’t provide a handle to capture app audio. Linux users have to choose between sharing audio for their whole desktop or sharing no audio at all. That’s not an experience we can accept long term, so we’re building per-app audio sharing on Wayland and giving it to the Linux community.
We’ve once again teamed up with Igalia to implement per-app audio sharing in xdg-desktop-portal, letting you pick exactly which app’s audio is shared. We’re even implementing it on GNOME and KDE ourselves to get it to users faster. This will take some time to reach critical mass across Linux desktops, but it’s a long-term investment to make a great Linux screenshare experience for both Discord and all screensharing apps. Stay tuned!
I’m not saying audio doesn’t work, I’m saying it doesn’t narrow down to just the application I’m sharing, this is a known regression with the discord client to the best of my knowledge, and as far as I know the orcaslicer crash is a mesa issue affecting just Wayland for whatever reason
I’ve had a bunch of issues with Orcaslicer and Wayland. Thankfully it’s currently working for me but the last year or so I kept having to switch back to X a lot for it.
Orca craches for me if I don’t force the language to be English by setting the LC_ALL variable
A lot of people just use Windows and everything they need works. And a lot of people like to customize things and use non-standard tools (quite common among Linux users, actually). It’s a bit silly to say “my setup works, I don’t know what people are complaining about”. Well, different people have different setups.
I don’t even know what I’m using. Whatever is default on Mint. It just works, I don’t want to think about my tools, I just want them to work. And, Mint does, for me.
How dare you say that on a meme community. This is very silly and inconsiderate of you. You HAVE to cry because someone else’s computer has issues because of decisions you had absolutely nothing to do with.
different people have different needs and wants. Some people need X11, and want KDE or Gnome