After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 751775 - spurious colord authentication request on login for remote session
spurious colord authentication request on login for remote session
Status: RESOLVED OBSOLETE
Product: gnome-settings-daemon
Classification: Core
Component: color
3.16.x
Other Linux
: Normal normal
: ---
Assigned To: Richard Hughes
gnome-settings-daemon-maint
Depends on:
Blocks:
 
 
Reported: 2015-07-01 11:23 UTC by Pierre Ossman
Modified: 2019-03-20 11:28 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Pierre Ossman 2015-07-01 11:23:01 UTC 
Recent versions of colord has switched from rejecting requests for remote sessions, to requiring authentication (commit 26dc57de). Unfortunately Gnome makes such requests whenever it sees a new monitor. That means you get evil focus stealing modal dialog boxes without user interaction.

Prime case is a VNC session. You'll get one dialog on login, and another as VNC adds new monitors to deal with client multi-head.
Comment 1 Pierre Ossman 2015-07-01 11:25:33 UTC 
The request in question is "org.freedesktop.color-manager.create-device" with the message "Authentication is required to create a color managed device".
Comment 2 Pierre Ossman 2015-10-16 13:07:56 UTC 
The code in question is gnome_rr_screen_output_added_cb() which calls gcm_session_add_state_output() which unconditionally tries to add a new colord device for every RandR output it sees.

I suggest holding off on creating a colord device until the user tries to actually modify the color profile.
Comment 3 GNOME Infrastructure Team 2019-03-20 11:28:12 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues/273.