A set of merge requests were opened that would effectively drop X.Org (X11) session support for the GNOME desktop and once that code is removed making it a Wayland-only desktop environment.

Going along with Fedora 40 looking to disable the GNOME X11 session support (and also making KDE Plasma 6 Wayland-only for Fedora), upstream GNOME is evaluating the prospect of disabling and then removing their X11 session support.

Some concerns were raised already how this could impact downstream desktops like Budgie and Pantheon that haven’t yet fully transitioned over to Wayland. In any event we’ll see where the discussions lead but it’s sure looking like 2024 will be the year that GNOME goes Wayland-only.

    • d_k_bo@feddit.de
      link
      fedilink
      arrow-up
      24
      arrow-down
      6
      ·
      edit-2
      1 year ago

      In my experience, most of the issues with wayland are caused by applications software not supporting it. If we enter a wayland-only world, developers are pushed towards supporting wayland.

        • d_k_bo@feddit.de
          link
          fedilink
          arrow-up
          13
          arrow-down
          3
          ·
          1 year ago

          It’s not GNOME’s or wayland’s fault that Nvidia refuses to fix their drivers.

        • edinbruh@feddit.it
          link
          fedilink
          arrow-up
          10
          arrow-down
          1
          ·
          1 year ago

          You are correct in saying that there are still several problems in both Wayland (e.g. lack of drawing tablet support) and mutter (e.g. tearing protocol non yet implemented). But then you proceed to list problems that are Nvidia’s fault.

          The first is weird, but it probably depends on Nvidia’s kernel driver.

          The second is probably a synchronization issue, so it’s probably due to Nvidia refusing to implement implicit sync, and explicit sync not being yet supported in Linux. But don’t quote me on that.

          Vulkan should work. But video acceleration is definitely absent, and is listed by Nvidia itself among current driver limitations. Try this.

    • jack@monero.town
      link
      fedilink
      arrow-up
      4
      arrow-down
      1
      ·
      edit-2
      1 year ago

      Choice is good, but progress always beats choice eventually. That’s just how it is.