[trop]

I'm curious about this as well, but wouldn't be pointing fingers at the Wayland developers. See, for example, one of the most recent comments in the discussion linked to in the parent post, by Nilvus, one of the (wise and knowledgeable) darktable developers:

> The only thing is that color management for Wayland is progressing and far from being completely done. Even if work is quite slow, things seems to go in good direction. For correct and complete Wayland color management, we just have to wait again.

Blender itself seems to be color-profile aware: https://docs.blender.org/manual/en/latest/render/color_manag....

Here is an issue tracking work on Wayland: https://gitlab.freedesktop.org/wayland/wayland-protocols/-/m....

There's a nice site which is parallel to this work which summarizes issues/goals: https://gitlab.freedesktop.org/pq/color-and-hdr

Here is parallel work on this in Sway: https://github.com/swaywm/sway/issues/1486 And parallel work in KDE: https://bugs.kde.org/show_bug.cgi?id=439135

I can't find any reference to color management in the Blender meta-issue at https://developer.blender.org/T76428. For X11, I believe applications would have to manually determine the color profile of the display holding the current window, then query colord or and X atom to determine the profile. The application would then manually do the colorspace conversion. Does querying colord and making an in-application conversion works for Wayland until Wayland becomes colorspace-aware? Or if there are more wrinkles?