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 690349 - Selected color profile won't stay applied
Selected color profile won't stay applied
Status: RESOLVED FIXED
Product: gnome-control-center
Classification: Core
Component: Color
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Richard Hughes
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2012-12-17 14:16 UTC by Dražen Lučanin
Modified: 2013-09-12 14:26 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
dependencies (7.98 KB, text/plain)
2012-12-17 14:16 UTC, Dražen Lučanin
Details
sudo /usr/lib/x86_64-linux-gnu/colord/colord -v > /home/kermit/colord.log (52.77 KB, text/x-log)
2012-12-23 18:52 UTC, Dražen Lučanin
Details
/usr/lib/gnome-settings-daemon/gnome-settings-daemon --debug > /home/kermit/gnome-settings-daemon.log (44.32 KB, text/x-log)
2012-12-23 18:53 UTC, Dražen Lučanin
Details

Description Dražen Lučanin 2012-12-17 14:16:31 UTC
Created attachment 231722 [details]
dependencies

When I select a new color profile for a screen in the color menu of the control center it goes back to the default after a reboot. When I go to select it again in the color menu, it shows the right colors on the screen for approx. 1 second and then flips back to the default profile (the radio button stays on the new profile, though).

Expected behaviour - the color profile should stay the same after a reboot. Selecting a new profile in the color menu should stick and not flip back after 1 second.

To reproduce:
- add and select a new profile in the color menu
- restart the machine
- the profile is not applied any more and you can't select it in the options for longer than 1 second

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: gnome-control-center 1:3.4.2-0ubuntu0.4
ProcVersionSignature: Ubuntu 3.2.0-30.48-generic 3.2.27
Uname: Linux 3.2.0-30-generic x86_64
ApportVersion: 2.0.1-0ubuntu12
Architecture: amd64
Date: Mon Sep 3 13:19:48 2012
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
SourcePackage: gnome-control-center
UpgradeStatus: Upgraded to precise on 2012-04-28 (127 days ago)
usr_lib_gnome-control-center:
 activity-log-manager-control-center 0.9.4-0ubuntu3
 deja-dup 22.0-0ubuntu2
 gnome-bluetooth 3.2.2-0ubuntu5
 indicator-datetime 0.3.94-0ubuntu2

Forwarded from Launchpad:

https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1045281
Comment 1 Richard Hughes 2012-12-17 14:28:41 UTC
As you're not running the systemd logging stuff, you'll have to launch the daemon manually in verbose mode:

sudo killall colord
sudo /usr/libexec/colord -v
(or wherever ubuntu puts that binary)

and then in a different tab;

killall gnome-settings-daemon
(press alt-f4 to dismiss the fail whale)
/usr/libexec/gnome-settings-daemon --debug

and in a different tab:

killall gnome-control-center
gnome-control-center -v

Then please try to change the profile in gnome-control-center. Please attach the *full* outputs from colord, gnome-settings-daemon and gnome-control-center -- thanks.
Comment 2 Dražen Lučanin 2012-12-23 18:52:51 UTC
Created attachment 232155 [details]
sudo /usr/lib/x86_64-linux-gnu/colord/colord -v > /home/kermit/colord.log
Comment 3 Dražen Lučanin 2012-12-23 18:53:24 UTC
Created attachment 232156 [details]
/usr/lib/gnome-settings-daemon/gnome-settings-daemon --debug > /home/kermit/gnome-settings-daemon.log
Comment 4 Dražen Lučanin 2012-12-23 19:02:48 UTC
Hi Richard,

I did as you told me. I didn't find the exact commands, but I think these are the closest in Ubuntu:

    sudo /usr/lib/x86_64-linux-gnu/colord/colord -v > /home/kermit/colord.log
    /usr/lib/gnome-settings-daemon/gnome-settings-daemon --debug > /home/kermit/gnome-settings-daemon.log
    gnome-control-center -v > /home/kermit/gnome-control-center.log

(the gnome-settings-daemon also has a *-3.0 version, I didn't use that one)

I attached the first two files. The last one is empty.

An interesting thing happend, so I don't know how usefult the logs will be. When I did the `killall gnome-settings-daemon`, my desktop environment shortly switched to a failsafe environment (everything looked Windows 98-ish) and after it went back to normal after a few seconds, the correct color scheme got applied. Because of that, I couldn't reproduce the bug in the control center - the profile I chose would stay applied. Is it maybe possible that restarting the gnome-settings-daemon once the whole system is up fixes the error? That might mean there is some timing problem - one service needing another one to be already running.

Cheers,
Dražen
Comment 5 Richard Hughes 2013-07-16 16:18:35 UTC
Could you try with colord 1.0.0 or newer please? We've solved a few timing bugs there in the past.
Comment 6 Dražen Lučanin 2013-07-16 17:26:36 UTC
How can I upgrade to >=1.0? Is there a PPA or should I try some development image (I see that Ubuntu 13.10 ships it in the proposed archive https://launchpad.net/ubuntu/+source/colord )
Comment 7 Dražen Lučanin 2013-09-05 12:13:35 UTC
OK, I tried it out again and it now works - the profile I chose stays applied even after a restart. I am now running Ubuntu 13.04 and colord version 0.1.30-0ubuntu3.

(sorry for taking so long, I don't have regular access to this machine any more)
Comment 8 Rui Matos 2013-09-12 14:26:01 UTC
(In reply to comment #7)
> OK, I tried it out again and it now works

Thanks. Closing