Hide Forgot
Description of problem: Timezone is not updated automagically even though set to be in GNOME Control Center. I am currently working in the US Eastern Time Zone, and my laptop thinks it is the Pacific Time Zone. Version-Release number of selected component (if applicable): control-center-3.20.1-1.fc24.x86_64 systemd-229-13.fc24.x86_64 Steps to Reproduce: I live in US Eastern Time Zone (Raleigh, NC). I flew to Vegas with my laptop (US Pacific Time Zone), the timezone updated at some point just fine. I did not note when this happened. Going home... I suspended the laptop and flew back home (Raleigh, NC) -- PT to ET I notice the laptop refuses to update the timezone properly and remains in PT. Additional info: I checked my settings: GNOME Control Center > Date & Time ... Yup! Automatic Date & Time and Automatic Time Zone are both on. I even turned off the time zone switch ...waited a bit... and tuned it back on. No change. For reference here are the results of timedatectl: [taw@rh ~]$ timedatectl Local time: Mon 2016-09-12 05:36:37 PDT Universal time: Mon 2016-09-12 12:36:37 UTC RTC time: Mon 2016-09-12 12:36:37 Time zone: America/Los_Angeles (PDT, -0700) Network time on: yes NTP synchronized: yes RTC in local TZ: no
Additional information... chronyd. chrony-2.4-1.fc24.x86_64 ... [taw@rh ~]$ systemctl status chronyd ● chronyd.service - NTP client/server Loaded: loaded (/usr/lib/systemd/system/chronyd.service; enabled; vendor preset: enabled) Active: active (running) since Mon 2016-09-12 17:00:48 EDT; 23h ago Main PID: 19236 (chronyd) Tasks: 1 (limit: 512) CGroup: /system.slice/chronyd.service └─19236 /usr/sbin/chronyd Sep 13 14:54:56 rh chronyd[19236]: Source 198.55.111.50 offline Sep 13 14:54:56 rh chronyd[19236]: Source 204.2.134.163 offline Sep 13 14:54:56 rh chronyd[19236]: Source 129.250.35.251 offline Sep 13 14:54:56 rh chronyd[19236]: Source 129.6.15.30 offline Sep 13 14:54:56 rh chronyd[19236]: Can't synchronise: no selectable sources Sep 13 14:54:58 rh chronyd[19236]: Source 129.6.15.30 online Sep 13 14:54:58 rh chronyd[19236]: Source 198.55.111.50 online Sep 13 14:54:58 rh chronyd[19236]: Source 204.2.134.163 online Sep 13 14:54:58 rh chronyd[19236]: Source 129.250.35.251 online Sep 13 14:54:58 rh chronyd[19236]: Selected source 129.6.15.30
Another point of reference... I Have a F23 box in a virt instance. When it comes back from "pause" the time, date, and timezone simply do not auto-update (also using GNOME3 UI in this case, in case that matters).
Additional info... That F23 in a virt instance (GNOME3 enabled): Does not autoupdate the time and zone until I uncheck and then recheck control-panel settings. So, in summary: In F23 -- doesn't autoupdate without uncheck/check In F24 -- doesn't autoupdate... at all without forcing the change with timedatectl
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '24'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
For me this was solved by enabling "Location Services" in Settings->Privacy which allowed for the time zone to be changed straight away.