Am Dienstag, 15. Mai 2018, 22:17:22 CEST schrieb Yuri: > OK, I've "fixed" the thing. > > It's all related to OS/GNOME default color profiles. GNOME contains a > GUI utility available under Settings - Color. Inside this utility just > select your output screen, add Standard space - sRGB profile and > enable it. Restart your apps (Firefox, DT, GNOME image viewers, etc.) > and you are done. > > The only down-side is darktable-cmstest starts nagging after you set > sRGB profile: > > darktable-cmstest version 2.4.3 > 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 > > LVDS-1 the X atom and colord returned different profiles > X atom: _ICC_PROFILE (15400 bytes) > description: sRGB > colord: > "/home/<username>/.local/share/icc/edid-1be6e0958dcbf558460fe50a8d95abc6.ic > c" description: ThinkPad T430 > > Better check your system setup > - some monitors reported different profiles > You may experience inconsistent color rendition between color managed > applications
So it's the auto-generated edid profile. We saw problems with that in the past already. No idea why GNOME keeps thinking those are useful. First of all you should now check why setting the display profile in GNOME doesn't set it in colord. Besides that you can tell darktable in its preferences to only look into the X atom for display profiles. That should make all applications use the configured sRGB. Tobias [...]
signature.asc
Description: This is a digitally signed message part.
