You are not logged in.
Pages: 1
systemd throws my system in the year 2076 after resume.
It happens some times, nothing interesting in any log, other than the stupid time change.
RTC/hardware clock is perfectly fine and in sync. In fact my work around is to manually set the system time to the rtc time.
i also noticed that systemd-timedated craps out unhelpfully
# timedatectl show-timesync -a --monitor
Failed to parse bus message: No such file or directoryanyone have any idea which file that may be?
starting the timedated.service just results in it dying after a while. with zero info in the logs, because, why? right?
anyone been trhu this particular systemd-helld already?
Offline
Pages: 1