I am having an issue in wayland sessions after updating to driver 555: generally the problem manifests itself in random flickery graphical glitches on an external monitor.
Laptop: Lenovo Legion 7 16ACHg6 (AMD Ryzen 7 5800H + NVIDIA GeForce RTX 3070 Mobile / Max-Q)
Monitor: Xiaomi Curved Gaming Monitor 34" (3440x1440) - Xiaomi Curved Gaming Monitor 34" – Xiaomi Australia
Software: Arch Linux, KDE Plasma 6.1
Happens:
- Both with monitor being connected over HDMI and DisplayPort (via a Type-C dock, as it’s not exposed directly on this laptop)
- Both with XWayland and native Wayland windows
- Both with
NVreg_EnableGpuFirmware
not set and set to0
- Both when the app runs on the AMD iGPU and on the Nvidia GPU (with
prime-run
)
Doesn’t happen:
- On X11
- On the laptop screen (I believe, unlike external monitor ports, it’s connected to my iGPU)
- On an older Nvidia driver (550.90.07)
(I haven’t tested all the combinations of these factors, but rather changed one variable at a time. My “default” configuration is DisplayPort over Type-C, with the monitor running at 144 fps)
The higher the display FPS, the worse the issue is: tested from 50 fps to 144 fps. With 144 fps it happens very often. With 50 fps it is comparatively rarer, but still quite reproducible.
The patters look somewhat like checkerboard (albeit with rectangular squares), often showing the contents of a previously visible window (see repro_osu_lazer_map_selection_2
in the attacked archive). They are also often located on the edges of the screen.
Happens in, seemingly, every application. The most reliable way to reproduce for me was to use osu! lazer 2024.625.2 with no framerate limit on the stable OpenGL renderer, with the external monitor running at 144 fps. Then the glitches are either visible on the main menu screen or in the map selection screen when selecting a random map with F2.
Also happens with:
- Minecraft 1.20.4, walking or even standing
- resizing large windows
- going into fullscreen on YouTube in Firefox
- watching a photo or video in telegram desktop
Here’s a result of running the nvidia-bug-report.sh script: nvidia-bug-report.log.gz (1.8 MB)
And here’s an archive with multiple videos of the bug being visible: repro_videos.zip (48.5 MB)
Hope this will help you reproduce and fix this issue!