Do you daily drive Wayland, if so since when, if not when will you?
I've been on Wayland for the past two years exclusively (Nvidia).
I thought it was okay for the most part but then I had to switch to an X session recently. The experience felt about the same. Out of curiosity, I played a couple of games and realized they worked much better. Steam doesn't go nuts either.
Made me think maybe people aren't actually adopting it that aggressively despite the constant coverage in the community. And that maybe I should just go back.
Yes. I've used X11 for far too long to have any rose tinted glasses for the piece of fucking broken shit it always was. a LOT of people don't realize how many hacks, workarounds and sheer tears and duct tape goes into making the piece of shit render the smallest line on the screen.
That's also why Phoronix comment section neckbeards are so infuriating for me. They talk like X.Org works like at all.
unfinished or abandoned alternatives to xorg tools (swhkd for example)
Made me think maybe people aren't actually adopting it that aggressively despite the constant coverage in the community.
Take the community with a grain of salt; It's made up of the same type of people that say Arch is a stable distro that never has any issues.
Some distros are pushing it aggressively (Fedora for example), so use them as a more accurate gauge. If Fedora doesn't accept the proposal to start phasing out xorg, you can know for sure it doesn't have the conversion rates they're hoping for.
I mainly use Wayland(nvidia) and have been using it for the last couple of years. Only switch to X11 when there is a game that absolutely won’t work with Wayland.
As I see it both display servers are ass.
X11 just being old and crusty, maintainers don’t really wanna deal with it. Vsync in general has problems so you usually just turn it off in hope of your software running fast enough(or you could lock fps lower than display hz) so you won’t get screen tearing.
Wayland being new and has active development is great but now we have a very opinionated dev team. It took until Valve came along for them to actually listen to complaints, I guess if Valve is knocking at your door you would answer.
Some days I’m pretty close to going back to Windows, then I remember how ass windows is and I just deal with it. And for anyone saying “just buy AMD” I had a AMD card before this and I couldn’t even use Linux, it would just constantly crash.
I've got three hard problems preventing me from using Wayland (sway/wlroots) right now:
No global shortcuts for applications, especially legacy applications; I need teamspeak3 to be able to read my PTT keys in any application. Yes I know that could be used to keylog (the default should be off) but let me make that decision.
Button to pixel latency is significantly worse. I don't need V-Sync in the terminal or Emacs. Let me use immediate presentation in those applications.
VRR is weird. I'd love if desktop apps were V-sync'd via VRR but the way it currently works is that apps make the display go down to 48Hz (because they don't refresh) but the refresh rate never goes up when typing; further exacerbating button to pixel delay.
Last week I did an install of Debian 12 on a little NUC7CJYH to use for web browsing and ssh sessions into work and ended up with wayland by default. Seems to work great.
From what I have experienced, it goes great with intel integrated graphics, great with a radeon card and can be made to work with Nvidia if you are lucky or up for a fight.
I’ve been daily driving Hyprland for almost a year now I think, my only complaint is that some of my electron apps act out a little bit (Discord won’t open links, etc). I don’t game as heavily as I used to, but I regularly am running Overwatch 2 around 200 FPS with no issues, and Bauldur’s Gate 3 is super smooth as well.
I switched to sway from i3 about 5 years ago. It's easier to configure (no /etc/X11 nonsense) and it fixed my screen tearing issue. I'm not much of a gamer, so can't comment on that. Supertuxkart and browser games work fine.
Tried Wayland about 5 years ago to see what all the hype was about, with Nvidia proprietary drivers, got a black screen. Could never get beyond that. Went back to xorg.
Tried about 3 or 4 years ago, with amdgpu drivers, no black screen this time but chrome would not work and a few other programs didn't work right or at all. There may have been special builds or wrappers to work around some of those issues but I had no interest in dealing with that at the time, so I went back to xorg.
Have not felt motivated to try again as I haven't had any issues with xorg. I'm using Nvidia drivers at the moment. I also heavily use turbovnc server with virtual gl and not sure how (or if) that'd work in combination with Wayland.
I haven't had to even think about the fact I'm using xorg or screw around with the configuration in like 10 or 15 years. It just works, for me and my setup, anyway.
I'll try again once Nvidia's 555 series drivers are released which should support explicit sync. Right now it's too unstable under Wayland even though I gave it a shot once KDE Plasma 6 released.
Still holding out for desktop streaming via SteamLink to work on Wayland. I use it almost nightly to mirror my screen to my phone so I can watch what's on my PC while cooking dinner via my phone.
Daily drove wayland back in November when I finally built my new desktop and installed Nobara. It's the default and it juat worked out of the box. Have always been a windows user until now.
Games workost of the time. Good enough for me. Full team Red build inside the case.
I switched my laptop to Wayland about three years ago. AMD graphics, normal DPI 60Hz screen, doesn't really do more than run a web browser.
My gaming desktop needed more of those troublesome edge cases hammered out - freesync in xwayland, app DPI scaling in xwayland, etc. I only switched it last year.
I daily drive Linux Mint, which has only recently just now launched experimental beta Wayland support. I've been on X11 this whole time and it's been surprisingly good.
I'll adopt Wayland when Mint does, I'm confident by then it'll be good and ready.
I do have a little tablet that runs Fedora Gnome, it runs Wayland. It's okay, though trying to get the digital pen to work properly is a problem because a lot of the advice out there is written with X in mind. But.
I've used Plasma on Wayland since 5.24, and Wayland-based tiling window managers before that. No complaints here. There have been some hiccups occasionally, but it's still leaps and bounds ahead of anything X11 could offer, at its best
Sway for a little over a year now (on an AMD gpu). I switched for mixed refresh rate support and VRR. VRR requires a workaround in sway but works better in others, like hyprland, however I like sway's tiling better so I stuck with it. Also the absence of tearing in anything, ever, is worth it to me. I have two vertical displays and it was really hit or miss on X11. Sometimes GPU acceleration would just decide not to work in browsers and I'd have to restart them because smooth scrolling would turn into a stop-motion film. That's never happened since switching to sway.
Not yet. Biggest dealbreaker for me is screen sharing not working in Slack, which I need for work. Once that’s no longer an issue I will be more inclined to make the move. Given that plasma is becoming the default choice for distros, I hope Slack devs will make this a priority.
What I look forward the most with Wayland is actual support for fractional scaling. I think fractional scaling is required for a pleasant experience when using high dpi monitors, but Slack screen sharing has higher priority for me.
Been daily driving sway for over 5 years now. There were a few problems along the way. I used to have JWM and then XFCE as a back up in case wayland fails. I really only need to go into them when there's a need for screen sharing. But then, I mostly live in terminal and browser. Low graphic games I play seems okay. The most demanding one I played is probably Starcraft 2 and it plays well even on my crappy 7 years old laptop with intel graphics.
3 or 4 years, including on Nvidia machines. I'll admit it took fiddling to get working awhile ago. Nowadays I use my desktops AMD iGPU as the main display driver and offload the rendering to the Nvidia card for intense programs or games, best of both worlds.
I wanted to love Wayland but the fact is half of the apps I use are either too small in the UI or too blurry when scaled up. Until that’s fixed I’m staying on x11 begrudgingly.
I have very recently after rallying against it for years. It seems like there has been a concentrated effort lately to get it working really well, which I only have to say "about damn time" after they've been advocating it for over a decade and it still was a buggy pile of garbage at that point. Plasma seems to have done a load of work getting Wayland stable lately, and with the latest Plasma6, I'm happy with it. There's some weirdness here and there but I can handle a little bit of problems vs. my entire system slowing to a crawl and then crashing after a day or two reliably when running Wayland vs. Xorg which ran fine even semi-recently.
As soon as it works. A recent update included Plasma 6.0.2 (on NixOS unstable/24.05) which apparently defaults to wayland, but it just exits to login right away. I'm not in a mood to tinker, so for now I plan to simply wait for things to Just Work. When I select "wayland" and things work and look the same (or better) is when I'm happy to rid myself of the horror that is X11, because as horrible as X11 is, it simply isn't giving me trouble these days - my system is stable and I like keeping it that way.
Edit: perhaps important to mention that I'm using a GTX 1070.
Edit 2: I realise that I'm sort of contradicting myself with how I worded the above. I don't mean to imply that I'm not willing to sacrifice anything to embrace Wayland; just that as it stands I don't think the benefits of Wayland outweighs my ability to use this computer the way I need to.
I used Wayland for a couple years on AMD hardware and it was fine; I didn't really have any issues. Since acquiring a laptop with an Nvidia card as a gift about a year agi (it was a hand-me-down), I switched to X11 because it is still more stable for Nvidia. I will be switching back to Wayland (with Nvidia) when Fedora 40 releases. Hopefully the support for explicit sync patch will be available by that time, but if not I won't be heavily affected, as I am not playing games currently. I expect that patch to fix the black frame insertion during VRR that people have been complaining about, at which point Nvidia will be viable (for me) on Wayland.
I've been on the Wayland train for quite some time now, it's only really had issues with Nvidia because Nvidia refuses to adapt their graphics driver for it. We have to rely on the Wayland and XWayland projects to fix the incompatibilities that Nvidia is too lazy to fix themselves (like not supporting implicit sync). Luckily AMD is on top of things and has worked very well with Wayland for years now, so those with AMD hardware are better off.
EDIT: Here's a link to a Lemmy post about the explicit sync patch. Looks like Nvidia drivers plan to support it in the May 15th patch, so about a month after Fedora 40 releases.
Switched like a year ago or so, not really any difference on my AMD pc and Intel laptop. Now I need wayland for HDR on Plasma 6 so there's no way I could go back personally, as well as the great multi-monitor and fractional scaling handling.
Zero issues for me. Been daily driving it for years. Play Steam games regularly, but have not tried switching to X. Performance on Windows is MUCH better with my 1080ti playing D4, but I'm prefectly content with preformance on Linux and don't want to keep switching.
I can't use Wayland until this xwayland Nvidia bug is fixed, which is a shame because I think that's the last thing holding Nvidia users back. I tried the new Plasma 6 recently and for the most part it was great until I tried gaming and hit that bug. I tried different older and newer beta driver versions but it was more or less the same bug.
Yes, for over a year now (since early December 2022, don't remember the exact date).
My experiences with it seem to constantly be different than that of most users, because Wayland was a direct upgrade for me - I couldn't play games properly on X11 at all because they would stutter and freeze really badly even when Vsync was disabled and the game reported to be running at 60 FPS, but Wayland fixed the issue altogether for me.
...Granted, I'm on an AMD card. If I was on Nvidia it'd probably be another story entirely. :x
I have been running wayland with sway for around 6-10 months (I forget when I switched). I have a 4-monitor setup and hated the default workspace management but swaysome convinced me to switch. I heard a lot of stuff about how manual tiling is bad but I actually don't mind it and kind of prefer it to automatic tiling from AwesomeWM which I used before sway, .
I've been using it on Ubuntu 22.04 for almost 2 years. It started off rocky, with frequent restarts needed, maybe every week or two. It's been pretty solid, though I did give up on using it for screen sharing and captures, which is unfortunate timing in today's WFH world.
I use xmonad/xfce which is not available on wayland, and I have no real desire to research alternatives and config them/learn their keyboard shortcuts/etc. Its unclear to me what the benefit is from switching, from a UI perspective. Probably nothing.
But I'll probably give it a try anyway in a few months maybe, I hear they merged something to make nvidia less glitchy, so maybe wait for that to be in my distro.
@headroom Wayland has been my daily for almost a year-and-a-half, most of that on Intel/Nvidia hybrid gpus. I used to use XFCE but switched to Plasma in anticipation of the Landing of Way.
In 2017 I bought a ThinkPad with a hidpi screen, which I knew would give me trouble with Linux. Fortunately the Fedora 26 beta had just been released and was using Wayland by default (I wasn't very Linux savvy to do it myself yet). I've been using Wayland on Fedora ever since without issue.
I daily drive a ThinkPad for work running Wayland. I have one occasional problem with a commercial application that I suspect is related but I haven't bothered to prove it since it's so infrequent. Otherwise, rock solid experience for the last year since I was given the machine.
I don't use Wayland. I can. I've tried, but I went back to X. On Wayland, when I take a Firefox tab out of a window to make it it's own window, there's a pause of over a second until the new window appears. It drives me crazy every time. On X it's instantaneous.
I don't use two monitors, I don't use Nvidia. For everything else I use my computer for, I haven't found an advantage of using Wayland over X. So, I'll stay on X until I'm forced to change, I guess.
I've been using wayland almost exclusively since 2020 because x-org doesn't support multi refresh rate setups and it was driving me nuts to have everything run at 60hz. It's been pretty smooth sailing because I use an AMD gpu. I have to admit that steam is indeed a lot buggier under wayland, I try to use gamescope for every game as that fixes most problems I have with them. My hope is that proton will use wayland for most games by the end of this or next year.
My Thinkpad touchscreens were useless until I switched to wayland.
The only drawback is I have to manually edit the qgis desktop file to start qgis with x11 instead of Wayland. I had to do the same to a couple other random experimental apps, too.
Switched over to wayland about 4-5 years ago, have run into a couple of problems dealing with theming, fractional scaling and of course nvidia, but on the whole my experience has been without major issues.
I never switched. Just doesn't seem worth the hassle.
Loads of broken features and extra work shoved onto the individual compositor / WM developers. I don't care about security on my own computer, I just want screen sharing and clipboards to work reliably.
That said, I use just one (ultrawide) monitor, so even the benefits aren't really there at all.
I tried Wayland out again last week and all it did was make my monitors flash white and black over and over again. Couldn't get it to stop unless I restarted. No idea how to fix that since I can't even do anything past the sign in screen lol. Maybe one day it'll work.
I've switched nearly all my computers to Linux with wayland in the past 2 years with the last device coming over in the last couple of months.
I run a headless fedora/kde /wayland gaming desktop (with a nvidia GPU) which I use exclusively over steam links dotted around the house. That took a bit of tinkering tbh but flawless operation since. Edit: Turns out its actually still on Xorg. Still some work to do here getting this moved over. I forget why I didn't stick but must've been some combination of headless and steam link streams
I use arch/hyprland on my daily driver laptop and arch/sway on my work laptop.
For about 3-4 years. I switched after sway added support for per-display VRR which xorg cannot do still (and probably will never be able to do due to core design limitations)
On AMD it's been better than Xorg for a couple years now in my use case. No more tearing and latency issues, any games that don't play nice have worked fine with gamescope.
With HDR support finally on the horizon it'll be able to completely replace windows for me which I already barely use.
The only issue I regularly encounter is programs handling windowing strangely. Some programs like to switch themselves into my active workspace under certain circumstances which is mildly annoying but just requires that I press the hotkey to put them back where they belong a couple times a day.
Probably like 3+ years on the laptop (Intel), approaching 1 year on the desktop (AMD).
Wayland + NVIDIA is still a disaster and a very inferior experience compared to the AMD side. I would stick with Xorg if I had NVIDIA too.
Only on Intel or AMD do you get a Wayland experience that makes you go "wow I can't wait for Xorg to be dead for good". I had a very, very noticeable improvement even years ago on Wayland when it comes to triple monitor performance, VRR and vsync in general. Now that screen capture and stuff is mostly figured out, it works perfectly for me.
At this point my only issues with Wayland are related to features that haven't been implemented yet, not bugs or performance issues. And I'm more than willing to workaround the limitations and take the benefits.
I've been patiently following development and waiting to switch for 10 years, first exploring Wayland with the EGLStream patch for Weston on my GTX 580. Even back then you could feel the difference, but obviously it was also unusable other than demos.
I do, but I have to switch to X11 for work. I log in using VMWare Horizon Client, which technically works on Wayland, except that keyboard shortcuts and keys like Meta are caught by my desktop.
I have a laptop that has an AMD embedded GPU for the desktop environment, and an Nvidia GPU for playing games. I have been using Wayland since plasma 6 hit Tumbleweed maybe a week and a half ago. So far I've had zero issues, likely because I'm using my AMD graphics all the time (I haven't played games on my laptop since I switched to Wayland)
I started daily driving sway during the transition from wlc to wlroots back in early 2019 (sway 1.0), so it's been 5 years.
Note that's since I got an HiDPI laptop in 2015, I have been looking at Wayland progress from the GNOME side for a long time, but not completly daily driving it because of some annoyances.
Have been using GNOME with Wayland on a dual GPU NVIDIA laptop for 2 years. DE runs on the integrated Intel card; Steam, games, anything that needs dGPU runs on NVIDIA. It’s been a smooth experience.
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 use multiple machines. On one of the core machines, I switched to Plasma 6 on Wayland when that was released. I used XFCE on X11 previously.
It seems ok so far.
I use Sway exclusively on my personal systems. For work, I have to use Zoom, and you can't share your screen on Zoom if you're using Wayland. So I use xorg-server and i3.
Aside from Zoom, the only thing I wish would support Wayland better is ffmpeg. There are janky workarounds to make ffmpeg capture from Wayland, but they're... well, janky workarounds. If I abolutely have to capture video from my desktop, I switch to xorg-server/i3 long enough to do that then go back to Sway.
I'll switch to Wayland on my work machine when Zoom supports it. And I guess the ffmpeg thing, while unfortunate, isn't enough of a deal breaker to keep me from daily-driving Wayland.
I know I have used it since Fedora made it default in 2016. I think I actually used it a while before that, but I don't have any thing to help me pin down the exact time.
Since I only use Intel built-in GPU, everything have worked pretty well. The few times I needed to share my screen, I had to logout and login to an X session. However, that was solved a couple of years ago. Now, I just wait for Java to get proper Wayland support, so I fully can ditch X for my daily use and get to take advantage of multi DPI capabilities of Wayland.
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
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.
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.
I only use wayland on my t480 and it makes a noticeable difference on that machine, but not on my desktop with Nvidia. I have been testing it for a couple of days on my Nvidia box though. So far I've found it mostly works better than I expected but some games played on Nvidia+Wayland makes it look like my monitor is about to die with the weird flickers it does at times and under certain conditions (like loading screens it's unbearable), otherwise performance is good and seems to lock in at 144hz. Also does anyone know why there are no settings in the nvidia-settings app under Wayland?
Full AMD. KDE. Only one issue. I RDP into my work laptop, and sometimes I get weird artifacts on the screen until I minimize/maximize. Everything else is flawless
Yes, I have Wayland on both my gaming machine and my laptop. I switched for security reasons (i.e. client input isolation). I think Wayland compositors tend to be buggier than X WMs/DEs, just because they are newer/more immature, and there is less native support for it. But some native Wayland-only programs are really good, like Foot is pretty much the perfect terminal emulator for me, being lightweight and fast but with sixel support too. It pretty much has every feature I want to use (except ligature support but that's not super important to me) without any of the features I wouldn't use (looking at you Kitty).
However the downside is the occasional program that just doesn't work on Wayland, like JetBrains IDEs, which are one of the few pieces of proprietary software I voluntarily use. JetBrains IDEs use a bunch of X hacks so they have some buggy behaviour on Xwayland. I really hope JetBrains hurries up with their native Wayland support, especially since so many DEs and distros are moving to Wayland by default now.
I also wish there were more tiling compositors out there. It seems to just be Sway, Hyprland, River, DWL, and QTile (which has a Wayland option, which is very cool). Of which I have daily driven Hyprland and River and been happy with them. I know there's others but they seem pretty obscure or abandoned and not something I'd be looking to daily drive. On X there are so many WMs for every possible use case. And of course the popular X WMs are pretty mature software; I don't remember many breaking bugs when I was on i3, but Hyprland and River are in very active development which means a new update can mean bugs of varying levels of annoying/need a workaround/need to downgrade.
I don't feel like fighting my OS. It locked up every time it went to sleep and I switched to X and the problem went away. Maybe I'll try again but why bother? Everything is working fine for me.
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.
I've been using Hyprland for about 2 years. I did have some issues with screen sharing (teams, discord) and some steam games (non native, with proton) need some extra launch parameters, but they all work now. Over time I was able to fix all the little issues. For me Hyprland is a daily driver, but I like to tinker. I can see how this is not for everyone.
Not yet. I'll give it another go when I get Plasma 6 (I'm on Debian, so either I'll switch to Sid or just wait a while).
Last time I tried it, it mostly worked, but mpv had some issues and missing features on Wayland. I haven't kept up with the mpv developments since then so I'm not sure if that's been addressed upstream yet.
Since Fedora 35 or more specifically rawhide in the lead up to Fedora 36, so late 2021. Plasma Wayland session, it had some rough edges, but I found it tolerable. I understand some people wont put up with it, or find workarounds and that is fair. Its been good to experience it as it has matured.
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 am a relatively new Linux user, 3 years (almost 2 years dual booted with Windows and now only Linux) and I started using Wayland after approx 2.5 years ago. I used it on my ideapad gaming with 3050etx and Intel igpu and prior to that I used some hp laptop... With gtx 980mx. I used manjaro then arch and then fedora for the last yeae mostly and I haven't encountered any issues with Wayland whatsoever
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.
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.
Generally I have when I use Gnome or KDE on Linux, though I have started to prefer MATE, which doesn't have Wayland support yet afaik. I also started using FreeBSD on one of my computers a bit more, and I believe Wayland support is still a bit wonky on that right now. But as soon as Wayland support is there I'm definitely switching to that on the daily.
Every update of plasma I switch to Wayland so far my record is 1 week before running into a deal breaker issue.
Though Plasma six is so close to working for me. The only issues I'm getting on wayland is flickering in games, an issue where some windows don't show up on the task bar, awful screen tearing when using two monitors of different resolutions, keyboard lag.
I would like to, but I'm running Arch with Cinnamon, and that desktop environment only has an experimental version of Wayland implemented. I've tried it, and it's too buggy to be used as a daily driver.
I've been dailying it on my desktop for a couple of years now (I want to say since 2022 but I forget exactly... there was a Plasma release where a certain feature finally became realised on Wayland and I switched then). Been running on my laptop for much longer, where I use GNOME. It's been great, but I don't have any Nvidia hardware.
I couldn't get the trackpad working right on X (why tf is acceleration on by default?), tried switching to Wayland in the first few hours of using Linux, and haven't had significant issues since. At that point I had no reference on performance, so no way to tell if X would be better.
There's maybe one bug that causes an unrecoverable GPU hang when using certain applications, but that may have been fixed in the kernel already, and I just need to use something newer than 22.04 LTS.
I use Wayland on my laptop running fedora 39 kde spin and it mostly runs fine. When I browse gifs in discord the screen flashes white and I can't maximize jellyfin on connected TVs but other than that no major issues.
I've been daily driving it on some devices for maybe 6 months.
My only showstopper was input-leap, but I have not had to use it for two months. So I've gone all-in since. It works better in every sense - except for the input-leap thing.
I’ve been using it ever since Ubuntu switched over. No major issues, though I have to launch Calibre (the ebook manager) via the command line with a special environment variable because the developer is anti-Wayland. I’m looking for alternatives.
I have a laptop with integrated Intel graphics and a desktop with Nvidia graphics. I use Wayland on the former right now as of KDE 6. I have noticed some odd behaviors, but overall it has been fine. The latter, however, just boots to a black screen. I have neither the time nor the desire to debug that right now, so I will adopt Wayland on that machine when it works with Nvidia to a reasonable degree of stability.
I tried Wayland many times in the past ~6 years, usually with Sway (but I tried most other compositors, other than KDE's), but I always came back to X11 (using cwm).
Around two months ago I started using river, and I think I'll stick with it. There are enough Wayland protocols which now exist (and are supported by river) that using a minimal compositor feels pretty similar to just using a window manager on X.
I've been using it since about spring 2022 and it's been way more reliable than X for me. The only times I've had trouble was one computer where I was missing one of the pipewire packages I needed for screen sharing and another time I tried to run it on a 20 year old Radeon X1600, but both of those were my fault and not something a normal user is likely to encounter. For context I've used Sway, Hyprland, GNOME, and Plasma although the usability has been the same between all of them.
It hasn't really caused game breaking issues for me, however it is nice that the few nit-picks have all been resolved.
I get the sense that the majority of people use it on Workstations, there is just a vocal minority that resists the change. There are so many academic and enterprise users just using distros in their default state Wayland and all.
Ye, since Plasma 5.24 I think. Used to occasionally switch to X11 for competitive gaming, but as of Plasma 6 their Wayland compositor supports fullscreen tearing, so now I have no need to use X11 anymore
A couple years(ish) on intel-only laptops. I run it with KDE Plasma. I only think about it when I see a thread like this one.
For me it Just Works™. I recognize that being intel-only may be a contributing factor, and my certification of Just Works™ is not to imply dismissal of any problems others may be having. 🙂
I use it with gnome on nixos without any problems AFAICT. Had the explicit sync issue with Nvidia initially but I ended up buying an rx6800 to use as the host GPU when I set up win11 with KVM. Been completely fine since.
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.
Plasma 6 fixed a lot of issues I had with Wayland, mostly multi monitor, but I've been using it since steam on X11 would cause your entire desktop environment to freeze up consistently every time. I read it was because steam was constantly pinging your display ports to see if there was another monitor connected, but I don't know how true that is. Moving to Wayland fixed that probably because of xwayland
I daily drive wayland with nvidia and I play games modestly. I have Xorg installed as backup for when issues happen, but it's been pretty rare in the last couple months.
I've been using it since Plasma 6 came out so about 3-4 weeks.
Overall, it's been a very negative experience for me. The main problems have been:
Random scaling issues in apps: some apps show a slightly smaller cursor, other show a poorly upscaled one, others have random rendering issues like lines remaining on the screen after an option is no longer highlighted (gimp, libreoffice, many others), some apps have random flickering of parts of the UI, some apps no longer scale at all or are scaled twice. Plasmashell itself has blurry icons on the desktop but all other KDE apps don't. I know fractional scaling has always been problematic, but it has gotten worse to the point of being almost unusable
Random crashes of GTK apps when using the wayland backend. Some GTK apps don't even start and segfault immediately with a wayland error in the terminal
Some apps like okular and libreoffice lag like crazy or outright freeze when scrolling
Some games not capturing the cursor properly (Proton)
Inconsistent font rendering, some fonts look fine in some apps and atrocious in others
Issues when resizing or moving windows, some times they "jerk" off the screen or resize to a very tiny window and I'm forced to use key combinations to resize them again
Random issues with window decoration not appearing in some apps but randomy appearing for things like context menus
This is on a full AMD system with Arch Linux, the latest kernel and mesa-git. I hope for KDE's sake that there's something broken in my installation because I can't believe the KDE team released Plasma 6 in this sorry state.
Yeah, I've been using it for a few years now. Not really given me any issues so I don't have any reason to use X again, but my use case is pretty basic 🤷
Got hyprland running on the macbook, have tested it out on desktop. Not quite the daily driver, plasma 6 on X is still the norm there, but I think as soon as synergy works in Wayland I’ll make the switch everywhere
I tried for a bit and it was great, no complaints. However, I was having issues getting NixOS set up as quickly as I would like, so I went back to Pop!_OS. I'm looking forward to the next release of Pop, which will have full Wayland by default.
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.
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.
I could switch tomorrow if I could do my current setup:
Tiling Window manager (sway?)
simple status bar to output text from a script with clickable applet icons (waybar?)
the way to show/hide windows on a button press - I have a script that I use to quickly toggle 3 dropdown terminal windows
Last time I tried Wayland in December, I had issues with waybar not supporting clicking tray applet icons. Also I've ported my dropdown terminals script to support sway - and it worked half the time, like, literally every second key press was ignored.
On one hand I have X session that currently has no downsides for me, on other - wayland that has no upsides. Tell me, why would I switch?
Been running Wayland for 5 years on my development laptop (sway, Intel GPU, blacklisted the nvidia gpu). At the start I've had a couple of issues, nothing too bad. Haven't had any issues for over 2 years.
Switched to Linux on my gaming PC about a year ago, KDE plasma on Wayland but do most of my gaming from a steam gamescope session.
Very happy overall with Wayland, glad it exists. Sharp text on a fractionally scaled display for reading code was just too compelling at the time and it only improved.
I had it on a test system and Chrome/Chromium wasn't happy. Slow af. Dunno if it had an impact on Firefox, but that used a lot of RAM and was very slow when sharing the screen.
At least Waydroid worked flawlessly 👍
For now, I'm back on X11 where I game. I'll just wait for it come by default on major distros ("stable"), wait a little longer (stable for real) and then switch once nothing on my system needs "XWayland" or whatever. wine does AFAIK, so at least due to that, no Wayland for me.