https://bugs.kde.org/show_bug.cgi?id=496991
--- Comment #7 from Akhil K <akhilkalwakur...@gmail.com> --- (In reply to Zamundaaa from comment #6) > 2. the Intel kernel driver is still broken when it comes to handling the > Colorspace property, and your monitor is one of the many that don't actually > enable HDR unless that works properly. If your screen has an OSD where it > shows whether or not HDR is enabled, please check that, and if you have > another device with an AMD or NVidia GPU, you could check with that as well. It's an laptop with hybrid GPU setup. So, there's no OSD to show if HDR is enabled. I do have a mux switch to connect the display to dGPU. Tried this and with Nvidia and it looks correct. I don't have a measuring device but, I used a lightmeter app on my phone to check the brightness on both intel (~200 lux) and nvidia (~600 lux). So, I guess it's an intel issue then. Happens with both i915 and xe drivers > For testing 2, if you're willing to compile KWin, you could also try > changing BT2020_RGB in > https://invent.kde.org/plasma/kwin/-/blob/Plasma/6.2/src/backends/drm/ > drm_pipeline.cpp?ref_type=heads#L300 to BT2020_YCC I think my screen doesn't support BT2020_YCC according to EDID. CE colorimetry data xvYCC601 support......... No xvYCC709 support......... No sYCC601 support.......... No AdobeYCC601 support...... No AdobeRGB support......... No BT2020CYCC support....... No BT2020YCC support........ No BT2020RGB support........ Yes Metadata profile flags... 0x80 -- You are receiving this mail because: You are watching all bug changes.
