Announcement

Collapse
No announcement yet.

SDL2 Reverts Its Wayland Preference - Goes Back To X11 Default

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • #11
    Originally posted by phoronix View Post
    Lantinga commented with the revert, "SDL Wayland support is stable, but there are a number of issues with third-party software (NVIDIA drivers, libwayland event overflow, libdecor not handling plugin load failures, Steam overlay not working with Wayland, etc.) that make it better to default to X11 at this time."
    Sigh.

    The very first thing that was named. Nvidia still holding back Wayland adoption.

    Could we get some flooding of Nvidia's bug report forum so they finally do something? It's so annoying. It's really so annoying.
    Last edited by ezst036; 18 April 2022, 02:25 PM.

    Comment


    • #12
      Matches what Ubuntu did yesterday for gdm3 for the 22.04 LTS release...

      "gdm3 (42.0-1ubuntu6) jammy; urgency=medium

      * Fix Wayland no longer being available for everyone
      - Fix by adding a separate revert patch instead of trying to
      rebase the cherry-picked patches (LP: #1969243)
      * Please note that Wayland is not currently available for
      systems using the Nvidia graphics drivers because those drivers
      don't properly handle suspend and resuming from suspend. It is
      intended for those drivers to be fixed in a future stable release
      update for Ubuntu 22.04 LTS. See bug 1968929"

      So until apparently until at least 22.04.01 Wayland won't be offered under the Nvidia drivers on Ubuntu 22.04 LTS.

      Comment


      • #13
        Just in time for the next Ubuntu LTS release.

        Comment


        • #14
          Originally posted by Vistaus View Post
          And here I thought most Phoronix members blamed X11 for being buggy, but it turns out Wayland is a bugfest too? :rolleyes
          It turns out mediocre nvidia driver is still POS and software like Steam were not updated to Wayland, yet. You could at least read the article.

          Comment


          • #15
            Originally posted by phoronix View Post
            libdecor not handling plugin load failures,
            See? This is why I wish every compositor implemented the server-side decorations protocol...

            Comment


            • #16
              Originally posted by ezst036 View Post

              Sigh.

              The very first thing that was named. Nvidia still holding back Wayland adoption.

              Could we get some flooding of Nvidia's bug report forum so they finally do something? It's so annoying. It's really so annoying.
              Wow exaggerate/sensationalist much?

              Out of the 6 things on the list, you bold the one thing that is controversial? Even completely ignoring the fact that Wayland support from NVidia driver is very fresh where as everything else on that list is Linux ecosystem issues that have literally existed for years.

              The only problem here is people pushing Wayland when its clearly not ready and in reality NVidia drivers is a tiny part of that problem.

              Comment


              • #17
                Originally posted by howarth View Post
                Matches what Ubuntu did yesterday for gdm3 for the 22.04 LTS release...

                "gdm3 (42.0-1ubuntu6) jammy; urgency=medium

                * Fix Wayland no longer being available for everyone
                - Fix by adding a separate revert patch instead of trying to
                rebase the cherry-picked patches (LP: #1969243)
                * Please note that Wayland is not currently available for
                systems using the Nvidia graphics drivers because those drivers
                don't properly handle suspend and resuming from suspend. It is
                intended for those drivers to be fixed in a future stable release
                update for Ubuntu 22.04 LTS. See bug 1968929"

                So until apparently until at least 22.04.01 Wayland won't be offered under the Nvidia drivers on Ubuntu 22.04 LTS.
                wayland promises land still lives



                Comment


                • #18
                  I guess that if nVidia hadn't been sabotaging proper Wayland support for years, most of these bugs would've been worked out already. If only AMD had truly competitive GPUs earlier

                  I've been on the latest KDE with Wayland for a few months now and the experience is perfectly fine. The one app that needs to get its stuff together is Zoom but even that mostly works.

                  Comment


                  • #19
                    Originally posted by xcom View Post
                    I still wait for Steam and Chrome, Chromium to support Wayland. These are really needed for full Wayland switch.
                    Actually Chrome / mium works really well in wayland, they also put an option in the flags, if you set it to auto, depending on if you are using xorg or wayland it will boot in native mode. At the moment however it is still set to xorg by default, but is set to change with future releases where it will be set to "auto" instead of the current xorg. However Chrome works really well native wayland on Plasma too.

                    Comment


                    • #20
                      Originally posted by mdedetrich View Post
                      The only problem here is people pushing Wayland when its clearly not ready and in reality NVidia drivers is a tiny part of that problem.
                      What is this supposed to mean? Literally none of the reasons stated for this reversion have anything to do with the protocol. They literally said that the Wayland support in SDL is stable but they're reverting because of issues with third party software and they were first to point out Nvidia drivers.

                      The reason that OBS doesn't work properly on Wayland on Nvidia hardware is because Nvidia drivers don't support EGL_NATIVE_RENDERABLE. The reason why Gnome night light doesn't work on Nvidia hardware in Wayland is because the driver doesn't support GAMMA_LUT and according to Nvidia it's part of the reason why Gamescope has issues running on Nvidia hardware either.


                      Comment

                      Working...
                      X