Bug 490415

Summary: Color corruption after resume from sleep
Product: [Plasma] kwin Reporter: Jonathan L Hanmann <jhanmann>
Component: colour-managementAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED UPSTREAM    
Severity: major CC: xaver.hugl
Priority: NOR    
Version First Reported In: master   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: Drm Info after wake from sleep with latest (post 6.1.2) KWIN
Drm Info after wake from sleep with latest (post 6.1.2) KWIN (After Ctrl-Alt-F2)

Description Jonathan L Hanmann 2024-07-17 18:13:24 UTC
SUMMARY

Problem only occurs with kwin build > v6.1.2. All other Plasma 6 components are newly built using kde-builder. Switching KWIN back to v6.1.2 appears to correct the screen/color corruption issue. Failing system is a Radxa Rock-5b (Rockchip RK3588 SoC) running Armbian Ubuntu 24.04 with all updates. Qt 6.7.1 is also installed.

STEPS TO REPRODUCE
1.  Put system to sleep.
2. Press power button to wake system from sleep.
3. Screen has what appears to be corrupted color mapping, i.e., image is visible but hard to read because colors are wrong.

OBSERVED RESULT

What appear to be corrupted colors are on the text consoles (Alt-Shift-F3, etc.) and the KDE Plasma graphical screen (Alt-Shift-F1). This appeared to happen in KWIN versions prior to 6.1.2 on my system also but switching to the text consoles and then switching back to the graphical screen corrected the screen corruption. With versions after KWIN v6.1.2 it doesn't appear possible to correct the screen/color corruption without a reboot.

EXPECTED RESULT

System should resume correctly.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma:  Armbian Ubuntu 24.10/KDE Plasma 6 from repo with kde-builder.
(available in About System)
KDE Plasma Version: 6.1.80
KDE Frameworks Version: 6.5.0
Qt Version: 6.7.1

ADDITIONAL INFORMATION
Comment 1 Jonathan L Hanmann 2024-07-17 21:12:44 UTC
It appears that the screen/color corruption can be corrected after the resume from sleep by switching to the login screen (Ctrl-Alt-F2) then switching back to the lockscreen (Ctrl-Alt-F1).

p.s. The Alt-Shift-Fx below should have been Ctrl-Alt-Fx. A mistaken key sequence on my part.
Comment 2 Zamundaaa 2024-07-18 12:57:18 UTC
Please attach the output of drm_info with 6.1.2, with git master before the glitches and with git master while the glitches are visible.
You can get the output from a different device with ssh if the screen isn't usable at all
Comment 3 Jonathan L Hanmann 2024-07-18 13:45:57 UTC
Created attachment 171758 [details]
Drm Info after wake from sleep with latest (post 6.1.2) KWIN

This is a run (as root) of drm_info after resuming from sleep. Run on text console prior to switching to login console (Ctrl-Alt-F2) to recover screens. Text console is solid green background but still actually functional.
Comment 4 Jonathan L Hanmann 2024-07-18 13:52:28 UTC
Created attachment 171760 [details]
Drm Info after wake from sleep with latest (post 6.1.2) KWIN (After Ctrl-Alt-F2)

This is a run (as root) of drm_info after resuming from sleep. Run on text console *after* to switching to login console (Ctrl-Alt-F2) to recover screens. Text console is now normal visibility.
Comment 5 Jonathan L Hanmann 2024-07-18 13:55:33 UTC
This is with the latest KWIN build and running. I did a drm_info capture with the screens corrupted and after fixing the screen corruption by switching to console Ctrl-Alt-F2 (the original login console). This is different than what you were asking and I will get that also but I thought it might also be helpful to see the before and after drm info in this situation as well. There are some differences visible.
Comment 6 Zamundaaa 2024-07-18 15:02:17 UTC
> I thought it might also be helpful to see the before and after drm info in this situation as well
It is; the only difference is that the working version has a gamma lut set, and the broken one does not. This is a bug in the display driver, please report it to rockchip