GNOME 50 completes the long migration to Wayland, dropping X11 backend code and relying on XWayland for any remaining compatibility needs.

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.

  • hallettj@leminal.spaceEnglish
    2·
    1 day ago

    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.caEnglish
      1·
      1 day ago

      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
        0·
        17 hours ago

        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.caEnglish
          1·
          11 hours 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·
            7 hours ago

            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.