Broken chromium 141 colors with HDR

[VlaDexa]

That is not how a github page should look like. This happened when I updated chromium to 141, which [enabled color management support by default](https://www.phoronix.com/news/Chrome-Lands-Wayland-CM) . Also this happens only when an app gets launched on my HDR monitor, my second non-HDR monitor is displaying fine. Other wayland HDR apps (mpv, games) seem to work fine.

Versions

All the packages come from nixpkgs 7df7ff7 (current nixos-unstable head)

vladexa@workstation ~> chromium --version
Chromium 141.0.7390.54 

vladexa@workstation ~> hyprland --version
Hyprland 0.51.1 built from branch v0.51.1-b at commit 71a1216abcc7031776630a6d88f105605c4dc1c9  ([gha] Nix: update inputs).
Date: 2025-09-22
Tag: v0.51.1, commits: 71a1216abcc7031776630a6d88f105605c4dc1c9
built against:
 aquamarine 0.9.4
 hyprlang 0.6.3
 hyprutils 0.8.4
 hyprcursor 0.1.13
 hyprgraphics 0.1.6


no flags were set

Monitor config

vladexa@workstation ~> hyprctl monitors
Monitor DP-2 (ID 0):
	[email protected] at 0x0
	description: Xiaomi Corporation Mi Monitor 5744900055116
	make: Xiaomi Corporation
	model: Mi Monitor
	physical size (mm): 600x340
	serial: 5744900055116
	active workspace: 1 (1)
	special workspace: 0 ()
	reserved: 0 55 0 0
	scale: 1.00
	transform: 0
	focused: yes
	dpmsStatus: 1
	vrr: false
	solitary: 0
	solitaryBlockedBy: windowed mode,missing candidate
	activelyTearing: false
	tearingBlockedBy: next frame is not torn,user settings,missing candidate
	directScanoutTo: 0
	directScanoutBlockedBy: user settings,missing candidate
	disabled: false
	currentFormat: XRGB2101010
	mirrorOf: none
	availableModes: [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] 

Monitor HDMI-A-1 (ID 1):
	[email protected] at 2560x0
	description: Samsung Electric Company LC27G5xT HK7W701831
	make: Samsung Electric Company
	model: LC27G5xT
	physical size (mm): 600x340
	serial: HK7W701831
	active workspace: 2 (2)
	special workspace: 0 ()
	reserved: 0 55 0 0
	scale: 1.00
	transform: 0
	focused: no
	dpmsStatus: 1
	vrr: false
	solitary: 0
	solitaryBlockedBy: windowed mode,missing candidate
	activelyTearing: false
	tearingBlockedBy: next frame is not torn,user settings,missing candidate
	directScanoutTo: 0
	directScanoutBlockedBy: user settings,missing candidate
	disabled: false
	currentFormat: XRGB2101010
	mirrorOf: none
	availableModes: [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected]
	```

[UjinT34]

Try #11914

[VlaDexa]

It's a lot better. Now it's just darker than it was or should be. Firefox for reference

[UjinT34]

Hard to tell without config. I see some difference with my config but it's much less obvious. Probably some SDR -> HDR settings are applied when they shouldn't or some HDR -> SDR mapping isn't correct. Chrome is always in HDR mode now.

[VlaDexa]

I've got sdrbrightness set to 1.2. I guess that no longer applies to chrome since it's in HDR mode now
hyprland.conf

[mastergopher]

@UjinT34 thanks for the fix in #11914

@VlaDexa I have the same "dark chromium" issue unfortunately. Seems like chromium no longer respects hyprland's HDR configurations.

As a workaround, try using chromium flag --disable-features=WaylandWpColorManagerV1. I recommend putting it in ~/.config/chromium-flags.conf.

This fixes the issue for me, even on chromium versions >= 141.

[ctilley83]

I can't open chromium in wayland mode after pulling the mentioned commit. It opens when I set the --ozone-platform to x11, but wayland gives the following error. Almost seems that chromium is trying to set a render mode that doesn't exist yet in libwayland

WARNING: radv is not a conformant Vulkan implementation, testing use only.
[38626:38626:1003/175840.881399:ERROR:ui/ozone/platform/wayland/host/wayland_wp_image_description.cc:219] Incomplete image description info from compositor.
[38626:38626:1003/175840.971992:ERROR:ui/events/platform/wayland/wayland_event_watcher.cc:47] libwayland: wp_color_management_surface_v1#47: error 0: Unsupported render intent

[1003/175840.974759:ERROR:third_party/crashpad/crashpad/snapshot/elf/elf_dynamic_array_reader.h:64] tag not found
[1]    38626 trace trap (core dumped)  chromium

My hyprland monitor config
monitor = DP-4,5120x2160@72, 0x0, 1.25, bitdepth, 8, cm, srgb.

[UjinT34]

It's either debug:full_cm_proto = 1 hitting unsupported bits or chromium trying to access unsupported features without checking.
bitdepth, 8, cm, srgb is better with render:cm_enabled = 0. No point in CM stuff if it's always reduced to default srgb.

[teachmain]

I think I have same problem. But I am not using any hdr stuff, as long as I set the cm as edid or wide, the chromium will become colorless.

My monitor config as

monitor=eDP-1, 2240x1400@60, 0x0, 1.25, cm, edid

chromium and hyprland version as:

$  chromium --version
Chromium 141.0.7390.76 Arch Linux

$ hyprland --version
Hyprland 0.51.1 built from branch  at commit 71a1216abcc7031776630a6d88f105605c4dc1c9  ([gha] Nix: update inputs).
Date: Mon Sep 22 20:54:03 2025
Tag: v0.51.1, commits: 6436
built against:
 aquamarine 0.9.5
 hyprlang 0.6.3
 hyprutils 0.10.0
 hyprcursor 0.1.13
 hyprgraphics 0.2.0


no flags were set

monitor info as:

$ hyprctl monitors 
Monitor eDP-1 (ID 0):
	[email protected] at 0x0
	description: Lenovo Group Limited 0x403C
	make: Lenovo Group Limited
	model: 0x403C
	physical size (mm): 300x190
	serial: 
	active workspace: 1 (1)
	special workspace: 0 ()
	reserved: 0 30 0 0
	scale: 1.25
	transform: 0
	focused: yes
	dpmsStatus: 1
	vrr: false
	solitary: 0
	solitaryBlockedBy: windowed mode,missing candidate
	activelyTearing: false
	tearingBlockedBy: next frame is not torn,user settings,missing candidate
	directScanoutTo: 0
	directScanoutBlockedBy: user settings,missing candidate
	disabled: false
	currentFormat: XRGB8888
	mirrorOf: none
	availableModes: [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected]