Bug 514928

Summary:	When brightness set to 100% Screen become abnormally bright
Product:	[Plasma] kwin	Reporter:	freddum <fred.dumois>
Component:	compositing	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	major	CC:	timwcx, xaver.hugl
Priority:	NOR
Version First Reported In:	6.5.5
Target Milestone:	---
Platform:	Fedora RPMs
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	screenshot

Description freddum 2026-01-22 06:14:35 UTC

Created attachment 188780 [details]
screenshot

***
If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports

Please remove this comment after reading and before submitting - thanks!
***

SUMMARY
(Please see attachement my English is not perfect)
I'm on Think pad laptop, when i put screen brightness 100%  after couple of minutes, screen has tendency to become a white screen (screeshot taken by Spectacle), when i set brightness back to 95% it intently back to normal 
I experienced this issue after 6.5.5 update , I'm using this computer on Kde since March last year 

I have the feeling this happen only on google chrome window as long as I detected 

Fun fact, I have an external screen on HDMI, this do not happen on the external screen only on built in

STEPS TO REPRODUCE
1. put brightness on 100% (regardless on HDR on off)
2. open geogle chrome 
3. wait couple of seconds

OBSERVED RESULT
Google chrome rendering go to white, even if you reduce the window and get it back it stay the same , you neeed to close chrome and open again

EXPECTED RESULT
google chrome render correctly  suppose

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora 43 
KDE Plasma Version: 6.5.5
KDE Frameworks Version:6.22.0 
Qt Version: 6.10.1

ADDITIONAL INFORMATION

Comment 1 timwcx@qq.com 2026-01-22 08:37:25 UTC

I have encountered the same problem and managed to capture the terminal logs when the white screen occurs. The errors confirm a failure in the Wayland color management handshake between Chromium and KWin:

[11807:11807:0122/154756.558929:ERROR:ui/ozone/platform/wayland/host/wayland_wp_color_manager.cc:214] Failed to populate image description for color space {r:[0.6368, 0.3298], g:[0.2917, 0.6017], b:[0.1486, 0.0586], w:[0.3127, 0.3290]}, transfer:SRGB, matrix:RGB, range:FULL}
[11807:11807:0122/154756.559091:ERROR:ui/ozone/platform/wayland/host/wayland_wp_color_manager.cc:296] Unable to set image transfer function.
[11807:11807:0122/154756.559128:ERROR:ui/ozone/platform/wayland/host/wayland_wp_color_management_surface.cc:63] Failed to create color management surface.

Analysis: This issue appears to be related to the Chromium implementation of the color management protocol, similar to what has been reported for Brave (see: https://github.com/brave/brave-browser/issues/50027). The white screen occurs when the browser fails to communicate color space parameters via the wp-color-management-v1 protocol. This failure consistently coincides with setting the screen brightness to 100%.

Workaround: For anyone facing this issue, disabling the Wayland Color Management feature in Chromium-based browsers prevents the white screen. Launch the browser with this flag: --disable-features=WaylandWpColorManagerV1

Comment 2 Zamundaaa 2026-01-22 13:04:26 UTC


*** This bug has been marked as a duplicate of bug 514868 ***