*** This bug is a duplicate of bug 1740666 *** https://bugs.launchpad.net/bugs/1740666
Public bug reported: When resuming, the clock remains at the time when the hibernate happened, even if timedatectl claims that it is being synced: $ timedatectl status Local time: Вс 2017-12-31 13:46:16 +05 Universal time: Вс 2017-12-31 08:46:16 UTC RTC time: Вс 2017-12-31 08:46:16 Time zone: Asia/Yekaterinburg (+05, +0500) Network time on: yes NTP synchronized: yes RTC in local TZ: no I've tried waiting a bit, but this persisted for some minutes, so I forced an update with systemctl restart systemd-timesyncd.service And afterwards the time was (apparently) correctly synced. Please, let me know what further informations are needed to debug the issue, and I would be happy to do some other test. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** This bug has been marked a duplicate of bug 1740666 systemd-timesyncd doesn't sync time after resume from hibernate -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1740665 Title: systemd-timesyncd doesn't sync time after resume from hibernate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1740665/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs