I run proprietary Nvidia drivers as well and Wayland runs so much better than Xorg now that I’m permanently coming over to Wayland. I’m extremely happy rn with Wayland
I run proprietary Nvidia drivers as well and Wayland runs so much better than Xorg now that I’m permanently coming over to Wayland. I’m extremely happy rn with Wayland
I keep trying Wayland and an in the middle of an attempt. I use fedora maniacally updated, Nvidia, and plasma shell. I’m about to abort again:
-even configured to directly use Wayland, I see chrome based browsers glitch out on occasion, and when it starts glitching it just keeps on glitching
-plasma panel stops updating multiple times a day, staying frozen including the clock
-sometimes kwin starts, but plasmashell has to run manually, and per above has to be restarted on occasion
-occasionally it just forgets what the monitor resolution is supposed to be and reverts to 1024x768
-the blur translucency effect glitches around mouse cursor
-immersedvr doesn’t support Wayland
On the flip side, xorg problems are: -occasionally kwin can’t grab keyboard for some effects until restarted. This is a well documented bug butt other than it being xorg specific, doesn’t seem to be figured out.
-some things tear in ugly ways, but not nearly as bad as the chrome glitch under Wayland.
Maybe kwin isn’t a great Wayland compositor, maybe Nvidia drivers are still not up to snuff. Ultimately, it’s not viable for me. Further kwin is a huge factor for “why Linux desktop” for me, gnome shell is more limited even than Windows for my workflows.
I had those same issues on my 3080. I switched to AMD and Kwin works great on Wayland.
I wonder. Does KWin still use the old workaround for Nvidia?
I remember gnome refusing to bend to Nvidia over eglstreams.
If Kwin is still using that workaround, even now after Nvidia conceded, maybe that is the problem.
Definitely think NVidia has got some ways to go on improving Wayland drivers. AMD has its share of issues but they’re a lot less obtrusive than what you’re describing