I switched to Wayland to get discord streaming with audio working but now Steam remote play has issues capturing some windows unless I open Steam with the -pipewire option. Other than these issues with video streaming it’s been almost the same ir better than x11 on my AMD machine.
Linux
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
Tried wayland but it doesnt work on debian stable + kde + nvidia hickup-free yet. I will switch when a) the fixes come to stable and b) a need to switch arises.
I've been daily-driving hyprland for the last couple of months and it's been very smooth sailing for me. I configured it to very closely resemble my bspwm - polybar config though it was easier to set up. I have to say that in 99% of cases the experience is equivalent. You also get to run Wayland exclusive applications (though those aren't really common).
i'll probably jump the next time i change window managers or distros... i havent a reason to currently
I am dependent on a couple of programs I run via wine - and wine still isn't directly compatible with wayland and buggy with xwayland...
When network keyboard and mouse sharing works. It is the only thing stopping me going full Wayland.
Are you using synergy? I have that but don’t use it anymore since they changed their code and I began to feel like a beta tester, but your point stands nonetheless. I always use Wayland on VMs but my main machine is X11 because I keep running into edge cases that make using Wayland inconvenient.
Been using it since plasma 6
Niche, I know, but I'm waiting on full functionality in Input Leap (Barrier fork which was a Synergy 1.x fork). Right now it sounds like it's 90% of the way there but lacks clipboard sharing. I'm running Wayland on my desktop, but this soft kvm is pretty fundamental to my workflow on my laptop.
I've been using Sway on and off since 2020. Wayland always worked well as long as it supports the specific use case and the apps are doing the right thing (e.g. pipewire, portals, no Xwayland).
VRR with multiple monitors and HDR are likely the biggest reasons to use Wayland, as most other improvements are less noticeable. E.g. Sway always felt more responsive to me than i3 + picom, even with a single monitor in 2020.
If you have issues with applications not working well on Wayland, either wait for proper Wayland support or ditch them. For Steam this'd likely mean stay on X.org.
About five years with Wayland now. Started with sway and now running KDE Plasma 6. It is snappy, simple and definitely so good I will not miss X11.
(I also think systemd is cool, you can crucify me now)
No, I see no benefits
Yes. Since 2013 or so, if I remember correctly. Gnome 3.10.
I've been using it since it felt usable enough in GNOME to me. Around 2015-ish, give or take a year. GNOME leading on Wayland support is a big part of why I switched to it from Xfce back then. Nowadays KDE and others have plenty good Wayland support too (better in some ways like allowing server-side decorations and global shortcuts) but I just haven't felt like trying to properly experiment to see what I like.
I've always avoided Nvidia on my desktops. Stuck with either radeon or intel and never had any exceptionally big issues with them on Wayland. Though other things like hardware accelerated video decoding have had a history of being spotty on some drivers/GPUs.
I tried it a few times on different hardware. There were weird lags, freezes, crashes, latency, artifacts, flickering (once I had to reinstall the system to fix it), no cursor in games etc etc so no thanks. It doesn't work for me. Maybe it's possible to fix if I spend a week in the terminal but ehh idk. It's just not ready for me I guess. And I didn't even have enough time to find compatibility issues. I'm a little bit afraid that by the time Wayland is ready, a new system will already be required lol. It's getting better though so probably it will be ready for business/production in a few years idk. The only thing I can definitely tell is that it must not be the default on regular desktop distros now. Wayland may be good but it's not mature. Switching to it on the login screen is a 3 seconds task and it fixes so many issues, especially on older hardware
For my home workstation running Debian/Bookworm I started running Wayland-Plasma when Xorg mysteriously refused to work after replacing my video card. Wayland just worked and really had no issues for me so while I'm sure I could have solved the X11 problem I didn't have a real need to.
I also changed my laptop to Wayland-Plasma more recently. A problem I had was in setting up the right modes for external monitors on laptops but that seems to work OK now. Generally things just work.
When I can use mtp connections with cli apps instead of only gui apps
Gsync doesn't work yet so... Not yet for me.
Also, they need to fix the load apps in last location like X has
I'm on AMD, so I've been on Wayland since around 2021. Haven't really experienced any issues.
Since I mostly run Debian with KDE, I've been using it a lot since KWin is on its stable repo.
First time I really use it is on Gentoo, which exclusively runs Plasma. Since it's rolling-release, it didn't take too long to be available.
I've been moving this build from one computer to another, they all work fine. Currently it's on a Thinkpad W530. Got some problems with multi-monitor that never happen under X11. Thankfully after I replace the firmware with coreboot, and opted for dGPU only, I never encountered any issue.
Currently, what keeps me from fully ditching X11 on KDE is the buggy SDDM support.
On the other hand, I've been using Linux Mint on my work PC. As you may have known, neither Cinnamon and XFCE has it at the moment.
About a year ago I moved to Hyprland & Wayfire for my NVIDIA & Intel boxes. Moved NVIDIA to Radeon a few months back and had mixed results.
Recently tried Plasma 6 for experimental HDR and am impressed.
I'll probably make the jump when Plasma 6.1 releases with their "real, fake session restore" functionality, was hoping that would make it in to Plasma 6, and I am daily driving Wayland on my laptop now, but I kinda need my programs (or at least file managers and terminal windows) to re-open the way they were between reboots.
Thanks to kscreen-doctor, I've been able to port most of my desktop scripts that I use for managing my multiple monitors to work on Wayland, and krdc/krfb have been a decent enough replacement for x11vnc or x2go for accessing the desktop on my home server/NAS remotely (I know, desktops on servers are considered sacrilege, but for me it's been useful too many times to get rid of at this point).
Where Wayland currently shines for me is VR, Steam VR works better, and more consistently on Plasma Wayland than X11 at this point, which is probably more of a Valve thing than a Wayland thing. When I first got my Index, X11 worked fine, but there have been times when Steam VR on Linux being "broken" has made the news on Phoronix/Gaming on Linux, but still worked fine on Plasma Wayland (which seems to be where Valve is doing most of their SteamVR Linux testing as of late).
As an end user, I do wish that the Wayland specification was organized better, because as an outsider, it seems a lot of the bickering that goes on has more to do with everyone having different end goals. I think if they would split out the different styles of window management to have their own sub-specs or extensions and then figure out what of that could be moved into the core after everyone has built what they need would be better than their current approach of compromising their way through every little decision that doesn't always make sense for every use case. Work together when it makes sense, but understand that there are times when that doesn't make sense, and sometimes you can't please every stick in the mud, and are going to have to do your own thing without them. I do get the appeal of doing things right the first time too though, even if it takes more time. But it seems like usability is always the thing that gets sacrificed when compromises are made.
KDE Wayland is an epilepsy inducing flickerfest with my Nvidia GPU, so it's off limits until they fix it. Games usually run fine on X11, but one exception I noticed is Noita, it runs like crap on X11, and runs great on Wayland for some reason.
If you don't know, the fix for that is here: https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/967
Whenever Nobara moves to KDE 6, I'll probs switch over to Wayland. Likely sometime this year.