- cross-posted to:
- linux
- [email protected]
- cross-posted to:
- linux
- [email protected]
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!
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
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=waylandis 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$DISPLYwhich is always:0in 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?
As it says above, it should really be inferred by default. Something weird is going on here.