Redshift fails to obtain location from gnome-clock
Bug #891674 reported by
Morgen
This bug report is a duplicate of:
Bug #868904: Redshift fails to start with session if no external location provider is available.
Edit
Remove
This bug affects 7 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Redshift |
New
|
Undecided
|
Unassigned | ||
| Debian |
New
|
Unknown
|
|||
Bug Description
As a work around to Bug #868904 I was attempting to set the location via gnome-clock. However it appears that Redshift looks for the gnome-clock city location under the wrong path. I get the following error:
Error reading city list: `/apps/
No city selected as current city.
Initialization of gnome-clock failed.
I check the location set Time & Date, and changed the location to another nearby city with the same result. Let me know if I can provide any additional information.
Revision history for this message
| LeandroDoctors (ldoctors-gmail) wrote | #1 |
| Changed in debian: | |
| status: | Unknown → New |
To post a comment you must log in.
I have had the same problem since I switched to GNOME 3 in Debian "testing". This is the output from the console.
$ redshift
Cannot list GNOME panel applets.
Initialization of gnome-clock failed.
Trying next provider...
Latitude and longitude must be set.
$ gtk-redshift
Cannot list GNOME panel applets.
Initialization of gnome-clock failed.
Trying next provider...
Latitude and longitude must be set.