this post was submitted on 09 Apr 2024
119 points (96.1% liked)

Linux Gaming

15846 readers
24 users here now

Gaming on the GNU/Linux operating system.

Recommended news sources:

Related chat:

Related Communities:

Please be nice to other members. Anyone not being nice will be banned. Keep it fun, respectful and just be awesome to each other.

founded 4 years ago
MODERATORS
 

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!

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 0 points 7 months ago* (last edited 7 months ago) (1 children)

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.

[–] Rustmilian 2 points 7 months ago* (last edited 7 months ago) (1 children)
[–] [email protected] 1 points 7 months ago (1 children)

Exactly. When the variable is unset the UI shows massive artifacts and weird rendering glitches.

[–] Rustmilian 2 points 7 months ago* (last edited 7 months ago)

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.