Wayland: Remove usage of the Wayland color management protocol to inform compositors of the color space used by kitty

As is typical with Wayland, the protocol is poorly designed and
implemented even worse. Hyprland 0.53 has completely broken color
management.
https://github.com/hyprwm/Hyprland/discussions/12788
In addition it and mangowc crash when using color management with nouveau drivers.
https://github.com/kovidgoyal/kitty/issues/9030

KDE kwin does not support the sRGB transfer function. And the geniuses
at Wayland are any way planning to deprecate sRGB as a transfer function.

Only GNOME mutter seems to get it right.

Then there are people that are likely going to shoehorn this into EGL
instead of leaving it under application control via the protocol anyway.
https://github.com/KhronosGroup/EGL-Registry/issues/197

Sigh. Wayland.
This commit is contained in:
Kovid Goyal
2026-01-15 09:53:09 +05:30
parent d35c786358
commit 9ef934cf54
5 changed files with 3 additions and 124 deletions

View File

@@ -192,6 +192,9 @@ Detailed list of changes
with frames that dispose onto background with non-zero delay using the native
engine (:iss:`9376`)
- Wayland: Remove usage of the wayland color management protocol to inform
compositors of the color space used by kitty
0.45.0 [2025-12-24]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~