systemd-timesyncd doesn't sync time after resume from hibernate
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
systemd (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
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-
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.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: systemd 234-2ubuntu12.1
ProcVersionSign
Uname: Linux 4.13.0-19-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.7-0ubuntu3.6
Architecture: amd64
CurrentDesktop: MATE
Date: Sun Dec 31 13:41:51 2017
InstallationDate: Installed on 2017-06-05 (208 days ago)
InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: Gigabyte Technology Co., Ltd. P35-DS3
ProcKernelCmdLine: BOOT_IMAGE=
SourcePackage: systemd
UpgradeStatus: Upgraded to artful on 2017-12-16 (14 days ago)
dmi.bios.date: 06/18/2009
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F14
dmi.board.name: P35-DS3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSof
dmi.product.name: P35-DS3
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
tags: | removed: artful |
Changed in systemd (Ubuntu): | |
status: | Invalid → Confirmed |
Changed in systemd (Ubuntu): | |
status: | Confirmed → New |
Does this system have hardware clock?