Ubuntu Joins the Movement: X11 Officially Being Phased Out

Between that and the uutils-coreutils, Ubuntu 25.10 sounds like it'll be an interesting experience for users, especially those with accessibility and internationalisation needs.

Well, they do recommend using LTS releases and the specifically change stuff more drastically on the release before the next LTS release.
I fully agree with you on the accessibility front. It's not even good on X11, but it's unusable on Wayland, from what I understand :( Accessibility on Linux needs a massive funding and development initiative, and it needed to be done a long time ago.
But uutils is pretty solid. I've swapped out my GNU coreutils entirely (on Arch, not Ubuntu, because I value my time too much to be troubleshooting broken snaps) and haven't run into any issues. I think people are underestimating how close the compatibility already is. I'm sure something I use at some point will try to invoke an option that doesn't exist in the uutils version, but it's been solid for me so far.
- Yeah, I think those are just lacking in the internationalisation?
  People like me, who at most have some reading glasses needs and have their computer set to generally English utf-8 will be likely be fine.

wait, we will lose xEyes?

No, thanks to XWayland.
- but it doesn’t work perfectly, xeyes through XWayland only follows your cursor if it’s hovering another XWayland window
  which makes it a fun way to see which apps use XWayland tho!
KDE has you covered. Someone made an applet that works on Wayland too: https://github.com/luisbocanegra/plasma-cursor-eyes

Hope they're gonna devote the development resources to making it actually work.

While it actually works, there are truly some missing features obviously. The hope is, when lot of major distributions and desktop environments stop supporting X11, then application developers and Wayland developers have to find a solution quicker. This will accelerate development of Wayland, at least the remaining issues.
One area where Wayland needs to improve is support for various accessibility features.
- That does feel rther like jumping out of a plane and hoping you can finish making your paracute before it's too late.
  The concept of moving on from X11 is a good one, but making Wayland just a protocol that every compositor has to implement separately, and having so many optional larts to the spec seems like a guarantee that the ecosystem around it will never properly mature.
  The KiCad developers have a good article about some of the issues with Wayland here.
- This is big "if we break your old toys, you'll HAVE to play with the new ones" energy.
  Tell me when they port FVWM. Seriously. FvwmButtons-- a pretty trivial dock except it can swallow other windows-- seems like it would be out-of-bounds on Wayland unless it was owned by the compositor itself to access the other windows. I don't see any of the new taskbar-tools used with Wayland compositors offering similar functionality (I could be wrong) and that seems an amazing loss of feature parity.
In what way does it not work?
- Remote desktop support is buggy on gnome and nearly non-existant on other DE's, which speaks to how poor a job wayland does at managing functions between DE's, where each individual DE has to build their own solution for basic functions, further fragmenting development efforts.
  Then there's accessibility functions, which wayland breaks almost by design by denying apps access to each other. Even something as simple as an on screen keyboard becomes nearly impossible to implement.
  Any software thats being pushed to users as the "main" experience, should not break things as common and fundemental as remote desktop or onscreen keyboards. Great way to drive away potential users switching from windows 10.
- Ctrl+Shift+V in KeePassXC should autotype username and password in another window, but I believe is still broken out of the box on Wayland.
  There may be some workaround that I haven't tried yet.
- Sessions don't resume properly after sleep. Tools like Barrier don't fully work. Wayland is fine, but it's just not mature.
- Here we are YEARS later and OpenBoard is STILL broken.
  No, I don't want a fully contained, separate whiteboard application - As a teacher, I need to be able to DIRECTLY DRAW ON THE DESKTOP. Until this is a fully supported feature that software can implement, Wayland is completely broken for me.
- When I resume chrome, all the windows open on desktop 1 regardless of what desktop they were on when they closed
- Garbage HDR support. But I think that's more of a KDE issue. (IDK I'm not a Linux pro)

How is wayland nvidia gaming at the moment?

Several months ago I tried gaming on wayland with nvidia and it was completely broken for me.

Just make sure the kernel modules are enabled and so are the systemd services. Shouldn't have a problem. It's been butter since they released the VRR fix a few months ago
- Could you please guide me to relevant documentation for this?
  For now I'll just start at the Arch wiki for wayland.
Games worked for me on Kubuntu, but a lot of other things were seriously broken. Compositor/Desktop effects did not work at all, weird screen artifacts, Taskbar crashes, Discord lags terribly and has display problems. I don't know, if that is going to be the new Desktop experience, we're gonna have a problem.
I've been gaming with a 2080ti in Wayland for about a year now. I can't say I've had any issues related to my graphics card at all. The only hiccups I've had are with a couple of games, maybe two, that I had to tweak to run. They were known issues with public fixes. It's been a great experience.
There was an issue a few months back with multi monitor setups. Anytime I changed a monitor input, it would hard lock. It's fixed now.
I've got an nvidia card and I've personally got no complaints about Wayland! been using it for some time to much success, I feel like x11 is just 'off' in comparison.
Depends on the desktop environment in my experience. On Fedora Gnome it was an unstable mess with my Nvidia RTX card but Fedora KDE Plasma has been stable.
- It was mainly on Nobara but I guess my negative experience also followed me from troubles in debian early 2024.
It works just fine for me on my RTX 3060 Ti. No significant performance decrease or stuttering at all (except in Cities Skylines II but that's not Wayland's fault)
Several months ago I had a similar experience. Even just running plasma with Wayland+Nvidia was enough to cause problems.
- This was my experience. I could barely even get my machine to run.

Do you people ever think that Wayland is being sorta shoved down our throats ?

PipeWire wasn't

Waylands initial release was 2008... I don't think so at all...
Pipewire was released in like 2017 but the transition was a lot smoother than Wayland so that's probably way it feels like that.
I’ve been waiting for Wayland to take over since like 2011 or some ancient time like that. I’m just glad it’s finally got some traction tbh.
- Maybe we should wait until Wayland is more mature (Like having proper accesibility) ?
Yes and no
This only applies to the gnome for now.
- But it's happening in KDE as well