Here is a new video of the issue :
Was this not also reproduced in lab by @amrits ?
https://forums.developer.nvidia.com/t/nvidia-555-58-4k-120hz-causes-flickering-artifacting-on-x-and-wayland-with-arch/298187/46?u=borna.vincek1
Yes, it was a repro but was not consistent, Anyway we got this reproduced again and engineering team is taking a look.
4 Likes
Hello, any update on this? @amrits can you make sure the engineering team is looking into this?
The DSC flickering has been a problem for several years now and is a very bad look for nvidia on linux for people with high-end expensive monitors (the same people that normally buy the most expensive nvidia cards)
It’s definitely in your best interest to fix this soon
@mdawson2 that attitude wont make this go faster
you mentioned for several years, do you have a date of the driver, or something so they can cross check, giving them most datapoints would be the fastest way to fix this
I’m on CachyOS.
A month ago, I still had a 4090. When I was in KDE, I had this exact same bug in KDE.
For reference, this is my monitor setup:
My only solution was to honestly not use KDE anymore. I went full hyprland. In hyprland, I had 0 issues with any kind of flickering.
3 Weeks ago I upgraded to a 5090 and just today I decided to test if the flickering still occurs. Installed KDE, made a user for clean dotfiles and: There are no longer any kind of issues present with flickering.
I had read somewhere that apparently the 40 series uses two internal display-port heads when it is connected to a DSC-Display. Since both my displays are an older generation with DP 1.4, they obviously use DSC to achieve 1440p@360 and 4k@240. And since I have two DSC displays, it’s technically using all four internal heads to display it. It could be related to this?
Back then I had whatever driver was the latest one in december 2025, so probably 580.
Now I’m on 590 though. Not sure if some bugfix may have fixed it in that driver verison or if this truly is related to DSC + pre 50 series cards. It could also be a KDE compositor bug, since this issue was never appearing in hyprland (which also uses wayland).
I hope this information can help!
1 Like
Also having this issue at 4K@240hz, no issues at 4K@120hz as shown in the video. I can consistently reproduce the issue while scrolling on a browser.
The monitor is an Alienware AW3225QF with 125% scaling, plugged to the DisplayPort on my 4080.
System info:
Operating System: Fedora Linux 43
KDE Plasma Version: 6.5.5
KDE Frameworks Version: 6.22.0
Qt Version: 6.10.1
Kernel Version: 6.18.6-200.fc43.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 9800X3D 8-Core Processor
Memory: 64 GiB of RAM (62.4 GiB usable)
Graphics Processor: NVIDIA GeForce RTX 4080
Manufacturer: ASRock
Product Name: B650E PG Riptide WiFi
NVIDIA Driver Version: 580.119.02
NVML Version: 13.580.119.02
Here are the EDIDs from all my monitors:
monitor-edid.txt (20.6 KB)
If any additional info could help, just let me know and I can provide it.
I have used several driver versions and never had this issue with my 4090 and an Asus PG32UCDM. I wonder if it is some desktop effect maybe not working nicely with the higher refresh.
Did you only have one monitor? If so, you’re only using two internal hardware heads. Which would explain your issue-free experience.
Yep, I will have to try this later with another monitor hooked up.
For what it’s worth I’m also experiencing this with a 4070 Super on CachyOS with a 1440@360Hz monitor! Hoping it can get fixed soon 🙏