The -l lat:lon is what I use and sufficient for me, but the workaround is insufficient, though, from a design perspective. For example, both my parents and my girlfriend just think the program is completely broken if they try to use it while not connected to the internet.
Both Unity and Gnome allow setting your current location. Redshift should probably do the following automatically by default unless given a manual over-ride (such as using the -l lat:lon option): 1. Try to find current location using geoclue and internet connection 2. If #1 doesn't work, fall back to using Unity / Gnome location in the clock applet 3. If #2 doesn't work, fall back to using last-known good startup location 4. If #3 doesn't work, prompt use to enter a location manually at least once using the -l switch (so it can create a config file and fall back to #3 next time) -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
