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.
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.
Maintainers don’t want to support it? Because the code is shit and they developed a new product Wayland. I mean when the people who develop it think the code is unmaintainable.
I’ll adopt it when it’s ready.
For NVIDIA users, that’s the right answer. For AMD users, it’s already ready. No problems here (6700xt)
Yeah, it was ready for my old AMD machine. My new Nvidia box…nah.
But since I’ve switched to XFCE, I don’t need to worry so much about new-fangled things like Wayland…for now.
It’s not just about hardware compatibility. It has to be compatible with existing workflows, and it’s currently very limiting.
On nvidia, there are still too many edge cases involving Wayland that are just crippled. Orca slicer doesn’t work for me for example, you are completely missing any of the 3d accelerated graphics in there.
On the other hand, the AMD 7x00 series have different kind of bugs, with ring0 errors leading to full resets.
I think once nvidia drivers are squared out (the proprietary ones) it will be smooth sailing.
All AMD here and I can’t have it as a daily driver. So many issues made me hate my PC. Back to X11.
Which DE are you using? I’m using KDE.
Plasma 6. I’m going through a very busy time at work at the moment. Once it’s done, I’ll just reinstall the whole system and see if that helps.
The first and the best answer
Full wayland all the time for probably 2 years now
Yeah, me too. Whenever Fedora made the move to Wayland by default for Gnome.
Since I switched to AMD about a month ago. Literally every naggling issue I had with NVidia is gone. Only complaint is that I didn’t switch sooner.
Why I’m not using it:
- worse performance (Nvidia)
- couldn’t get screen sharing and recording to work
- 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.
Started my Linux journey with Wayland 1.5 years ago and haven’t used X11 at all.
Oh, you’ve been missing out on a lot of “fun” 😄
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.
That’s because their mid-2000’s setup with single 1024x768 screen works just fine with compositing disabled, 24bit color depth via VGA connector.
I had to switch to Wayland the moment I tried to run simple 4K@60 on my old RX570, and Xorg was just refusing to set the mode, or produced some colorful vomit garbage when forced to do so, no matter what. And Wayland (just like Windows) simply worked.
Was it perfectly ready back then? Heck no. Is it ready now? Maybe not for everyone, but it’s getting there and time is telling us that the missing parts on Wayland side are fixable.
Criticism is viable to some degree, though. Because from the very beginning there were certain assumptions made, and creators of the base protocol didn’t care about real world use on desktop as much as they cared about the security model, it takes a lot of time to solve some of those. The development is slow and there are always some gaps here and there, but I watch it long enough (17 years) to know that to some degree it is like that with the entire ecosystem, let alone Xorg that no programmer wants to touch anymore for anything but simple bugfix or security patching.
I’ve used it for about a year on a laptop with an 8th gen i7 and Intel graphics. It works well there.
I don’t. And I will when it actually fucking works.
What doesn’t work?
When my DE, Budgie, supports it. I’m not too bothered about using it, with a beast monitor and a high-end PC I hardly notice the X.Org quirks.
I’ll take it as when Budgie is ready to ship a full Wayland-only experience, I’ll be ready to use one.
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?
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.
input-leap
this software has wayland support already https://github.com/input-leap/input-leap/issues/109
Cool.
Last I checked kwin was still waiting for some protocols to become available. I’m sure it’ll be good to go if and when I need another Mac on my desk to synergize.
There was another server that already supported wayland/gnome, but the scrolling was too wonky for my nerves.
deleted by creator
Barrier hasn’t been updated in two years, so I wouldn’t expect that to happen. Input-leap is a fork that is maintained and updated, and has had wayland support added.
deleted by creator
no problem!
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 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.
They didn’t make it the default until 2021 https://fedoramagazine.org/announcing-fedora-34/
That’s why it felt very early to have used it before it was default, I mean before 2016 felt too early for me… But it was way before Covid, so I’d say around 2017.
