I know that this is something that has been discussed before but I’m unable to find the solution.
Sidenote: this may be something new since my update to Ubuntu 22.04, I don’t think I’ve noticed this before… I may be wrong about that and simply did not notice it before.
So the problem is this, that darktable-cmstest returns this message:
(base) aadm@psion:~ $ darktable-cmstest darktable-cmstest version 4.0.0 this executable was built with colord support enabled darktable itself was built with colord support enabled primary CRTC is at CRTC 0 CRTC for screen 0 CRTC 1 has no mode or no output, skipping CRTC for screen 0 CRTC 2 has no mode or no output, skipping CRTC for screen 0 CRTC 3 has no mode or no output, skipping CRTC for screen 0 CRTC 4 has no mode or no output, skipping CRTC for screen 0 CRTC 5 has no mode or no output, skipping CRTC for screen 0 CRTC 6 has no mode or no output, skipping DP-0 the X atom and colord returned different profiles X atom: _ICC_PROFILE (724 bytes) description: sRGB built-in colord: "/home/aadm/.local/share/icc/SW2700 #1 2022-12-15 10-00 120cdm² D6500 2.2 F-S XYZLUT+MTX.icc" description: SW2700 #1 2022-12-15 10-00 120cdm2 D6500 2.2 F-S XYZLUT+MTX Better check your system setup - some monitors reported different profiles You may experience inconsistent color rendition between color managed applications
As you see I have a profile calculated with displayCAL (the fork by @eoyilmaz, compiled from source), and it looks like this is correctly “loaded” into the system.
First of all I don’t properly understand X atom and colord, I’ve understood they’re two different tools to “load” the profile into the system and you have the option to choose which one to use in prefs/“miscellaneous”/“interface” section/“ (and I’ve deliberately set "method to use for getting the display profile” → “colord” intead of “all” since colord sees the correct profile).
Anyway I would have happily disregarded the above msg but when I run dt (or ansel) I see these msg when opening an image in the darkroom:
(base) aadm@psion:~ $ ansel [get_output_profile] called with ICC type -1 [colorspaces] Trying to fetch embedded profile. image 56154 embedded color profile NOT found embedded matrix NOT found [colorspaces] could not fetch the profile. [colorspaces] WARNING: no colorspace found, sRGB will be tagged in final exported file. Colors may be inconsistent
Can anybody pls tell me if this is a problem, how can I check if an exported image is properly “calibrated”, i.e. what color profile it’s been assigned / if sRGB is indeed what I should aim for when I send for example this photo to an outside printing service or to share with others, how to make “X atom” load the same profile that colord sees, etc
(I know it’s a lot of things and probably confused and surely many of you will send me back to some earlier post that I’ve probably read but haven’t realized its pertinence to my question etc…)
Disclaimer: I have read (as suggested by @claes) the section “Loading The Profile In Your User Session” in https://encrypted.pcode.nl/blog/2013/11/24/display-color-profiling-on-linux/ but really I don’t understand how to do that, check if this is already present in my system, what is xiccd, etc…
Disclaimer bis: I have also read lots of other threads as mentioned above!