Maybe this isn’t the right place to ask, but does anyone know why Wayland just started shitting the bed whenever I have multiple monitors connected aftera kennel update a couple weeks ago? I’m running Debian trixie with KDE Plasma and using the latest NVIDIA proprietary driver with a RTX 3050.
Improper driver vaccination leads to kennel cough
Too bad Wayland is glacially slow when taking screenshots next to X11 (Had a python script taking screenshots of a Minecraft window and doing some image recognition at 60 fps on X11 and …3 on Wayland. I now need to rewrite it to stream the whole desktop as a webcam for the same thing.)
My uneducated guess is maybe it should be written in C instead of python. On top of that, screen recording via OBS works great on Wayland, so Wayland can’t be fully to blame.
Most likely, it’s Wayland throttling screenshot demands. Obs actually stream the desktop instead of grabbing it.
Is it not an option for you to just use Pipewire, or is that what you mean by a webcam? It’ll be somewhat of a refactor but should still be quite fast compared to screenshots even on X11.
Did you know there is no accessible documentation to do so with pipewire? The best I could find was an uncommented python source and a technical wiki that skips the basics. V4Lloopback is far simpler. And shorter.
How can you miss Cosmic, written in Rust by system76 guys? It’s the most modern desktop there is for Linux.
Not as full featured as plasma but it’s matching Gnome for sure.
i thought compiz fusion is the most modern
Beings back memories. :)
Oh its the best, it handles workspaces in external monitors quite well (i dont know why GNOME chose to show same workspaces number on both primary and external diaplays)
Really? Workspaces on external monitors is my main complaint about GNOME. Does Cosmic gracefully handle disconnecting an external monitor, i.e. keep all the windows on their respective workspaces instead of randomly scattering them?
Does Cosmic gracefully handle disconnecting an external monitor, i.e. keep all the windows on their respective workspaces instead of randomly scattering them?
I don’t know the answer, but how are you supposed to access windows that are located on a disconnected screen?
I love and use Wayland and KDE but MAN my best remote tool still hates wayland.
Yup. RustDesk for me. When prompted on the PC I tried giving access to all screens imstead of one, now it can never “'get display info”. That plus issues with Chromium and CEF made me go back to X11 and alter the setup
Wayland still lacking adoption and functionality for basic and essential needs after more 15 years and with such budgets, really speaks volumes about it’s architecture and decisions.
Like what?
Wayland still lacking adoption and functionality for basic and essential needs after more 15 years and with such budgets, really speaks volumes about it’s architecture and decisions.
VMware Player still can’t copy and paste properly between the two machines on Wayland. How on earth is that affected by the desktop compositor?
One problem here lies within the architecture of wayland that it forces every DE/WM to implement their own compositing and many other things. So more and more fragmentation and harder for both WM developers and app developers.
In 2012 I had a job that centralized all of its email communications to a server in the closet. Instead of installing apps, the IT department used X11 forwarding, on Windows desktops, to open remote Thunderbird on everyone’s machine. The linux box ran postfix, dovecot, maildir and thunderbird all in one. It did not work well lol
Is there a single, unified product that I can use for remote desktop access to Linux running either X11 or Wayland, Windows, and MacOS? I provide support for family that are both Windows and Mac users (and one Linux user, yay!). I’d like a single remote desktop solution for everything that is easy to get Windows users and MacOS users to install. I’ve been using AnyDesk, because ninite.com has an installer for it, so it’s a low bar for low-skilled windows users, and it’s easy enought to get installed on MacOS. But incoming Anydesk connections don’t work on Wayland. Does Rustdesk handle incoming Wayland connections these days?
I’m on Wayland (KDE), Rustdesk works beautifully. No complaints.
The problem I remember having was getting login screen access on a wayland remote machine. I could attach to a running session, but couldn’t log in to a new one. If they’ve fixed that, awesome!
Are you self-hosting a Rustdesk server, I remember the performance of the public server to be pretty spotty.
Just try it. Rustdesk works really well, but I haven’t tried it on Wayland. If you already have a wayland machine, it won’t do harm to try.
I have tried it in the past. It was great but I could only connect to running wayland sessions. It wouldn’t handle the login screen. Also the public server performance was pretty spotty, but I could always self-host the server.
I just use it in an already logged in desktop session on x11, so I have never felt a difference in terms of servers or used login functionality
X11 really needs to be put down. Its had its time
Make amazing things that can’t be replicated on X. Notably the list of things people think only works on Wayland is long and wrong. Right now there is a vibrant window manager ecosystem and HDR.
Alternatively wait until new versions of basic apps no longer work on X. Although it would be hilarious if we got a comparability layer to run wayland apps on x
Unless there’s a replacement without losing functionality, it’s going to be hard. I waited years for the switch to let wayland be ready. I thought it was when kde defaulted to Wayland, but nope. Once every month I run into issues related to Wayland. Or I run into not being able to implement certain things in Wayland that were super easy in x11.
I mean yes we could force the transition, but for many people maintaining their workflow and features are important. That said, I would want new applicationd snd libraries to support Wayland.
Just give it another 10 years and a few hundred thousand dollars of budget and it’ll be finally good (it won’t)
I can’t get by without xdotool. Wayland intentionally breaks this and calls it security.
What deficiencies does ydotool have for your workflow?
Sending keys to non-active windows without activating them.
It looks like ydotool also needs root, and has weird interactions with non-qwerty keyboard layouts.
I’ve also been using Autokey lately which has similar blockers with Wayland.
It’s abandoned it’s GitHub page talks about rewriting in JavaScript in 2024. X actually gets security updates.
I’m in the same boat. Looks like there is a whole bunch of alternatives: https://superuser.com/questions/1032270/wayland-alternative-for-xorgs-xdotool
The seem to have their own issues, which isn’t great, but so does xdotool.
Now that it at least supports my multiscreen, multi UI scale setup, it feels like Wayland is what all DE’s want to be. It’s so smooth and fast, and can always impose it’s will on all the windows. What do you mean this window won’t minimize and always stays on top?? WAYLAND SMASH. There I fixed it.
It feels very luxurious and decadent to have a DE that is so frocking good and reliable.
except at the faa
Aaaaand… GNOME still haven’t implemented server-side decorations.
Yeah GNOME is sabotaging Wayland now more than anything
They can’t keep getting away with this!!
I love the benefits of Wayland (display scaling, negative coordinates, hdr) but wish it had anything remotely as useful as xrandr (I have a 768x1024 16:9 plasma tv).
what are the benefits of negative coordinates?
being able to more easily have a detachable monitor to the logical left
wrandr?
I’ll give it a shot, but I doubt it has a way to do seperate horizontal and vertical scaling, or rotate the screen 17.5° as a joke
There’s also the trick of xrandr of using --panning and --scale for a larger-than-physical desktop you can edge-scroll around in. Wondering if that is even possible in wayland?
iirc there is some joke compositor that has two axis scrolling
Wayland is so smooth. When I go to my friends house and use mint I’m instantly reminded how shit x11. Screentearing on the desktop, cmon what year is this.
If you’re getting screen tearing, it’s not X11’s fault. It’s the graphics manufacturers putting speed over stability.
I had an old Nvidia card that I never had a problem with under X11. The moment I upgraded to an AMD card, screen tearing, screen tearing everywhere.
To fix, you generally need to slap a small config file into /etc/X11/xorg.conf.d that tells the graphics driver that slow and steady wins the race.
The AMD solution literally contains the line
Option "TearFree" "true". Ridiculous.Link to one of many sites providing the full solutions: https://linuxjunkies.org/guides/fix-screen-tearing-on-linux
You need screen tearing for gaming. Wayland allows screen tearing on games but sync for everything else configured with a single check box.
If you’re getting screen tearing, it’s not X11’s fault. It’s the graphics manufacturers putting speed over stability.
This is the central part of why wayland adoption has been difficult. With X11, the idea is “the buck stops here”, with wayland it’s “this is out of scope.”
Now, in terms of managing a cleaner project, which is wayland’s goal, that’s fair.
However, in the practicalities of seamless adoption and not breaking shit, it’s not being the “drop in replacement and new standard” it’s hoping to be.
Wayland is so smooth
My plasma desktop is very noticeably slower and choppier with Wayland. The most visible example is when I switch workspaces and instead of the animation taking a fraction of a second it takes a second or two. It honestly feels like my laptop (which isn’t that old) was aged a decade by simply switching to Wayland.
I moved from X to Wayland when Fedora dumped X, and the first weeks were a pretty unstable experience (mainly because the Nvidia drivers still had some issues after implementing explicit sync), while performance never was an issue. Nowadays all of those problems are solved. Desktop streaming works fine with both pipewire and through whatever Sunshine uses, game FPS are comparable to Windows with some variation depending on title, and my desktop experience is buttery smooth.
I thought Cinnamon finally added Wayland support now? Anyway I had the same experience. Using Mint is how I realized 90% of distro recommenders on reddit and Lemmy have 0 fucking clue what they’re talking about
The Wayland session is still to buggy to enable
They added experimental support and i think they made it mostly functional in the upcoming release but dont quote me on that last bit
IIRC support is no longer experimental, but might still not be quite up to par with X11. Although by now I’d expect it to be really close if not already there, it’s been a while since I last checked.
It’s not great though. I’m running Kde Plasma for now, and it’s so much better.
Why is GNOME and KDE against X11 in this meme? Did they announce they are going to drop support for X11?
I’m surprised there are so many comments about the user experience for Wayland and X11. Unless you are programming for Wayland and X11, or are doing a lot of remote connection, you will not be able to tell much of a difference between the compositors other than package support differences. Im glad that there is an effort to move away from the X11, working with xlib is pretty archaic.
Im glad that there is an effort to move away from the X11, working with xlib is pretty archaic.
I find working with xlib to be simpler and easier for creating window managers than libwayland-client imo.
IIRC Gnome dropped support for X11 and KDE wants to fully drop it on Plasma 7(They made X11 KDE optional).
Did they announce they are going to drop support for X11?
AfaIk, KDE dropped X11 support of the Plasma desktop some month ago.
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
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.
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.
I’ve even forgotten that I’m on Wayland. Everything I need works
different people have different needs and wants. Some people need X11, and want KDE or Gnome
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?
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 WaylandGlobal 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
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.
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.
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
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.
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
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.
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.
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.
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.
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.
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 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 😂
What is the origin of this meme? Why do they want to kill this poor man who presumably lives there and just mowed the lawn?
Apparently the original:
The edit looks less edited than the original.
Right? Knives look more natural than clothes unmoving from a package, wayyyy to much cornstarch if the shirts are holding that well.
They also grip the clothes weirdly, while it’s right for a handle.




























