wait, we will lose xEyes?
this post was submitted on 19 Jun 2025
276 points (97.6% liked)
Linux
8032 readers
694 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
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.
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.
load more comments
(1 replies)
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.
I've been using remote desktop for work daily on wayland (kde) for the last 3 or 4 years... I have no idea what "buggy support" you are refering to
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 don't care about that. Hhit was working and now it's not" - the users
load more comments
(11 replies)
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.
load more comments
(1 replies)
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.
Drawing directly on the desktop is a native feature of KDE Plasma. :)
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.
load more comments
(2 replies)
load more comments
(7 replies)
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.
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.
load more comments
(5 replies)
Well, they do recommend using LTS releases and the specifically change stuff more drastically on the release before the next LTS release.
Yeah, I think the fact that the next LTS will be 26.04 is the driver here, I just get the impression that things might get a little rocky and that they might've been better off had the next LTS been further into the future.
But it'll be a real smoke test release, at least. Hopefully they have enough resources to fix the issues that are uncovered, and don't wind up reverting for the LTS, or with a crummy LTS.
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.
EDIT: Two days on wayland nvidia now, both gaming and using NVENC in OBS. It's been amazing.
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.
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.
load more comments
(10 replies)
view more: next ›