Wrong color display

[anonymousgrasshopper]

The colors displayed by kitty do not match the ones that should be displayed. Meaning all color output in the terminal is slightly off compared to what it should be; this includes my kitty colorscheme, but also the ones of tuis, shell, etc. For instance, the output of kitten @ get-color | grep "^background" is not the background color I actually see on my screen. Most colors are modified a bit (exepted a few like #000000, #ff0000, ...).
The issue is resolved by forcing kitty to run on XWayland instead of Wayland (so not a kitty config issue). Furthermore, I tried moving all of my .config, .local and .cache elsewhere to see if it changes anything, and reinstalling kitty through the kitty-git AUR package, but the issue remained. The only thing I found on the web related to that is this post, which is still unresolved. Other terminal emulators like Ghostty work just fine.
Does anyone have any idea how I could troubleshoot that ?

[kovidgoyal]

Your wayland compositor has a buggy implementation of the color management protocol. Try a different compositor.

[MrRoiz]

Same here, after upgrading my packages, there was a Hyprland upgrade, seems like there's no issue created in that repo yet.

[kovidgoyal]

The following patch, will work around the issue by preventing kitty from using the wayland color management protocol:

diff --git a/glfw/wl_window.c b/glfw/wl_window.c
index 8cd724a9b..3d5cc15f8 100644
--- a/glfw/wl_window.c
+++ b/glfw/wl_window.c
@@ -587,7 +587,7 @@ create_surface(_GLFWwindow* window, const _GLFWwndconfig* wndconfig) {
     wl_surface_add_listener(window->wl.surface, &surfaceListener, window);
     wl_surface_set_user_data(window->wl.surface, window);
 
-    if (_glfw.wl.color_manager.has_needed_capabilities) {
+    if (_glfw.wl.color_manager.has_needed_capabilities && false) {
         ensure_color_manager_ready();
         if (_glfw.wl.color_manager.image_description && !window->wl.color_management) {
             window->wl.color_management = wp_color_manager_v1_get_surface(

[anonymousgrasshopper]

Thank you for your quick reply, this worked. @MrRoiz opened a discussion on Hyprland.

[kovidgoyal]

And I tested it under kwin, mutter and hyprland with

kitty --config=NONE -o 'background=#1e1e1e'

In kwin with kcolorchooser the reported background color is #1e1e1e in hyprland 0.53.0 it is #232323. In GNOME using org.gnome.Shell.Screenshot.PickColor it is #1e1e1e. These are the three compositors that support this protocol.

You should report the issue to hyprland. If it helps tell them that kitty is using WP_COLOR_MANAGER_V1_TRANSFER_FUNCTION_SRGB and WP_COLOR_MANAGER_V1_PRIMARIES_SRGB with WP_COLOR_MANAGER_V1_RENDER_INTENT_PERCEPTUAL