[argyllcms] Re: dispwin sets the wrong X.org _ICC_PROFILE atom
- From: Graeme Gill <graeme@xxxxxxxxxxxxx>
- To: argyllcms@xxxxxxxxxxxxx
- Date: Wed, 16 Nov 2016 17:25:24 +1100
Niccol├▓ Belli wrote:,
I'm using argyllcms 1.9.2 through displaycal 184.108.40.206 and I noticed that it
sets the wrong
X.org _ICC_PROFILE atom: eDP1 gets the profile of DP1-1 and DP1-1 gets the
DP1-8. DP1-8 gets the right profile. On the contrary colord gets all the
(at least if I use xiccd because colord-kde doesn't enumerate my DP-MST
I suspect that this is simply a symptom of the lack
of standardization with regard to the root window _ICC_PROFILE
atom when used with XRANDR (i.e. the "ICC Profiles in X Specification").
It doesn't cover the fact that a screen may have multiple Outputs,
and it seems that Richard and I have punted in different directions
Typically this shouldn't cause any problems, because an application dealing
with XRANDR based displays should look at the _ICC_PROFILE property set in the
rather than for a root window atom, since there is no ambiguity about this, and
it gives the (more likely) correct information for different screen regions.
I think I will make some changes to this though, to restrict setting the
_ICC_PROFILE_xxx value to just the first working Output of the corresponding
Screen, to make it more backwards compatible with non XRANDR aware applications.
I'll suggest an update to the specification to prompt wider X11 application
compatibility, and see if there is any consensus.
Other related posts: