Re: Custom profiles dropped by display prefs after screensaver
Re: Custom profiles dropped by display prefs after screensaver
- Subject: Re: Custom profiles dropped by display prefs after screensaver
- From: Martin Diers <email@hidden>
- Date: Fri, 19 Feb 2010 15:56:56 -0600
Well, you know what they say about hunches... :)
Being on IT manager, to my knowledge, there is no way for any IT
department to force a profile to be loaded in OS X.
In this case, the problem described by Thom is a known issue in 10.5.8
(and I think one or two other 10.5.x revs). It only appears to happen
when there are two monitors involved. It can also happen when the
machine wakes from sleep. The screen saver does not even need to come on.
If one opens Display Preferences and goes to the Color tab, the correct
profiles are immediately loaded. In other words, the OS knows which
profiles it SHOULD be using, and by opening Display Preferences, it sort
of wakes up and fixes the problem without you even having to click on
the correct profile. That is why renaming profiles has no effect. As far
as I can tell, the problem is actually not that it is loading the wrong
profiles, but rather that it is not loading any profiles at all, and the
graphics card's LUT is in its default state.
This bug has been fixed in Snow Leopard, but as far as I know, Apple
never released the fix for Leopard.
On 2/19/10 2:56 PM, Marco Ugolini wrote:
> Thom Schroeder wrote:
>
>
>> Anyone else having this problem?
>>
>> Equipment/OS:
>> Mac Pro 2.66GHz Quad-Core/Eizo CG211/ACD 20/OS 10.5.8
>>
>> When my screensaver kicks on (our IT enforces a 15-minute max period of
>> inactivity before launching into screensaver mode so I cannot set to
>> 'Never') and it comes out of screensaver, one or both (sometimes none, this
>> is sporadic) of my custom monitor profiles for the Eizo (main display) and
>> Apple (secondary) are dropped by Displays Preferences. The machine reverts
>> back to the OS auto-generated profiles.
>>
>> The only fix I have been able to find is to keep the display prefs icon in
>> the menu bar and click it, open the prefs and the machine then kicks back
>> into the custom profiles.
>>
>> I tried creating custom profiles and naming the same as what the OS auto
>> profiles are named and replacing them in the
>> HD/Library/ColorSync/Profiles/Displays folder but no luck. This seems to be
>> a bug between what I can only assume the OS and this particular machine as I
>> did not have this issue on a previous Mac Pro 2x2.66GHz dual-core.
>>
>> This may very well be some issue with the user profile our IT department set
>> up when they configured this machine for me but before I go back to them and
>> have my machine completely re-imaged I wanted to find out if anyone else is
>> also having this particular issue. Our IT has our machines fairly locked
>> down so I cannot test very much (like install a previous OS update, etc.).
>>
> I'm saying this based on a hunch, but I would suggest that you talk to the IT people. My guess is that the active user profile defines the OS-created profile as the active one, instead of the custom one, and that whenever the CPU comes out of sleep mode that's what that user profile forces it to revert to.
>
> IT people are usually smart and capable, but they may tend to think they know more than they do, specially about issues having to do with color management.
>
> One thing seems clear: if the company cares about color-managed workflows, the present situation is (ob)noxious, and cannot be allowed to continue.
>
> Marco Ugolini
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Colorsync-users mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Colorsync-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden