https://bugs.kde.org/show_bug.cgi?id=514928
[email protected] <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #1 from [email protected] <[email protected]> --- 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 -- You are receiving this mail because: You are watching all bug changes.
