Bug 499673 - Laptop internal (OLED) display is not recognized as HDR-capable
Summary: Laptop internal (OLED) display is not recognized as HDR-capable
Status: CONFIRMED
Alias: None
Product: kwin
Classification: Plasma
Component: platform-drm (other bugs)
Version First Reported In: 6.2.5
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
: 502017 (view as bug list)
Depends on:
Blocks:
 
Reported: 2025-02-08 09:15 UTC by dantmnf
Modified: 2025-12-20 17:27 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
drm_info (159.26 KB, text/plain)
2025-02-08 09:16 UTC, dantmnf
Details
kscreen-doctor (860 bytes, text/plain)
2025-02-08 09:16 UTC, dantmnf
Details
EDID dump (256 bytes, application/octet-stream)
2025-02-08 09:17 UTC, dantmnf
Details

Note You need to log in before you can comment on or make changes to this bug.
Description dantmnf 2025-02-08 09:15:54 UTC
SUMMARY
The internal (OLED) display of Asus Zenbook S 14 notebook is not recognized as HDR-capable by kwin.

STEPS TO REPRODUCE
1. Start Plasma Wayland session
2. Attempt to turn on HDR

OBSERVED RESULT
In the Display & Monitor section of Settings, there is no option to enable HDR.

EXPECTED RESULT
In the Display & Monitor section of Settings, there should be option to enable HDR.

SOFTWARE/OS VERSIONS
Windows: HDR is functioning properly.
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: 6.13.1-arch1-1
KDE Plasma Version: 6.2.5
KDE Frameworks Version: 6.10.0
Qt Version: 6.8.2

ADDITIONAL INFORMATION
HDR for external display works as it should be.
Comment 1 dantmnf 2025-02-08 09:16:31 UTC
Created attachment 178069 [details]
drm_info
Comment 2 dantmnf 2025-02-08 09:16:56 UTC
Created attachment 178070 [details]
kscreen-doctor
Comment 3 dantmnf 2025-02-08 09:17:15 UTC
Created attachment 178071 [details]
EDID dump
Comment 4 Zamundaaa 2025-02-10 16:45:39 UTC
That EDID only says it's HDR capable in the DisplayID extension bits, which libdisplay-info doesn't parse yet. Once that's fixed, this should work.
Comment 5 Zamundaaa 2025-02-10 17:32:56 UTC
Git commit 979e1b88c7e6df635ea877035ec72ca1ea90a6bb by Xaver Hugl.
Committed on 10/02/2025 at 16:59.
Pushed by zamundaaa into branch 'master'.

utils/edid: port to higher level libdisplayinfo API for colorimetry information

M  +17   -33   src/utils/edid.cpp

https://invent.kde.org/plasma/kwin/-/commit/979e1b88c7e6df635ea877035ec72ca1ea90a6bb
Comment 6 Zamundaaa 2025-05-21 14:21:26 UTC
*** Bug 502017 has been marked as a duplicate of this bug. ***
Comment 7 Eduardo Correia 2025-12-20 17:27:58 UTC
I have two OLED modern laptops, Asus Zephyrus G14 2024 (OLED 2.8K 120Hz) and a Lenovo Legion Pro 5i 2025 (OLED 2.5K QHD 165Hz). Both have HDR capable displays, on Windows both have Dolby Vision certification and HDR color profiles out of the box. HDR works beautifully on both, in Windows, and the Lenovo can even reach 1200 nits over HDR. However, both of them are totally unrecognized on KDE. Running "kscreen-doctor -o" gives HDR as "incapable" on both, where it is not true.