Bug 500021

Summary: Night Light seems to cause weird graphical issues
Product: [Plasma] kwin Reporter: Tarballwalf <unzippedtarball>
Component: performanceAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal CC: xaver.hugl
Priority: NOR    
Version First Reported In: 6.3.0   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: Desktop artifacts/graphical issues

Description Tarballwalf 2025-02-13 20:33:31 UTC
Created attachment 178317 [details]
Desktop artifacts/graphical issues

SUMMARY
I was playing Baldur's Gate 3 and CS2 today while having Night Light on. I have noticed that the desktop became sluggish while playing BG3 and seconds later, the whole entire desktop, along with some Electron programs (Discord) started having weird graphical issues. 

After trying CS2, everything was fine except the Steam that overlay started being extremely sluggish and having weird graphical issues.

I have attached an image of the graphical issues.
STEPS TO REPRODUCE
1. Open a game on the NVIDIA GPU (as of now, I have found that the desktop graphical issues only happen with BG30
2. Leave the game running for a while
3. Tab out and try to use Discord
4. Notice how after a while things start to go crazy
5. All of these while having Night Light on

OBSERVED RESULT
Upon turning off Night Night, while playing BG3 the general sluggishness of the desktop went away along with the artifacting of the desktop and I have have noticed that CS2 gained 100fps compared compared to when I had Night Light on. 

EXPECTED RESULT
Desktop and general performance should not be impacted by this.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux
KDE Plasma Version: 6.3.0
KDE Frameworks Version: 6.10.0
Qt Version: 6.8.2

ADDITIONAL INFORMATION
I am running on a laptop in hybrid mode, with an Intel iGPU and an NVIDIA dGPU, running the Wayland session.
Comment 1 Zamundaaa 2025-02-14 13:31:31 UTC
I don't know about those glitches, but the issue is almost certainly resolved by the same commit as bug 499987

*** This bug has been marked as a duplicate of bug 499987 ***