this post was submitted on 06 Nov 2025
138 points (99.3% liked)

Linux

10022 readers
485 users here now

A community for everything relating to the GNU/Linux operating system (except the memes!)

Also, check out:

Original icon base courtesy of lewing@isc.tamu.edu and The GIMP

founded 2 years ago
MODERATORS
 

Although Wayland has been GNOME’s default session since 2016, X11 has continued to linger in the codebase—until now. That changed with the recent merging of two PRs (here and here), which completely removed the X11 codebase from both Mutter, GNOME’s default window manager and compositor, as well as the GNOME Shell itself.

In other words, the GNOME project is finally closing one of the longest chapters in Linux desktop history. With the upcoming GNOME 50 release, scheduled for mid-march 2026, the desktop environment will officially drop support for the native X11 session, making Wayland the sole display system moving forward.

you are viewing a single comment's thread
view the rest of the comments
[–] popcornpizza@lemmy.blahaj.zone 7 points 19 hours ago (2 children)

I'm on GNOME 42 with X11. Wayland kills mouse gestures, apparently, because there's no way to know which window is focused, or which window the mouse is hovering on. At least, not as easily as with X11.

So I'm not sure where I'll go after this. Mouse gestures per window is an extremely important feature to me. Doesn't help that easystroke has been abandoned for years.

KDE has an idea thread about it, but no one is working on it.

[–] muhyb@programming.dev 10 points 19 hours ago (2 children)

Don't know about the other things but "focus follows mouse" is possible on Wayland. Well, it's possible on river at least, not sure about KDE or GNOME. Could be a wlroots related feature though.

[–] popcornpizza@lemmy.blahaj.zone 5 points 15 hours ago

I wasn't specific enough, but I meant programmatically. In X11 we have stuff like xprop and xdotool. I can see where my mouse is, which window is underneath, activate or focus a window, etc. I mean these things in code, not visually on the desktop.

Wayland considers these things "security risks", and I get it, but at the same time... customization of my own OS is what drove me to Linux. 🤷🏻‍♂️

For example: A while ago I tinkered with easystroke plus a custom script using xprop + xdotool. The way it worked (easystroke does this natively, but I just wanted to learn how to do it myself, and the GUI is a bit clunky anyway) is that you assign a stroke/gesture, and execute your script with parameters. The script verifies where the mouse is at execution by grabbing window info with xprop, and runs a different command depending on that (more often than not, using xdotool to send keys). So if I do a flick upwards, the script sees Firefox in the background and sends CTRL+T to the window. A new tab is opened. But if VSCodium is in the background of the mouse, I send CTRL+N instead, to open a new text file (tab).

Unless something has drastically changed in the past few months, it's my understanding that none of that is possible with Wayland, and now it's up to the DEs (or whatever else) to come up with something that gives window info.

[–] Neptr@lemmy.blahaj.zone 3 points 18 hours ago

It is possible on both GNOME and KDE iirc. I never use that feature, but i am sure i saw it in the settings.

[–] imecth@fedia.io 9 points 18 hours ago

Yeah accessibility features tend to be last in line. The good news is that getting rid of x11 will put a fire under people to get it done.