The day is finally here. Xwayland now has the code for Explicit GPU Synchronization merged after waiting over a year for everything to be ready.

This merge resquest has finally been merged into XWayland, which means NVIDIA users are just one beta driver release away (May 15th) from probably having a good experience on Wayland now!

    • tarsisurdi@lemmy.eco.brOP
      11·
      2 years ago

      You can’t deny their support for Wayland has been steadily improving with the latest driver releases. In fact it’s already in a good state if it weren’t for the flickering in certain applications caused by these issues with explicit sync which are currently being addressed.

  • Malix@sopuli.xyz
    23·
    2 years ago

    am I correct to assume this is the thing that’ll fix eg. Steam going full seizure mode under wayland + nvidia?

    • tarsisurdi@lemmy.eco.brOP
      13·
      2 years ago

      That’s true, but thankfully it’s already been merged in mutter and is underway in kwin.

      The code for GNOME has already been merged, KDE has a merge request open for it too, Mesa also already has it merged in.

      • 𝘋𝘪𝘳𝘬@lemmy.ml
        31·
        2 years ago

        Who thought individual compositors having to re-implement base features individually and over and over again would be a good idea?

        Same with the dozens of different protocols and portals and all the other magic bullshit. Once feature-complete with X11,Wayland will be of same complexity.

      • 𝘋𝘪𝘳𝘬@lemmy.ml
        24·
        2 years ago

        Nvidia shouldn’t need to put anything in. It’s entirely Waylands fault that it does not work well with the already existing hardware and drivers environment.

        Nvidia is shit for so many reasons but not because Wayland doesn’t work well with it.

        • Bene7rddso@feddit.de
          4·
          2 years ago

          If Nvidia had worked together with Wayland devs from the beginning this wouldn’t be an issue

              • 𝘋𝘪𝘳𝘬@lemmy.ml
                1·
                2 years ago

                Cannot confirm any Nvidia unique X11 bugs since everything works perfectly fine since a decade or so for me – but tons of Nvidia unique Wayland bugs (same driver version and same card). I am not quite sure if Nvidia are really the bad one in this specific case.

                My whole invironment is full of stuff to make Wayland actually work with Nvidia.

                $ cat .config/labwc/environment 
GBM_BACKEND=nvidia-drm
__GLX_VENDOR_LIBRARY_NAME=nvidia
LIBVA_DRIVER_NAME=nvidia
QT_QPA_PLATFORM=wayland
WLR_NO_HARDWARE_CURSORS=1
XDG_CURRENT_DESKTOP=wlr
XDG_SESSION_TYPE=wayland

                Not one single line of configuration is used for X11.

    • Lojcs@lemm.ee
      3·
      2 years ago

      Are you sure that’s not because it’s running at a very low frequency?

      • Sabata11792@kbin.social
        2·
        2 years ago

        Not sure how to check, still fairly new.

        I did notice the temperatures though. The card normally idles at 30-40c having anything open after a while will have it cooking at 75ish. I would expect it to be in the 50s after a few hours of youtube, or pushing 90-100 gaming. No issues on the Windows half of the install. From what I could piece together it dose seem to be related to Wayland and the drivers. I was thinking of waiting till Nobara updates and hope it goes away.

        Seems if I have anything opened and on screen like firefox or the file browser, it gets toasty.

        • Lojcs@lemm.ee
          1·
          2 years ago

          If it’s reaching those temps then the answer is probably no. Hope you find a solution