Hi, I've got the same issue as Mikhail, with the added wrinkle that I have an analog clock widget on my desktop that shows the time two hours ahead, while the digital clock (in the tool bar) is two hours behind. I'm also using the Europe/Dublin timezone. And, as in Mikhail's case, the issue survives reboots and I don't have Steam installed. On 19/11/2018 06:22, David C. Rankin wrote:
What is shown with:
ls -al /etc/localtime
lrwxrwxrwx 1 root root 33 Nov 16 19:42 /etc/localtime -> /usr/share/zoneinfo/Europe/Dublin
Does it match your settings?
Compare the output of:
sudo hwclock -r
2018-11-19 07:53:20.796201+0000
with
date
Mon Nov 19 07:53:37 GMT 2018
Do the hwclock and sysclock agree with each other?
Also, systemd couldn't keep it's paws off the clock either and it now provides time sync services similar to ntp through timedatectl.
Check:
timedatectl status
Local time: Mon 2018-11-19 07:54:28 GMT Universal time: Mon 2018-11-19 07:54:28 UTC RTC time: Mon 2018-11-19 07:54:28 Time zone: Europe/Dublin (GMT, +0000) Network time on: yes NTP synchronized: yes RTC in local TZ: no
(which gives a nice summary of what systemd thinks all the clock settings are)
These are more just things to check than any silver-bullet guaranteed fix. If you have a 2hr difference in time that survives boot, then there is either a zoneinfo issue, or your sys and hardware clocks differ and are not being synced on boot, or you have two different parts of your system fighting over the clock, one of which has botched settings -- but seems to be winning the fight.
Report back and we will try and help further.
You may also want to check the journal or even dmesg to see if there is any error thrown related to a clock or time.
For what it's worth, the problem doesn't appear to be with the system clock settings, but (possibly) something in KDE/Plasma (at least in my case). Not sure where to look for time settings there. Brendan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org