- cross-posted to:
- [email protected]
- cross-posted to:
- [email protected]
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.
can’t speak for OP but the only beef I have with wayland is discord. If i’m in voice comms it will ONLY work if I’m either in a game or my discord is focused. if I’m in my web browser or doing something else like in an IDE or terminal etc then voice doesn’t work. It’s annoying.
If anyone has a workaround for that I’d love to hear it. on x11 never had these issues but I can’t use x11 as my primary machine is a hybrid nvidia and amd gpu laptop so no gaming on x11.
I’m using the Discord Flatpak on Fedora Kinoite (Wayland/KDE) and have no such issue.
The standard workaround seems to be “scream at the developer to rewrite their features around Wayland’s limitations and stop bothering the Wayland developers asking for feature parity”. You know… The same way Android handles updates.
It is pretty hard to improve if you are not allowed to change anything.
Yes, the design of Wayland means that some of the techniques that work on X will not work on Wayland (on purpose). So yes, some apps have to be adapted to use the techniques that do work on Wayland. And no, changing Wayland to support the old ways is not the answer (because they were changed on purpose).
Wayland has been criticized for taking away previous capabilities before providing new ways to do things. That is a fair critique, though somewhat par for the course when replacing old tech. But at this point, almost everything necessary is possible and Wayland users are in the majority (the massive majority soon).
At this point, it really is the apps developers responsibility to support Wayland properly. I mean, they do not have to of course but that means their app will be broken for 80% of Linux users on two years (and more than half today).
Yes, the insane old ways are being phased out for a reason. Sorry that we don’t keep the world in a heavily romanized version of 2003 forever.
Preach all you want. In a practical sense, X works for me and Wayland does not. No amount of yelling about security exploits that have not once been exploited in the wild even by the most resource rich state actors will change the fact that I can not maintain my daily productivity with Wayland, and I’m not going to accept being LESS productive to satisfy anyone’s personal development crusade. That’s the antithesis of how software, especially FOSS software, is supposed to work. Either Wayland will give me every single feature I need, or I will sit here with my old but functioning X installations until the day I die.
You are the one preaching and yelling.
Stay on X if you want. As you say, that is the freedom Open Source provides. I use ancient hardware. To each their own. If I was still using XFCE, I would still be using X myself*.
But if you are going to voluntarily stay behind, stop complaining that the bus left without you.
Wayland users are in the majority. By the time Mint (Cinnamon) flips to Wayland (2026?) and GTK5 is released (2028?) it will be over 90%. Almost all GNOME and Plasma users are Wayland now and that must be 60% already (without even counting Hyprland, Sway, COSMIC, or Niri).
We already have Wayland only distros (eg. RHEL10). GNOME will not even be the first Wayland only DE (COSMIC). The ship has sailed.
My family uses Discord heavily, and I’ve set up a number of different distros and window managers at different times, all using Wayland, and I have not seen this issue. I think that includes running in browsers using Xwayland, and using native Wayland - but I’m not 100% sure because I’ve been running browsers in native Wayland mode for a long time, while my family members usually use the Discord Electron app.
There might be some more specific issue on your system, like a pipewire misconfiguration? Do you use pipewire?
well it’s been happening with me across multiple distros like Arch, CachyOS, NixOS, etc and it’s always been the same. yes I’m using pipewire so I’m not exactly sure what it is.
Gonna chime in and add that I have also not had this issue, Nobara Linux here. My discord voice comms work great in browser, and the various other versions I have run. Hope you figure it out!
are you using push to talk? that’s the only thing I can think of that’s not working for me. because everyone is saying it works fine in wayland but again I’ve used both flatpaks and packaged versions across multiple distros and the push to talk outside of discord or a game never works for me.
That explains things. Non-focused applications cannot read keystrokes on Wayland.
Since Discord is still running in X11, if you are on KDE you can enable one of these options as a workaround:
Hopefully Discord (or a wrapper for it) will eventually get proper global shortcut support, in which case you can set it right in the KDE shortcut settings.