Wayland has a bright future ahead: The move from Xorg to Wayland had a rough start, but things have improved, and there is an exciting roadmap for the future.
-
Now consider that most enterprises are about five years behind that. Takes a few years before what’s available in Fedora trickles down to RHEL, and a few more years before it’s rolled out to clients. Ubuntu is on a similar timeline.
The fixes you got two years ago might be rolled out in 3 years in these places. Oh, and these are the people forking up much of the money for the Wayland development efforts. The current state of Wayland if you pay for it is kinda meh.
Those are terribly run enterprises. I work for a giant multinational that is widely considered to be obsolete tech-wise ... I'm on fedora 42 on my work laptop. The team responsible for vetting, security and customising the deployment was ready day one.
Its 3-4 people catering for the ~2-3000 users that use the os internally.
I get the need for stability and repeatability in enterprise. I'm a sysadmin for more than 20 years.
That 3 year timeline could maybe move up a bit, even windows deployments are more or less up to date. Why would't linux be?Lastly, the more resistance to wayland, the longer it will take for it to reach a level of polish to where even you would aprove of.
When the switch became inevitable (distros defaulting, dropping x11), I installed it, lived with its crappy issues back then, reported said issues and moved on with my day.
-
This post did not contain any content.
Yeah it's at the point where i'm wondering if i still even need xorg. I'm still keeping it around just in case for now, but i could very easily purge it from my system anytime since i'm using nixos and all my xorg related settings are in a specific file. The main pet peeve i have with wayland is gaming related, and should hopefully improve when wine and proton go native wayland. I have a dual monitor setup and games always choose the wrong monitor by default, which means i can only use the resolution and refreshrate of the secondary monitor. I have a keybind to set the primary xwayland monitor with xrandr, which solves the problem, but it is a bit hacky. I also need to toggle vrr on and off with a keybind because it causes flickering on my monitor. It's a bit annoying but atleast it works, on xorg you can't even use vrr with multi monitor to begin with.
-
god i wish. half of my X11 apps don't work, some that used to keep breaking without reason.
Steam works through the XWayland compatibility layer
unless you use an environment that doesn't support XWayland, like niri. xwayland-sattelite used to be the easier route in that case but that seems to be broken now.
Issue is already closed though and might have more to do with xwayland itself it seems. Also fwiw, i just tested steam on niri with xwayland-satellite a few weeks ago and it worked just fine.
-
This post did not contain any content.
I dunno why but I can't even log into KDE when I select wayland. The screen just turns black and unresponsive
-
The gnome implementation that I'm forced to use is god damn awful. This whole eventbus implementation is so bad, it misses events and doesn't always register key-up, when I'm switching workspaces. I do it a lot, and the key gets stuck spamming the same letter, because it didn't register key up!! Hell sometimes it doesn't register keydown, super annoying when writing passwords.
Random crashes of gnome happens more often than I would like to admit, and all that you've been working on is gone aswell. What a garbage design, why the fuck should the wm own the processes, I swear the wayland people live on a another planet.
And the whole permissions thing to ensure privacy, mf this is linux, stop making me do workarounds for shit that you won't allow, because you haven't implemented the correct support for it.
I'm running Ubuntu 24.04, thing fucking sucks, I'm forced by work. Dude x11, just worked, like Wayland solved anything at all.
hard disagree about the permissions. If I want to run closed source programs like games, discord, zoom or whatever, I like knowing they can't log all my keys, take screenshots or even run their own version of windows recall without my explicit permission
-
I dunno why but I can't even log into KDE when I select wayland. The screen just turns black and unresponsive
Something similar happens to me on my desktop (debian 13) - it goes black then brings me back to the login screen. But in my case it's probably the nvidia drivers (proprietary). Not certain, though. Still happy on X11 for the meantime.
-
hard disagree about the permissions. If I want to run closed source programs like games, discord, zoom or whatever, I like knowing they can't log all my keys, take screenshots or even run their own version of windows recall without my explicit permission
yeah. the thing with the stuck keys and crashes is not normal. I've never experienced it (though I wanted to restart the window manager once), but also I'm using KDE
and you know what? if you still need x11 for some things, log in on a 2nd TTY to another user with an x11 session. you can then switch the active TTY to use the other. Though I admit, I have no idea how the 2 users' sound system work together
-
"I set my house on fire damn why did my house burn down its the builders fault."
at which part did they set the house on fire?
-
As an average desktop user, I've run into very little pushback on Wayland. Its made huge leaps in a short amount of time.
until you start using it and screenrecords dont work, multimonitor setups work once and then fail forever...
systemd,wayland, unity, ubuntuOne and all that stupid shit can right f off. -
hard disagree about the permissions. If I want to run closed source programs like games, discord, zoom or whatever, I like knowing they can't log all my keys, take screenshots or even run their own version of windows recall without my explicit permission
hard disagree. if your software is missing baaic functions, you shut up about roles and permissions or even force that crap on others.
-
Not sure if it was a kde issue or a wayland issue, but I tried it last year and had trouble with cursor locking.
Virtualbox had issues with the input being intermittent, and my mouse would move off the screen while gaming.
It might be fixed now, but I don't plan on trying it again for another few years, because what I'm using works for me.
the cursor locking still happens in a handful of games for me - most work perfectly fine but sometimes i do end up running something with gamescope with the --force-grab-cursor argument to fix it.
this is when running games with either steam or wine/bottles/lutris.
strange that it happens in virualbox, i would think it "virtualizing" an entire display would fix issues like that. does virtualbox itself "grab" the cursor, or allow it to go off the screen by default? sorry i don't really know virtualbox, never used it much
-
Yeah it's at the point where i'm wondering if i still even need xorg. I'm still keeping it around just in case for now, but i could very easily purge it from my system anytime since i'm using nixos and all my xorg related settings are in a specific file. The main pet peeve i have with wayland is gaming related, and should hopefully improve when wine and proton go native wayland. I have a dual monitor setup and games always choose the wrong monitor by default, which means i can only use the resolution and refreshrate of the secondary monitor. I have a keybind to set the primary xwayland monitor with xrandr, which solves the problem, but it is a bit hacky. I also need to toggle vrr on and off with a keybind because it causes flickering on my monitor. It's a bit annoying but atleast it works, on xorg you can't even use vrr with multi monitor to begin with.
Have you tried running your games with gamescope?
-
Have you tried running your games with gamescope?
I think it does work, but from my understanding when nested inside another wayland session, thing like vrr don't work, which brings me back to the xorg problem, but my current workaround works for me, so now it's just a matter of hoping it will improve and become less tedious.
-
Your point is that it is still rough and then you bring up a bunch of stuff that is no longer an issue.
NVIDIA in particular is basically a solved problem with both explicit sync and open source kernel modules as the default from NVIDIA themselves.
Rustdesk and Waypipe are probably going to eat into your billion dollars (and network transparency laments).
As stated in the article, opt-out vsync is already a thing (though not widely implemented yet).
I have not used GNOME in a while but KDE on Wayland is great. And the roadmap certainly looks a lot nicer than xorg’s.
I was on a video call in Wayland an hour ago. I shared my screen.
If that is your full list, I think you just made the case that Wayland is in good shape.
Last I tried Rustdesk (two days ago) it was a buggy, glitchy mess and the shared screen was tearing immensely. Is that recent or did it use to be better?
-
Something similar happens to me on my desktop (debian 13) - it goes black then brings me back to the login screen. But in my case it's probably the nvidia drivers (proprietary). Not certain, though. Still happy on X11 for the meantime.
I'm running Bazzite on KDE Wayland with the proprietary Nvidia drivers just fine. I think you've got another issue causing this.
-
This post did not contain any content.
I might switch to wayland when xfce starts to have decent support for it. I'm not a ride or die Xorg fan, I just want to keep using the DE I'm used to.
-
This post did not contain any content.
I have a shitload of bug/weird behavior with Wayland, I hope it gets better but for me it is not there yet.
-
This post did not contain any content.
Sorry but pipewire is shit and it works with Wayland (didn't see anything Wayland uses pulseaudio) and I believe Wayland still not ready for use, It's unstable for me because pipewire crackling like fire
-
Sorry but pipewire is shit and it works with Wayland (didn't see anything Wayland uses pulseaudio) and I believe Wayland still not ready for use, It's unstable for me because pipewire crackling like fire
Get your shit together.
-
I'm running Bazzite on KDE Wayland with the proprietary Nvidia drivers just fine. I think you've got another issue causing this.
I'm not familiar with Bazzite. Did you get those drivers from Nvidia's website? That's my only issue with Debian 13 right now. Everything else is working as expected. Also the reason I had to get the drivers from the website is somehow I couldn't enable some stuff (like amd-pstate) on the default Bookworm kernel and had to use a backported one.
