SUMMARY When enabeling HDR, SDR Colour Intensity slider seems to do nothing. STEPS TO REPRODUCE 1. Enable HDR 2. Apply settings 2. Move SDR Colour Intensity slider 3. Apply settings OBSERVED RESULT HDR is enabled, slider appears to do nothing. EXPECTED RESULT HDR is enabled, slider adjusts colours. SOFTWARE/OS VERSIONS Operating System: EndeavourOS KDE Plasma Version: 6.1.3 KDE Frameworks Version: 6.4.0 Qt Version: 6.7.2 Kernel Version: 6.9.10-arch1-1 (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION Graphics Processor: AMD Radeon RX Vega Monitor: LC-Power 32QHD-165-C-K (reported by system as Beihai Century Joint Innovation Technology Co., Ltd. 32QHD-165-C-K)
Updated Version. Bug still present in Plasma 6.1.5.
SOFTWARE/OS VERSIONS Operating System: EndeavourOS KDE Plasma Version: 6.1.5 KDE Frameworks Version: 6.5.0 Qt Version: 6.7.2 Kernel Version: 6.10.9-arch1-2 (64-bit) Graphics Platform: Wayland
It's still seems to be a bug in Plasma 6.2.3.
Please attach the parsed EDID for your screens. You can get that like so: > edid-decode /sys/class/drm/card1-eDP-1/edid (with the card and connector name adjusted for your setup)
Created attachment 175789 [details] Output of edid-decode command Hopefully this will give enough info.
(In reply to Alexander Streng from comment #5) > Created attachment 175789 [details] > Output of edid-decode command > > Hopefully this will give enough info. Decided to add more info about my system: Operating System: Fedora Linux 41 KDE Plasma Version: 6.2.3 KDE Frameworks Version: 6.8.0 Qt Version: 6.8.0 Kernel Version: 6.11.7-300.fc41.x86_64 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 7735HS with Radeon Graphics Memory: 14.9 GiB of RAM Graphics Processor: AMD Radeon RX 7600S Manufacturer: ASUSTeK COMPUTER INC. Product Name: ASUS TUF Gaming A16 FA617NS_FA617NS System Version: 1.0
Created attachment 175827 [details] Another affected EDID Bug persists for me too, please find my EDID attached as well
hmm, the color capabilities look pretty close to those of my monitor, where the difference is definitely noticeable. (In reply to Gregor from comment #7) > Created attachment 175827 [details] > Another affected EDID > > Bug persists for me too, please find my EDID attached as well That > Failures: > > Block 1, CTA-861 Extension Block: > Colorimetry Data Block: Reserved bits MD0-MD3 must be 0. > EDID conformity: FAIL might be relevant. Does KWin parse any warnings in its log about it? You can check it with > journalctl --user-unit plasma-kwin_wayland --boot 0
(In reply to Zamundaaa from comment #8) > hmm, the color capabilities look pretty close to those of my monitor, where > the difference is definitely noticeable. > > (In reply to Gregor from comment #7) > > Created attachment 175827 [details] > > Another affected EDID > > > > Bug persists for me too, please find my EDID attached as well > That > > Failures: > > > > Block 1, CTA-861 Extension Block: > > Colorimetry Data Block: Reserved bits MD0-MD3 must be 0. > > EDID conformity: FAIL > might be relevant. Does KWin parse any warnings in its log about it? You can > check it with > > journalctl --user-unit plasma-kwin_wayland --boot 0 Not as far as I can see: Nov 15 17:20:09 user-desktop systemd[1555]: Starting KDE Window Manager... Nov 15 17:20:09 user-desktop systemd[1555]: Started KDE Window Manager. Nov 15 17:20:09 user-desktop kwin_wayland[1600]: No backend specified, automatically choosing drm Nov 15 17:20:10 user-desktop kwin_wayland_wrapper[1764]: The XKEYBOARD keymap compiler (xkbcomp) reports: Nov 15 17:20:10 user-desktop kwin_wayland_wrapper[1764]: > Warning: Unsupported maximum keycode 708, clipping. Nov 15 17:20:10 user-desktop kwin_wayland_wrapper[1764]: > X11 cannot support keycodes above 255. Nov 15 17:20:10 user-desktop kwin_wayland_wrapper[1764]: > Warning: Could not resolve keysym XF86KbdInputAssistPrevgrou Nov 15 17:20:10 user-desktop kwin_wayland_wrapper[1764]: > Warning: Could not resolve keysym XF86KbdInputAssistNextgrou Nov 15 17:20:10 user-desktop kwin_wayland_wrapper[1764]: Errors from xkbcomp are not fatal to the X server Nov 15 17:20:10 user-desktop kcminit[1770]: Initializing "/usr/lib/qt6/plugins/plasma/kcms/systemsettings/kcm_fonts.so" Nov 15 17:20:10 user-desktop kcminit[1770]: Initializing "/usr/lib/qt6/plugins/plasma/kcms/systemsettings/kcm_style.so" Nov 15 17:20:17 user-desktop kwin_wayland[1600]: Module 'org.kde.kwin.decoration' does not contain a module identifier directive - it cannot be protected from external registrations. Nov 15 17:20:17 user-desktop kwin_wayland[1600]: kwin_core: Cannot grant a token to KWin::ClientConnection(0x62797e054fe0) Nov 15 17:20:17 user-desktop kwin_wayland[1600]: kwin_core: Cannot grant a token to KWin::ClientConnection(0x62797e1dbe80) Nov 15 17:20:17 user-desktop kwin_wayland[1600]: kwin_core: Cannot grant a token to KWin::ClientConnection(0x62797e1dbe80) Nov 15 17:20:18 user-desktop kwin_wayland[1600]: kf.windowsystem: static bool KX11Extras::mapViewport() may only be used on X11 Nov 15 17:20:38 user-desktop kwin_wayland[1600]: kf.windowsystem: static bool KX11Extras::mapViewport() may only be used on X11 Nov 15 17:27:26 user-desktop kwin_wayland[1600]: kf.windowsystem: static bool KX11Extras::mapViewport() may only be used on X11 Nov 15 17:29:35 user-desktop kwin_wayland[1600]: kf.windowsystem: static bool KX11Extras::mapViewport() may only be used on X11 Nov 15 19:13:54 user-desktop kwin_wayland[1600]: kwin_core: Cannot grant a token to KWin::ClientConnection(0x62797eb125e0) Nov 15 19:13:54 user-desktop kwin_wayland[1600]: kwin_core: Cannot grant a token to KWin::ClientConnection(0x62797eb125e0) Nov 15 19:14:08 user-desktop kwin_wayland[1600]: kwin_core: Cannot grant a token to KWin::ClientConnection(0x62797f4691f0) Nov 15 19:14:18 user-desktop kwin_wayland[1600]: kwin_core: Cannot grant a token to KWin::ClientConnection(0x62797f4691f0) Nov 15 19:16:01 user-desktop kwin_wayland[1600]: kf.windowsystem: static bool KX11Extras::mapViewport() may only be used on X11 Nov 15 19:18:31 user-desktop kwin_wayland[1600]: kf.windowsystem: static bool KX11Extras::mapViewport() may only be used on X11 Nov 15 19:32:24 user-desktop kwin_wayland[1600]: kf.windowsystem: static bool KX11Extras::mapViewport() may only be used on X11 Worth mentioning: Adjusting brightness works on Linux. Also: While this is (relatively) cheap china tech, HDR is recognized and seems to work on Windows. That said, there is no colour adjustment I think
Might help: My monitor does NOT have (or claim to have, according to Windows) any HDR certification. It just communicates its max. brightness etc.
Created attachment 176082 [details] journalctl --user-unit plasma-kwin_wayland --boot 0 output
(In reply to Alexander Streng from comment #11) > Created attachment 176082 [details] > journalctl --user-unit plasma-kwin_wayland --boot 0 output Here's my monitor's output as well. Here's also monitor's specs: https://www.msi.com/Monitor/MAG-345CQR
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone!