Heavy Flickering on Second Display using Plasma Login Manager or SDDM running on Wayland #1022
Description
NVIDIA Open GPU Kernel Modules Version
580.119.02
Please confirm this issue does not happen with the proprietary driver (of the same version). This issue tracker is only for bugs specific to the open kernel driver.
- I confirm that this does not happen with the proprietary driver package.
Operating System and Version
Fedora 43 KDE
Kernel Release
Linux 6.18.8-200.fc43.x86_64
Please confirm you are running a stable release kernel (e.g. not a -rc). We do not accept bug reports for unreleased kernels.
- I am running on a stable kernel release.
Hardware: GPU
RTX 4060
Describe the bug
So I have two monitors, the main one is 1080p 144hz and the second one is a 1280 x 1024 monitor that can reach up to 75hz and it's positioned on the left of my main monitor, and basically as you can see from the picture, I experience heavy flickering only on that second monitor, and only when SDDM or Plasma Login Manager are running on Wayland, and I've seen this issue happen with the COSMIC login manager as well once.
Basically this flickering happens either when I log out and go in the login screen, or after I log in, and this flickering doesn't happen all the time, but it happens pretty frequently, and the only workaround is that after the flickering starts, I turn off the monitor and turn it on again.
I have also reported this bug to the NVIDIA Linux developers forum:
https://forums.developer.nvidia.com/t/heavy-flickering-on-second-display-using-plasma-login-manager-or-sddm-running-on-wayland/360308
I've already reported this bug to SDDM and to KDE Plasma but it seems like it a NVIDIA driver issue:
https://bugs.kde.org/show_bug.cgi?id=514276
sddm/sddm#2123
To Reproduce
Two ways to reproduce:
1: log out of KDE and go to the login screen (it doesn't matter if it's SDDM or Plasma Login Manager as this bug happens with both of them)
2: log in
Bug Incidence
Sometimes
nvidia-bug-report.log.gz
I've run the bug report from the 580.119.02 driver but this bug is still happening with the latest 590 driver too.
More Info
No response