Is anyone else seeing strange rendering issues with the new Nvidia 470 series drivers and Kernel 5.13? I updated to both at the same time, so not entirely sure which caused it, and I haven’t seen anyone else mentioning anything similar to this (did everyone switch to Wayland already?)
The issue can best be described as windows being rendered in the background, even after they are closed. Sometimes its just the menu parts, sometimes its the whole window, even after that window has been minimised or closed. This obviously builds up when switching between virtual desktops, and gets quite annoying after a while.
The good news is that it can easily be fixed by either changing the compositor to xrender and back again, or even something like changing the scaling setting (which I presume resets the driver).
I’m not sure - I don’t really have enough information to create a proper bug, and it could just be me, obviously. Anyone seen anything like this recently, or before?
Unable to re-create it on kernel 5.13, but even though we’re both using the latest 470 driver and KDE Plasma, there’s so many other things that can be the culprit. Does this issue arise when rebooting into the 5.10 LTS kernel?
Can you try again after applying Force Full Composition Pipeline for Nvidia’s X Server settings, and then rebooting?
Launch nvidia-settings with sudo privileges: sudo nvidia-settings
Check the option for Force Full Composition Pipeline under X Server Display Configuration
Click Apply
Click Save
Save it over the file /etc/X11/mhwd.d/nvidia.conf, and make sure to check the option “Merge with existing file” (a backup .conf file is automatically made)
Exit Nvidia Settings, but now re-launch it as a normal user: nvidia-settings
Makde sure “Sync to VBlank” is enabled under OpenGL Settings
I’m definitely running with Force Full Composition Pipeline on both monitors. Its not a blurring thing, its just like the background gets… additive, so anything rendered onto it stays when you change virtual desktops - I use transparency for inactive windows, so you can kinda see all the layers, also sometimes the transparency effect itself goes a bit screwy, in that the active window is still transparent.
I am going to have to try this with an LTS kernel as you say - its a bugger to test though as it happens ‘at some point’ when I am running a session. I suspected it might be after locking the screen, but I am really not sure its that simple.
Its a RTX 2070 super btw. As you say, though, so many variables, which is why I haven’t yet submitted a bug.
Also thanks @philm, fingers crossed that this helps
I myself haven’t filed a bug report for it yet, but considering how many people are running into this bug, I’d be surprised if the KDE devs don’t know about it yet.
As for what priority they’ll give to the bug, I don’t know. I’ve already filed a couple of confirmed bugs before and I never got any notifications of a followup. Some of those bugs have already been around for ages too, and some were fixed but then got reintroduced again in a later version of the software.
This has been driving me insane since the last update, I thought I was the only one experiencing this, but I didn’t report it because I was trying to find a way to reproduce it, but no, it just happens so randomly in the most annoying way. Already tried different kernels, different OpenGL, different Nvidia driver, and no luck.
Yes, I too thought the issue was resolved, but so far it has happened to me again every day as well. As the matter of fact, it just happened again a few minutes ago, with a popup menu in chromium. Restarting the compositor ─ press Alt+Shift+F12 to stop it and once more to restart it ─ remedies the problem.
…