Above mentioned work around works without active internet connection. i.e, redshift doesn't go looking for geolocations if you use this workaround.
But if we tuse terminal and use command : $ redshift (it shows) ** (process:3248): WARNING **: Metadata for error domain "geoclue-error- quark" already registered Started Geoclue provider `Geoclue Master'. Using provider `geoclue'. Could not get location (3 retries left): Geoclue master client has no usable Position providers. Unable to get location from provider. But when you type command $ gtk-redshift -l LAT:LONG (Where LAT and LONG correspond with your coordinates.) it runs soomthly as send in the above question. Hence forth a startup application is created using this command. By the way when you click Applications>Accessories>Redshift it works through geolocation and needs a active internet connection every time where as the little workout in http://askubuntu.com/questions/194525 /does-redshift-need-active-internet-connection-to-work/194582#194582 helps the otherway by mannually creating the geolocation. -- 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
