GNOME Bugzilla – Bug 788026
If time is incorrect on login, and is corrected after, Night Light does not correct itself
Last modified: 2018-06-05 13:24:50 UTC
Right now there's a bug on Solus that makes it so I have to manually connect to the Internet by clicking on Wired Connection ( https://dev.solus-project.com/T4108 ), and until I do so, my time is incorrect. This makes Night Light have an incorrect color temperature for the display, and it doesn't seem to ever correct itself. I can fix it by switching to manual, then back to "sunset to sunrise". If I use Redshift instead, it corrects itself fairly quickly. However, when it works, Night Light works better for me (Redshift sometimes flickers off momentarily on my computer) so I'd prefer to use it - but right now it's inconvenient.
I can also just toggle Night Light off and back on again. That also causes a correction.
Hm, right. It seems that if your clock moves backwards, then we are not picking up on that and the re-check may not happen for a long time. I am actually a bit confused by the code. It makes a point on waiting for a specific point in time, but also sets this point in time to 1 minute in the future. Seems a bit there was the idea to only wake up when the next change is required. Anyway, I added a patch to fix this into https://gitlab.gnome.org/GNOME/gnome-settings-daemon/merge_requests/21 Closing is fixed already, assuming that the patch will be merged soon.