Bug 430976 - Problems with rendering on Wayland and Nvidia
Summary: Problems with rendering on Wayland and Nvidia
Status: RESOLVED UPSTREAM
Alias: None
Product: kwin
Classification: Plasma
Component: wayland-generic (other bugs)
Version First Reported In: 5.20.4
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-12-30 11:54 UTC by Ihor
Modified: 2021-01-05 18:42 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:
vlad.zahorodnii: NVIDIA+


Attachments
Render artifacts. (3.42 MB, image/jpeg)
2020-12-30 11:54 UTC, Ihor
Details
Render artifacts. (2.41 MB, image/jpeg)
2020-12-30 11:56 UTC, Ihor
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ihor 2020-12-30 11:54:42 UTC
Created attachment 134400 [details]
Render artifacts.

SUMMARY
After installing arch linux, proprietary drivers on the Nvidia graphics card, and running plasma on wayland, strange rendering artifacts (Cloning flashing cursors, Strange shadows) are observed when running certain programs (google-chrome, chromium, flameshot...). There are no such problems when starting firefox, telegram-desktop. 

Sometimes a problem with a problematic program can be solved by running shortcut 'Quick Tile Windows to the Left/Rigt' (Meta+Left/Right), and then everything works as it should. Artifacts completely disappear when the program that could not be displayed is closing by Alt+F4. 

It is noteworthy that render problems appear only in the place where the open application should theoretically be located. The rest of the desktop works correctly.


STEPS TO REPRODUCE
1. Install ArchLinux
2. Install Proprietary drivers for Nvidia
3. Add kernel option for running driver in modesettings mode (dvidia-drm.modset=1)
4. Inslall Plasma-meta, plasma-wayland-session and sddm
5. Install chromium
6. Start Plasma Wayland
7. Open chromium


Measures taken:
1. Reboot system - Nothing has changed
2. Changing compositor backend - Nothing has changed


EXPECTED RESULT
Correct rendering of opened applications.


SOFTWARE/OS VERSIONS
Operating System: Arch Linux 2020.12.01
KDE Plasma Version: 5.20.4
KDE Frameworks Version: 5.77.0
Plasma Wayland: plasma-wayland-session-5.20.4-1
Egl Wayland: egl-wayland-1.1.6-1
Nvidia Driver: nvidia-455.45.01-7
Qt Version: 5.15.2
Kernel Version: 5.9.14-arch1-1
OS Type: 64-bit
Processors: 20 × Intel® Core™ i9-10900K CPU @ 3.70GHz
Memory: 31.3 GiB of RAM
Graphics Processor: GeForce RTX 3080/PCIe/SSE2


ADDITIONAL INFORMATION
To be honest, I'm not completely sure that this bug is due to KDE. When running KDE on Xorg, there are no such problems, but there are microfreezes of animations,  that's why I want to switch to Wayland. But on the same system, next to KDE, I installed Gnome and when running Gnome Wayland, no artifacts are observed. On the Windows 10 operating system, too, everything works. I came to the conclusion that the problem is not with wayland or the graphics card. Perhaps can be a problem in the Nvidia drivers, but Gnome works without problems...
Comment 1 Ihor 2020-12-30 11:56:25 UTC
Created attachment 134401 [details]
Render artifacts.
Comment 2 Vlad Zahorodnii 2021-01-05 08:26:28 UTC
Cannot reproduce with Radeon.
Comment 3 Ihor 2021-01-05 12:12:44 UTC
After a detailed study of the problem of Nvidia and closed proprietary drivers, the topic can be closed. The problem of microfreezes on Xorg was solved by increasing the minimum frequency of the video card to 450 Mhz using nvidia-smi (It works exactly for my card).
Comment 4 Nate Graham 2021-01-05 18:42:02 UTC
Oh wow, thanks for the update! So I imagine this means the issue is in the Nvidia driver for now doing this automatically for that particular card.

Please report this issue to the Nvidia folks, either by sending an email to linux-bugs@nvidia.com or making a post at https://forums.developer.nvidia.com/c/gpu-unix-graphics/linux/

It would be helpful to the Nvidia developers if you could run nvidia-bug-report.sh and attach the resulting file in your report.

Thanks again!