Re: gcm not working for second logged in user



On Thu, Jul 22, 2010 at 1:11 PM, Pascal de Bruijn <pmjdebruijn pcode nl> wrote:
> On Wed, Jul 21, 2010 at 10:26 AM, Richard Hughes <hughsient gmail com> wrote:
>> On 20 July 2010 22:58, Pascal de Bruijn <pmjdebruijn pcode nl> wrote:
>>> User 2 logs in
>>> gcm-prefs loads videolut (from a different profile)
>>> gcm-prefs sets profile atom for user 2
>>
>> Yes, this is a valid bug. We probably should get our GSD plugin to
>> watch for ConsoleKit changes (the ACTIVE attribute) but really this
>> needs some proper session support. I really don't want to add yet
>> another session process just watching for a session active state
>> change.
>
> Well it's a very rare use case tho...
>
> Since screen calibration is inherently a system properly and not
> really a user thing...

I disagree.

Profiling the monitor is inherently a system thing (presumably it's
the *same* monitor for all users).  The LUT setting is a different
story.  One user might want 6500K, another might want 7000K, and a
third might want no correction at all for maximum 3D gamut because
they know that whatever program they care about is already using a
CLUT profile.  A fourth user might run dispwin -c themselves and the
first user might want their calibration back when they switch back.

(Of course, the profile to use depends on the LUT, but that's "just"
an implementation detail.)

>
> It could become a user thing when two users disagree on what
> gamma/white point should be profiled against... But then again, there
> isn't that much debate about this, and even so, a single shop will
> standardize to a single setting...

You should get a Lenovo X series laptop.  I had to calibrate mine to
6000K because the screen is *so* bad that I lose an annoying amount of
brightness and get rather crappy results if I calibrate to anything
else.  (Last I checked, the calibration GUI doesn't have that setting,
so I just did it manually with dispcal.)


But I'm not sure there's a problem at all.  Don't the two users have
their own X servers, and shouldn't the X server restore the LUT on its
own?  (I *think* that drv-intel 2.9.0 or newer with recent xserver is
smart enough.)

--Andy


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]