| Summary: | Background flickers through to foreground when using Display Stream Compression via DisplayPort | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | Mike Dawson <mikedawson> |
| Component: | general | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED UPSTREAM | ||
| Severity: | normal | CC: | mikedawson, xaver.hugl |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Mike Dawson
2025-06-01 23:23:31 UTC
KWin has neither control nor even knowledge about DSC. Please report this to NVidia at https://forums.developer.nvidia.com/c/gpu-graphics/linux. (In reply to Zamundaaa from comment #1) > KWin has neither control nor even knowledge about DSC. Please report this to > NVidia at https://forums.developer.nvidia.com/c/gpu-graphics/linux. since this doesn't happen in Gnome, I assumed it was a KDE bug There are a large random-seeming reasons for why synchronization bugs can become visible or invisible, and it not happening on Gnome for you doesn't mean all that much. The difference could come from lower latency, higher bit depth, different compositing shaders, different optimizations, or anything else that can cause even tiny timing differences. If the driver side investigation finds that we should be doing something differently, do reopen this bug report. But that driver side investigation needs to happen first - especially while other reports of artifacts with DSC are currently floating around, like https://forums.developer.nvidia.com/t/displayport-dsc-4k-240hz-flickering-artifacts/294490 Thank you, I will post on the nvidia forums that you linked |