[PATCH] Find the correct applet
Bug #598277 reported by
Gabriel de Perthuis
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Redshift |
Fix Released
|
Undecided
|
Jon Lund Steffensen |
Bug Description
The current code to find the clock applet finds an applet that might not be enabled. That can happen when an applet or a panel is deleted; it will still exist in gconf thanks to a schema, but won't be referenced anywhere. The patch enumerates only enabled applets.
Related branches
Changed in redshift: | |
status: | New → Confirmed |
Changed in redshift: | |
status: | Confirmed → Fix Committed |
Changed in redshift: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
I'm seeing this bug too. On my desktop computer, redshift launches fine without any parameters (so it manages to get the info from my clock's timezone/city), but on my laptop it doesn't work:
"No city selected as currenty city.
Initialization of gnome-clock failed."
Both computers have the city/timezone set identically. I saw that the laptop has lots of old applets listed in gconf that aren't actually there.