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 693846 - Color calibration profiles are not automatically applied to monitors
Color calibration profiles are not automatically applied to monitors
Status: RESOLVED OBSOLETE
Product: gnome-color-manager
Classification: Core
Component: general
3.6.x
Other Linux
: Normal major
: ---
Assigned To: gnome-color-manager-maint
gnome-color-manager-maint
Depends on:
Blocks:
 
 
Reported: 2013-02-14 22:51 UTC by Russell Harrison
Modified: 2013-06-10 08:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Russell Harrison 2013-02-14 22:51:40 UTC
After creating then applying a profile for my monitor and rebooting my machine I find that the profile is not applied to my display when I log in and instead the default display profile is being used.

On opening the color settings I also don't see the profile I created even listed as an option for my monitor but it is in the list of available profiles when I click on the "Add Profile" button.

Every time I log into Gnome I have to perform the following:
1. Click on the user menu and click on "System Settings" to open the control center
2. Open the "Color" control panel
3. Click the "Add profile" button.
4. Find the most recent profile I've generated in the list and click the "Add" button
  * Note I've gone to including YYYY-MM-DD in my profile descriptions because without it (if I accept the default when generating a new profile) there isn't a way to know which one is the most recent until all of them have been imported into the control panel.
5. Select the "imported" profile to activate it and have it applied to my display.
6. Most of the time I'll click the "Set for all users" button even though it seems to have no effect.

This issue has also been reported downstream:
https://bugzilla.redhat.com/show_bug.cgi?id=847421

I see this issue on Fedora 18:
gnome-color-manager-3.6.1-1.fc18.x86_64

argyllcms-1.4.0-6.fc18.x86_64
argyllcms-doc-1.4.0-6.fc18.x86_64
colord-0.1.28-1.fc18.x86_64
colord-extra-profiles-0.1.28-1.fc18.noarch
colord-gtk-0.1.22-3.fc18.x86_64
colord-libs-0.1.28-1.fc18.i686
colord-libs-0.1.28-1.fc18.x86_64
color-filesystem-1-10.noarch
Comment 1 Richard Hughes 2013-02-15 14:26:40 UTC
I'm pretty sure this was fixed in 0.1.29 -- can you try with the packages here please: https://admin.fedoraproject.org/updates/FEDORA-2013-2053/
Comment 2 Tobias Mueller 2013-06-10 08:47:07 UTC
Let's assume this to be OBSOLETE then. Please reopen if this is not the case.