Linux

10022 readers

444 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

Ategon@programming.dev

anzo@programming.dev

dwraf_of_ignorance@programming.dev

113

GNOME 50 Ends the X11 Era After Decades (linuxiac.com)

submitted 18 hours ago by cm0002@toast.ooo to c/linux@programming.dev

31 comments fedilink hide all child comments

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

[–] rozodru@pie.andmc.ca 3 points 14 hours ago (3 children)

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.

[–] mycodesucks@lemmy.world 3 points 13 hours ago (1 children)

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.

[–] vivendi@programming.dev 1 points 26 minutes ago

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.

[–] hallettj@leminal.space 3 points 13 hours ago (1 children)

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?

[–] rozodru@pie.andmc.ca 1 points 13 hours ago (1 children)

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.

[–] ArchEngel@lemmy.ca 1 points 6 hours ago* (last edited 6 hours ago) (1 children)

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!

[–] rozodru@pie.andmc.ca 1 points 1 minute ago

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.

[–] domi@lemmy.secnd.me 1 points 1 hour ago

I'm using the Discord Flatpak on Fedora Kinoite (Wayland/KDE) and have no such issue.