10mo ago

Explicit GPU Synchronization for Xwayland now merged

www.gamingonlinux.com Explicit GPU Synchronization for Xwayland now merged

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!

Linux @programming.dev

Mac @programming.dev

10mo ago

Explicit GPU Synchronization for Xwayland now merged

www.gamingonlinux.com /2024/04/explicit-gpu-synchronization-for-xwayland-now-merged/

32 1

Linux @lemmy.ml

petsoi @discuss.tchncs.de

10mo ago

Explicit GPU Synchronization for Xwayland now merged

www.gamingonlinux.com /2024/04/explicit-gpu-synchronization-for-xwayland-now-merged/

193 11

Gaming @lemmy.zip

Zippy Bot @lemmy.zip

BOT

10mo ago

Explicit GPU Synchronization for Xwayland now merged

www.gamingonlinux.com /2024/04/explicit-gpu-synchronization-for-xwayland-now-merged/

10 0

You're viewing part of a thread.

Show Context

34 comments

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.
text

$ 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.
- Here's just a tiny fraction of the Nvidia specific bugs on X11 :
  https://github.com/NVIDIA/open-gpu-kernel-modules/issues/380
  https://bbs.archlinux.org/viewtopic.php?id=283461
  https://forums.developer.nvidia.com/t/16-bit-overlays-broken-with-x11-and-4xx-series-driver/128067
  https://bugs.kde.org/show_bug.cgi?id=460341
  labwc
  You're using a WM bud, wtf do you expect?
  
  You’re using a WM bud, wtf do you expect?
  I expect it to work, like Openbox works on X11.
  
  You miss the entire point of WMs then.
  \ You're complaining about 7 lines of configs when the entire point of WMs is for you to literally customize everything through configs.
  \ Shit, you probably don't even need half of that crap. QT_QPA_PLATFORM=wayland is already handled by qt, you only need that when running apps across Waypipe from a headless server environment. By default QT infers your environment from $DISPLY which is always :0 in Wayland.
  
  Thank you for educating me on basic knowledge about WMs, which I use since ove a decade.
  I just expect applications behave the same. I have literally not one single line of configuration for X11 in any of my configuration files.
  I need this QT variable, otherwise Cura does not work properly.
  
  Cura as in this one? :
  
  Exactly. When the variable is unset the UI shows massive artifacts and weird rendering glitches.
  
  I don't see any graphical glitches on my hardware.
  \ Perhaps you're still on the qt5 version?
  \ Maybe a bug with your Nvidia driver?
  \ Perhaps your WM doesn't have explicit sync yet and your card & driver needs it in this particular case? Perhaps it's running under XWayland?
  Wayland#Qt :
  \ While it shouldn't be necessary, to explicitly run a Qt application with the Wayland plugin, use -platform wayland or QT_QPA_PLATFORM=wayland environment variable.
  As it says above, it should really be inferred by default. Something weird is going on here.

34 comments