https://bugs.kde.org/show_bug.cgi?id=525650
Bug ID: 525650
Summary: HDR + Wide Color Gamut cause a black screen on cold
boot and resume from sleep
Classification: Plasma
Product: kwin
Version First 6.7.5
Reported In:
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: colour-management
Assignee: [email protected]
Reporter: [email protected]
CC: [email protected]
Target Milestone: ---
Created attachment 196090
--> https://bugs.kde.org/attachment.cgi?id=196090&action=edit
kscreen-doctor outpu
DESCRIPTION
HDR + Wide Color Gamut cause a black screen on cold boot and resume from sleep,
but apply and persist correctly when enabled in a running session
STEPS TO REPRODUCE
1. In System Settings → Display Configuration, enable HDR on the internal
display.
2. Either reboot, or suspend and resume.
OBSERVED RESULT
Screen stays black. No automatic recovery observed on cold boot. Recovery
requires a TTY and manually clearing highDynamicRange / wideColorGamut in
~/.config/kwinoutputconfig.json
EXPECTED RESULT
HDR/WCG apply the same way they do when toggled live
SOFTWARE/OS VERSIONS
Operating System (available in the Info Center app, or by running `kinfo` in a
terminal window): Fedora Linux 44 (Kinoite)
KDE Plasma Version: 6.7.5
KDE Frameworks Version: 6.30.0
Qt Version: 6.11.12
ADDITIONAL INFORMATION
kwin: 6.7.5-1
plasma-workspace: 6.7.5-1
Graphics platform: Wayland
GPU: Intel Lunar Lake integrated, xe driver
Display: internal panel, EDID identifier SDC 16903, 2880×1800 @ 120Hz, OLED,
HDR-capable
Enabling HDR + WCG live, in an already-running session, applies immediately
with no issue, and survives multiple subsequent logout/login cycles without
failing — the problem is specific to a fresh initialization (cold boot,
resume), not to KWin restarting.
ICC profile assignment was tested independently and ruled out — the same
failure occurs with iccProfilePath/hdrIccProfilePath blank.
On multiple occasions, applying HDR live triggered an immediate black screen
that self-reverted after KScreen's own confirm/revert timeout. That safety net
does not appear to engage on the cold-boot or resume path.
A recurring line appears on every boot, ~20s after driver init, possibly
unrelated: xe 0000:00:02.0: [drm] *ERROR* Tile0: GT1: GSC proxy component not
bound!
--
You are receiving this mail because:
You are watching all bug changes.
