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.
this post was submitted on 19 Jun 2025
250 points (97.7% liked)
Linux
7972 readers
617 users here now
A community for everything relating to the GNU/Linux operating system
Also check out:
Original icon base courtesy of lewing@isc.tamu.edu and The GIMP
founded 2 years ago
MODERATORS
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.
internationalization
Interesting point. I don't actually know about that. What can the GNU coreutils do with regard to internationalization? Just the output of commands, or can they also internationalize stuff like command args?
I'm generally an en_*.UTF-8 user (even tried en_DK.UTF-8 for a bit for a reason we'll come back to), so I don't have a complete picture of it and would have to go look at the documentation or source for that, but I'd expect
- documentation
- date formats:
en_DK.UTF-8should give you ISO8601-formatted dates, if I can't have that I at least want DD/MM/YYYY; the US-american nonsense is just plain unacceptable - sorting: e.g. Norwegian will have …zæøå and expect
aato be sorted aså, the Swedes have …zåöä, the Germans …zäöü, the Turks will want ı and İ sorted and upper/lowercased correctly, and there are some options around how you deal with "foreign" letters and diacritics. - Probably more stuff relating to
LC_*that I can't think of off the top of my head
but in any case, an ls -l output should be different depending on your locale, and in ways you likely don't even think about as long as it looks normal.
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.
I actually see this working out in the long run at least. In the mean time, there will be a lot of creativity while everyone tries to "invent the wheel" while great ideas perculate up during the stabalization phase.
Oh wow. I am suddenly less excited about our Wayland future.
Damn yeah. Just the window managment issues are a complete no go for any productive work.
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.
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.
That's a side effect of just dumping everything into X11, once you switch from it you lose all the random kitchen sink warts it grew over the years.
Like an on-screen keyboard shouldn't be fiddling with a display protocol to fake keyboard inputs, it should be using the actual OS input layer to emulate them (So then it'd work with devices that read input directly and not go via X11). Same with accessibility, there's a reason other OSs use separate communication channels with their own protocol.
I think it boils down to trade offs.
The major benefit to Wayland is that it has less overhead since apps talk directly to the desktop. Having desktops implement the protocols instead of relying on a external project means that the user experience is cleaner.
For smaller projects like window managers there are libraries that implement the core protocols. This allows for the minimal window managers Linux traditionally had as an option.
I won't argue that Wayland has issues with remote desktop. The problem currently is that it has to be implemented as a custom non standardized solution by every desktop. I don't think that there are any portals for doing session management which is unfortunate.
From a accessibility perspective I believe that has already been addressed.
I also don't see any reason to try to "market" Linux. Windows 11 is the successor to Windows 10. It isn't that bad compared to ever other version of Windows.
I guess we will see. Tiling WM on Wayland was, at my last check, totally limited to sway. As a dwm guy Wayland has yet to give me what I need.
As someone who's a week into trying to switch from Windows to Linux, I don't even know what X11 or Wayland are. My biggest hurdle has been how the Linux community always just assumes everyone knows every little thing. This article is a perfect example. It would have taken a sentence or two to add "X11 does this, but is being phased out".
I spent at least an hour today trying to connect to a shared network printer! As a geek, I love Linux but it's still not ready for the masses. And that's referring to Mint.
I've been using Linux for just about my entire adult life, except for a brief experience with Windows Vista, and I don't know what x11 and Wayland are. I just know Linux does what I want without bogging itself down with weird shit.
Honestly, that's not something you should have to know about. Many Linux folks just care about the inner workings of everything so they can make it work how they want.
Of course, when things break it helps knowing what the reason is and how to fix it. But usually your distribution should handle everything so that nothing breaks.
I agree with your first part, but I dont think I've ever used a windows, osx or linux computer that hasnt had issues connecting to printers, the problem there isnt with the computer.
It probably depends on the printer. I helped dad install Mint on a used laptop he bought, and the only help he needed with the printer was figuring out which config application to open to add it.
I use system-config-printer to set up both our Canon and Epson printers any time I install a fresh Linux here; it works flawlessly.
X11 is the display server. Your desktop environment, like gnome, has a window manager managing your opened applications and tells the display server "please render this stuff on the actual screen".
X11 is ancient and sucks, because for example, it can't do fractional scaling well, which is important for screens that have a higher resolution, since everything appears tiny otherwise.
The display server also offers some functionalities that the desktop environment can make use of, like global hotkeys, or screen sharing.
I'm not an expert or anything, but I think it's about right like this.
Many thanks for the explaination!
Sessions don't resume properly after sleep. Tools like Barrier don't fully work. Wayland is fine, but it's just not mature.
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.
Is that a problem of Wayland or a problem of KeePassXC?
I'd be highly surprised if Wayland actually has a protocol for applications to just type across other applications, we barely even have global shortcuts (it's getting there but reaaaaaally slowly).
KPXC might be able to get around it by using whichever method ydotool does (by faking a device AFAIK) - probably needs root to do this though, and it would also need to implement the global shortcuts API to be able to respond to a key bind I believe.
So perhaps a bit of column A and column B.
It works on X11, so I'd say Wayland.
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.
It might be a problem of the openboard software, not a problem of wayland. I don't know what you mean by "directly draw on the desktop", but whatever it is have you looked for other apps that might do the same thing?
Quite simply, you can draw and annotate the screen. I can circle things, draw attention to things, and highlight things on every window in the desktop environment without ANY consideration of what application is running - it's completely agnostic. Wayland's design doesn't allow it.
Until this feature is present, Wayland is unusable for me.
This kind of thing is precisely why the overall decision to replace X by building something NEW was folly from the beginning - because you are ALWAYS going to be missing use cases. X should've been treated like an API and "completion" be measured directly and terms of how much of the functionality is implemented - not in terms of "how much, in fuzzy natural language terms, do we have that works equivalently".
Also, and let's be entirely clear about this... Open Board got here FIRST. It was FINISHED software. Developed, released, and doing its job. To come along, make a change to its dependencies, and then blame IT for doing something wrong? Is it the job of every single developer to update their software to match what Wayland wants? Thousands of projects over decades? What happens when the Wayland devs make another change and something else breaks? I'm getting flashbacks of Linus Torvalds RIGHTFULLY yelling at a developer blaming an application for not functioning after a kernel update. "WE DO NOT BREAK USER SPACE."
Android forces developers to make these kinds of retroactive changes, and it's why the ecosystem sucks and any stable, well-built software is a couple updates away from being useless. I don't want my desktop OS to be more like that.
Wayland isn't a piece of software. It is simply a set if standards apps use to talk to the desktop which then talks to the kernel and hardware.
Apps access resources via XDG portals. If there isn't a portal for something it needs to be implemented at the desktop.
Back to your use case, I think you probably just need the appropriate desktop extension. Drawing on the desktop sounds like a desktop level thing.
And can you not see how that's a problem? Software that was written without using XDG portals shouldn't have to be concerned about their existence. If it is required that existing, finished software has to adapt to a new paradigm, it is not a replacement - it's new. And it's intrusive. If you replace the water system for a house, that's one thing. If you replace the water system in the house AND the new system requires the owner to buy and install all new fixtures on all the faucets, that's an entirely different thing altogether.
load more comments
(7 replies)
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.
load more comments
(10 replies)
view more: next ›