SUMMARY I clicked ‘enable HDR’ on one of my monitors and something broke. The whole system froze up and the HDR monitor went black. If I reboot it freezes right after I login. If I unplug that monitor or start in X11 instead of Wayland then everything is fine. Plugging the HDR monitor in while I’m logged into a Wayland session also freezes everything. How can I disable the HDR setting? The monitor doesn’t show in System Settings whilst its unplugged so I’m hoping theirs some way to fix it on the CLI. The only place I’ve found HDR referenced is .config/kwinoutputconfig.json. I set HDR to false but after reboot it’s set to true again. I also tried deleting .config/kwinrc and .local/share/kscreen but no luck. STEPS TO REPRODUCE 1. Enable HDR on Monitor in System Settings > Display OBSERVED RESULT - HDR monitor goes black - Other monitor now unresponsive. - System works if monitor is not plugged in on start up - Cannot disable HDR setting in UI without the monitor plugged in. If I plug in the monitor then the system freezes. - Monitor also does not appear in kscreen-doctor when unplugged. EXPECTED RESULT - System does not freeze - Saved monitor settings can be modified or cleared even when disconnected. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.3 ADDITIONAL INFORMATION Lemmy Community Discussion https://lemmy.kde.social/post/1104524 Similar to https://bugs.kde.org/show_bug.cgi?id=483600 but if I use only the HDR monitor it still has the issue. Fixed by - Ctrl + Alt + F3 to go into terminal - Set `HighDynamicRange` and `WideColorGamut` to false in ~/.config/kwinoutputconfig.json - Execute `plasmashell --replace` - Reboot, Login, Reattach HDR Monitor - AMD based Desktop - Nvidia GPU - Dual Monitor Setup (BenQ and Gigabyte) - HDR setting enabled on Gigabyte. - Installation is approximately 4 years old.
hardware probe: https://linux-hardware.org/?probe=66b49c3998
We're gonna need some debug information, ideally from both KWin and the driver side. The best way to get it is probably to enable HDR, disconnect the monitor, log out, switch to a tty, connect the monitor again and then run the script from https://invent.kde.org/plasma/kwin/-/wikis/Debugging-DRM-issues Afterwards, just attach kwin-drm-debug.log and dmesg-drm-debug.log here
Created attachment 168730 [details] kwin-drm-debug.log
Created attachment 168731 [details] dmesg-drm-debug.log
hmm, I see nothing obviously wrong in there. There's a few atomic tests that fail with "needs modeset", but that's a normal part of KWin's startup sequence, and at the very end of the log I see KWin successfully doing a modeset to turn the screens on. Maybe the problem only happens later... Could you bump the "sleep 3" in the script to "sleep 20" or something like that, and attach the logs for that again?
I changed it to 90 seconds for good measure. It might also be worth noting that I can't recover the system once the monitor is plugged in. It locks up immediate (at least visually) and even after disconnecting the monitor it doesn't start working again. Even trying to switch out to terminals once the monitor is disconnected doesn't work. Need to reboot to get back in.
Created attachment 168990 [details] kwin-drm-debug 90 seconds wait
Created attachment 168991 [details] dmesg-drm-debug 90 second wait
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
Whoops. Didn't know I needed to set Status to Reported