Public bug reported:
When I restart my laptop on a train without wifi, redshift restarts, and
geolocation fails due to no network connection. But I probably set the
system time correctly, which provides at least an approximation of the
right thing to do. Alternatively, falling back on my last location isn't
an all bad option, at least compared to the current behavior of exiting
and not working at all.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: redshift 1.8-0ubuntu6
ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
Uname: Linux 3.13.0-35-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.4
Architecture: amd64
CurrentDesktop: ratpoison
Date: Thu Sep 18 07:37:54 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2013-12-21 (270 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
SourcePackage: redshift
UpgradeStatus: Upgraded to trusty on 2014-06-21 (88 days ago)
** Affects: redshift (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1370862
Title:
feature request: fall back on timezone when geolocation unavailable
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/redshift/+bug/1370862/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
