On 11/18/2018 09:45 PM, Mikhail Ramendik wrote:
On Sun, 18 Nov 2018 at 15:28, gumb <gumb@linuxmail.org> wrote:
Probably unrelated but I ran into an issue like this on another 42.3 KDE machine a couple of months ago. It seemed to be something to do with having installed Steam. I'd tinkered with the timezone setting in some part of the Steam interface, and it had somehow messed with my system clock after I exited Steam back to the desktop. Nothing I did to the system clock thereafter would correct it, I think it needed a reboot, or at least logging in anew.
No Steam on this system - but indeed I should have mentioned that the issue survives reboots.
What is shown with: ls -al /etc/localtime Does it match your settings? Compare the output of: sudo hwclock -r with date 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 (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. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org