[opensuse] 42.3: KDE on-screen clock 2 hours off
Hello, I have an OpenSUSE 42.3 system. now fully updated with zypper up. Network time sync is enabled. The timezone is Dublin. which should be GMT. If I open a Konsole window and run "date", I get the correct time (now 13:50 GMT) But the clock in the system tray is off by 2 hours, showing 11:50! I have right-clicked the clock and selected "Digital Clock Settings" and the timezone is correct, Dublin. I tried adding a Moscow rime zone, now on mouseover I get "GMT 11:50 MSK 14:50", even though actually it's GMT 13:50 MSK 16:50 - and the GMT in the command line is correct! How can I fix this? Thanks! -- Yours, Mikhail Ramendik Unless explicitly stated, all opinions in my mail are my own and do not reflect the views of any organization -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 18/11/2018 14:53, Mikhail Ramendik wrote:
Hello,
I have an OpenSUSE 42.3 system. now fully updated with zypper up. Network time sync is enabled. The timezone is Dublin. which should be GMT.
If I open a Konsole window and run "date", I get the correct time (now 13:50 GMT)
But the clock in the system tray is off by 2 hours, showing 11:50!
I have right-clicked the clock and selected "Digital Clock Settings" and the timezone is correct, Dublin. I tried adding a Moscow rime zone, now on mouseover I get "GMT 11:50 MSK 14:50", even though actually it's GMT 13:50 MSK 16:50 - and the GMT in the command line is correct!
How can I fix this? Thanks!
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. gumb -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
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. -- Yours, Mikhail Ramendik Unless explicitly stated, all opinions in my mail are my own and do not reflect the views of any organization -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
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
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
On Mon, 19 Nov 2018 07:57:03 +0000 Brendan McKenna <brendan@hallwaysdc.com> wrote:
On 19/11/2018 06:22, David C. Rankin wrote:
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
FWIW, on my system, which is working fine: Local time: Mon 2018-11-19 10:03:06 GMT Universal time: Mon 2018-11-19 10:03:06 UTC RTC time: Mon 2018-11-19 10:03:06 Time zone: Europe/London (GMT, +0000) Network time on: no NTP synchronized: yes RTC in local TZ: no I think, but do not know, that systemd's 'network time' and 'NTP synchronization' are mutually exclusive. They should not both be on. But as I say, that's just a dim memory, so please check the docs before doing anything. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Dave Howorth <dave@howorth.org.uk> [11-19-18 05:09]:
On Mon, 19 Nov 2018 07:57:03 +0000 Brendan McKenna <brendan@hallwaysdc.com> wrote:
On 19/11/2018 06:22, David C. Rankin wrote:
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
FWIW, on my system, which is working fine:
Local time: Mon 2018-11-19 10:03:06 GMT Universal time: Mon 2018-11-19 10:03:06 UTC RTC time: Mon 2018-11-19 10:03:06 Time zone: Europe/London (GMT, +0000) Network time on: no NTP synchronized: yes RTC in local TZ: no
I think, but do not know, that systemd's 'network time' and 'NTP synchronization' are mutually exclusive. They should not both be on. But as I say, that's just a dim memory, so please check the docs before doing anything.
do: systemctl status systemd-timesyncd -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hi again,
do: systemctl status systemd-timesyncd
Did that, and it reports the service as being inactive. The timedatectl command still shows Network time on: yes and NTP synchronized: yes, although I'm not certain whether the one affects the other. I also tried starting systemd-timesyncd, but that had no effect on the displayed time. I've also tried stopping the ntpd and starting systemd-timesyncd and that, too, has no effect. The curious thing is that the time displayed on the login screen is correct, it's just the digital clock and analog clock widgets that have the incorrect time. And that the digital clock is 2 hours slow while the analog one is two hours fast. Thanks for the suggestions. If you have any more, I'm more than willing to give them a shot... Brendan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/19/2018 01:48 PM, Brendan McKenna wrote:
Did that, and it reports the service as being inactive. The timedatectl command still shows Network time on: yes and NTP synchronized: yes, although I'm not certain whether the one affects the other.
They do and should not both be active. I don't think one conflicts with the other, I think the problem is any update by systemd-timesyncd will cause issues with the ntp 'driftfile' if time updates occur when both are enabled. (and ntp my cause the same issue with however timedatectl tracks the clock slew) Other than that -- I don't think they conflict, more it is just incompatible to have both running. Both will sync to the correct date/time, so they are not in conflict there -- but it one applies an update to the clock, it is likely to screw up how the other keeps track of the clock drift. -- 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
On 20/11/2018 00.04, David C. Rankin wrote:
On 11/19/2018 01:48 PM, Brendan McKenna wrote:
Did that, and it reports the service as being inactive. The timedatectl command still shows Network time on: yes and NTP synchronized: yes, although I'm not certain whether the one affects the other.
They do and should not both be active. I don't think one conflicts with the other, I think the problem is any update by systemd-timesyncd will cause issues with the ntp 'driftfile' if time updates occur when both are enabled. (and ntp my cause the same issue with however timedatectl tracks the clock slew)
Yes, they do conflict. They all try to adjust the same clock and interfere one with another, because they then do wrong calculations. They may not say anything about the problem, they may not know anything about the other one running (they should!), but the condition may create strange symptoms and errors. Use only one of: systemd time, ntpd, chrony -- Cheers / Saludos, Carlos E. R. (from openSUSE 15.0 (Legolas))
One more data point -- I changed the timezone settings from Europe/Dublin to Europe/London (we're in the same timezone, after all), and it reduces the error to 1 hour from two. Still have the analog clock fast by 1 hour and the digital one slow by 1. Something in Plasma apparently has it in for folks in GMT... Brendan On 19/11/2018 23:47, Carlos E. R. wrote:
On 20/11/2018 00.04, David C. Rankin wrote:
On 11/19/2018 01:48 PM, Brendan McKenna wrote:
Did that, and it reports the service as being inactive. The timedatectl command still shows Network time on: yes and NTP synchronized: yes, although I'm not certain whether the one affects the other.
They do and should not both be active. I don't think one conflicts with the other, I think the problem is any update by systemd-timesyncd will cause issues with the ntp 'driftfile' if time updates occur when both are enabled. (and ntp my cause the same issue with however timedatectl tracks the clock slew)
Yes, they do conflict. They all try to adjust the same clock and interfere one with another, because they then do wrong calculations. They may not say anything about the problem, they may not know anything about the other one running (they should!), but the condition may create strange symptoms and errors.
Use only one of: systemd time, ntpd, chrony
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/19/2018 01:57 AM, Brendan McKenna wrote:
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
That is definitely what it is looking like -- glad it still works right in KDE3 :) -- 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
On Mon, 19 Nov 2018 at 06:22, David C. Rankin <drankinatty@suddenlinkmail.com> wrote:
What is shown with:
misha@ramendik-desktop:~> ls -al /etc/localtime lrwxrwxrwx 1 root root 33 Nov 18 13:35 /etc/localtime -> /usr/share/zoneinfo/Europe/Dublin misha@ramendik-desktop:~> sudo hwclock -r [sudo] password for root: 2018-11-21 03:22:59.077312+0000 misha@ramendik-desktop:~> date Wed 21 Nov 03:23:23 GMT 2018 misha@ramendik-desktop:~> timedatectl status Local time: Wed 2018-11-21 03:23:35 GMT Universal time: Wed 2018-11-21 03:23:35 UTC RTC time: Wed 2018-11-21 03:23:35 Time zone: Europe/Dublin (GMT, +0000) Network time on: yes NTP synchronized: yes RTC in local TZ: no misha@ramendik-desktop:~> So all the times are in sync in command line 0- but digital clock in Plasma is two hours behind. I did try switching the "digital clock" timezone in Plasma to London, nothing changed. I also have Fedora 28 on another machine, same time zone, also Plasma. The widget works correcrly. This is the first time KDE is workiedora better than in OpenSUSE - for KDE things it's usually either the same, or OpenSUSE better. (Which is not a surprise as Fedora is more focused on Gnome). -- Yours, Mikhail Ramendik Unless explicitly stated, all opinions in my mail are my own and do not reflect the views of any organization -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 21/11/2018 04.28, Mikhail Ramendik wrote:
On Mon, 19 Nov 2018 at 06:22, David C. Rankin <> wrote:
What is shown with:
misha@ramendik-desktop:~> ls -al /etc/localtime lrwxrwxrwx 1 root root 33 Nov 18 13:35 /etc/localtime -> /usr/share/zoneinfo/Europe/Dublin misha@ramendik-desktop:~> sudo hwclock -r [sudo] password for root: 2018-11-21 03:22:59.077312+0000 misha@ramendik-desktop:~> date Wed 21 Nov 03:23:23 GMT 2018 misha@ramendik-desktop:~> timedatectl status Local time: Wed 2018-11-21 03:23:35 GMT Universal time: Wed 2018-11-21 03:23:35 UTC RTC time: Wed 2018-11-21 03:23:35 Time zone: Europe/Dublin (GMT, +0000) Network time on: yes <===== NTP synchronized: yes RTC in local TZ: no misha@ramendik-desktop:~>
"Network time on" refers to systemd-timesyncd. Thus you are running both systemd-timesyncd and ntpd. You must disable one of the two. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
Hello, I have updated the system to 15.0. However, I am still having the problem. I found the bug being actively handled in bugzilla: https://bugzilla.opensuse.org/show_bug.cgi?id=1114570 They are offering a workaround in installing an RPM from a repo but I do hope this gets into system updates soon. I did find a rather dirty workaround. Right click desktop clock, "Digital clock settings", "Time zones", select Kiev. As my actual TZ is GMT and Kiev is GMT+2 and the clock is 2 hours behind, the clock becomes correct, though has an incorrect "EET" next to it. Re the ntp thing: On Wed, 21 Nov 2018 at 12:20, Carlos E. R. <robin.listas@telefonica.net> wrote:
"Network time on" refers to systemd-timesyncd. Thus you are running both systemd-timesyncd and ntpd. You must disable one of the two.
I have now disabled ntpd but the problem remains and also the output remains. misha@ramendik-desktop:~> timedatectl status Local time: Sun 2018-12-02 01:40:31 GMT Universal time: Sun 2018-12-02 01:40:31 UTC RTC time: Sun 2018-12-02 01:40:31 Time zone: Europe/Dublin (GMT, +0000) Network time on: yes NTP synchronized: yes RTC in local TZ: no misha@ramendik-desktop:~> systemctl ntpd status Unknown operation ntpd. misha@ramendik-desktop:~> systemctl status ntpd ● ntpd.service - NTP Server Daemon Loaded: loaded (/usr/lib/systemd/system/ntpd.service; disabled; vendor preset: disabled) Drop-In: /run/systemd/generator/ntpd.service.d └─50-insserv.conf-$time.conf Active: inactive (dead) Docs: man:ntpd(1) misha@ramendik-desktop:~> -- Yours, Mikhail Ramendik Unless explicitly stated, all opinions in my mail are my own and do not reflect the views of any organization -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op zondag 2 december 2018 02:50:52 CET schreef Mikhail Ramendik:
I have now disabled ntpd but the problem remains and also the output remains.
misha@ramendik-desktop:~> timedatectl status Local time: Sun 2018-12-02 01:40:31 GMT Universal time: Sun 2018-12-02 01:40:31 UTC RTC time: Sun 2018-12-02 01:40:31 Time zone: Europe/Dublin (GMT, +0000) Network time on: yes NTP synchronized: yes RTC in local TZ: no misha@ramendik-desktop:~> systemctl ntpd status Unknown operation ntpd. misha@ramendik-desktop:~> systemctl status ntpd
This looks like /etc/localtime does not point to or is a copy of, in your case, /usr/share/zoneinfo/Europe/Kiev. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Mikhail Ramendik composed on 2018-11-18 13:53 (UTC):
I have an OpenSUSE 42.3 system. now fully updated with zypper up. Network time sync is enabled. The timezone is Dublin. which should be GMT.
If I open a Konsole window and run "date", I get the correct time (now 13:50 GMT)
But the clock in the system tray is off by 2 hours, showing 11:50!
I have right-clicked the clock and selected "Digital Clock Settings" and the timezone is correct, Dublin. I tried adding a Moscow rime zone, now on mouseover I get "GMT 11:50 MSK 14:50", even though actually it's GMT 13:50 MSK 16:50 - and the GMT in the command line is correct!
How can I fix this? Thanks!
I don't know, but would like to. I don't use Plasma on Leap, and I haven't seen this happen on Plasma on TW, but I have experienced this on Fedora 28: https://lists.fedoraproject.org/archives/list/kde@lists.fedoraproject.org/th... There is https://bugzilla.opensuse.org/show_bug.cgi?id=1114570 that looks like might be the same thing. I searched bugs.kde.org, found nothing open that looks like a match, but did find a possible match that has been closed: https://bugs.kde.org/show_bug.cgi?id=388322 -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (9)
-
Brendan McKenna -
Carlos E. R. -
Dave Howorth -
David C. Rankin -
Felix Miata -
Freek de Kruijf -
gumb -
Mikhail Ramendik -
Patrick Shanahan