Bug 487627

Summary: Time inaccurate after long sleep and doesnt re-sync
Product: [KDE Neon] neon Reporter: Thomas-Luke Duffin <thomaslukeduffin>
Component: generalAssignee: Neon Bugs <neon-bugs-null>
Status: REPORTED ---    
Severity: normal CC: carlosd.kde, jr, neon-bugs-null, p.r.worrall
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Thomas-Luke Duffin 2024-05-27 14:07:39 UTC
SUMMARY
Using my laptop (Lenovo 14APH8 Ideapad Pro 5), if I leave the system in sleep mode for a long period (hours, overnight) the clock becomes wildly out of sync and refuses to re-sync automatically. The date can be anywhere from a few hours out of date to over a hundred years into the future, which usually (definitely) causes SSL handshakes to fail until fixed.

Usually, I have to toggle "auto-sync time/date" checkbox in the system settings, as the system doesn't seem to do this at all after boot.

A useful feature could also be a "sync time now" button in the system settings beside the checkbox for automatically syncing, as that may be more intuitive for less technical users who aren't used to the common troubleshooting method of toggling a checkbox!

STEPS TO REPRODUCE
1. Set system to sleep mode for a few hours/overnight
2. Wake system back up

OBSERVED RESULT
Date is wildly out of sync, with no real pattern to it. Sometimes it can be the correct date but a few hours off, or it can a seemingly random date in the future (year 2187 seems to be favourable if that helps).

EXPECTED RESULT
The date is in sync with the real date.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 6.0, kernel 6.5.0-35-generic
KDE Plasma Version: 6.0.4
KDE Frameworks Version: 6.2.0
Qt Version: 6.7.0

ADDITIONAL INFORMATION
None yet.
Comment 1 Paul Worrall 2024-05-27 14:43:10 UTC
is systemd-timesyncd enabled and active? (systemctl status systemd-timesyncd)