The problem is still present in Raring (13.04). If gtk-redshift is added
as a startup application, geoclue-ubuntu-geoip crashes after login.

To build upon's Jeremy's workaround (#48), you can also specify provider
and your location in ~/.config/redshift.conf – this way, gtk-redshift
always uses correct settings. Configuration example follows:

[redshift]
location-provider=manual

[manual]
lat=<latitude>
lon=<longitude>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/868904

Title:
  Redshift fails to start with session due to geoclue failure

To manage notifications about this bug go to:
https://bugs.launchpad.net/redshift/+bug/868904/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to