On Wednesday 22 June 2016 20:29:19 I. Ivanov wrote: > Hi Tobias, > > Yes - it is dispcal (displaycal - 3.1.3.1). It is Ubuntu 14.04 64 bit
That has been known to make problems, especially when used at the same time as other means (like colord, which you are using, too). > The result of the command is below. HDMI-0 is the IPS screen (and critical) [...] > HDMI-0 the X atom and colord returned the same profile > X atom: _ICC_PROFILE (768956 bytes) > description: GW2765 #1 2016-06-17 16-39 2.2 F-S XYZLUT+MTX > colord: "/home/bojo/.local/share/icc/GW2765 #1 2016-06-17 16-39 > 2.2 F-S XYZLUT+MTX.icc" > description: GW2765 #1 2016-06-17 16-39 2.2 F-S XYZLUT+MTX Here the X atom and colord are both set to the same/correct profile. Good. > LVDS1 the X atom and colord returned different profiles > X atom: _ICC_PROFILE_1 (0 bytes) > description: (none) > colord: "/home/bojo/.local/share/icc/8MN61-156AT #2 2016-06-15 > 21-07 2.2 F-S XYZLUT+MTX.icc" > description: 8MN61-156AT #2 2016-06-15 21-07 2.2 F-S XYZLUT+MTX Here only colord is correctly configured, setting the X atom for the 2nd screen is probably not supported by dispcal. > Better check your system setup > - some monitors reported different profiles > You may experience inconsistent color rendition between color managed > applications I would just configure darktable to only use colord to retrieve the display profile. Then even moving the windows between screens should correctly work. To test your setup you could for example set the display profile of one screen to be this test profile: https://houz.org/tmp/BRG.icc and see if darktable recognizes it – the difference should be obvious. > Regards, > > B Tobias [...]
signature.asc
Description: This is a digitally signed message part.
