[SOLVED] xfce clock shows wrong time

pedpup2 · 12-22-2023, 06:36 AM

Running SolydX ( debian based ) with xfce desktop. HP 8560P laptop.
Suddenly the clock in the system tray is off by 12 hours.
I checked the ntp service- it was inactive. I activated it.

No change

from CLI ran "date" - and that is right.

Here is the result of systemctl status ntp:

Code:

ntp.service - Network Time Service
   Loaded: loaded (/lib/systemd/system/ntp.service; enabled; vendor preset: enabled)
   Active: active (running) since Thu 2023-12-21 14:42:56 CST; 6h ago
     Docs: man:ntpd(8)
  Process: 782 ExecStart=/usr/lib/ntp/ntp-systemd-wrapper (code=exited, status=0/SUCCESS)
 Main PID: 817 (ntpd)
    Tasks: 2 (limit: 4915)
   Memory: 3.1M
   CGroup: /system.slice/ntp.service
           └─817 /usr/sbin/ntpd -p /var/run/ntpd.pid -g -u 119:133

Dec 21 14:44:03 phils8560 ntpd[817]: Soliciting pool server 45.84.199.136
Dec 21 14:44:03 phils8560 ntpd[817]: Soliciting pool server 72.46.53.234
Dec 21 14:44:04 phils8560 ntpd[817]: Soliciting pool server 217.180.209.214
Dec 21 14:44:04 phils8560 ntpd[817]: Soliciting pool server 45.79.1.70
Dec 21 14:44:05 phils8560 ntpd[817]: Soliciting pool server 44.190.5.123
Dec 21 14:44:05 phils8560 ntpd[817]: Soliciting pool server 104.131.139.195
Dec 21 14:44:06 phils8560 ntpd[817]: Soliciting pool server 2620:135:5003:ffff::123
Dec 21 14:44:07 phils8560 ntpd[817]: Soliciting pool server 71.162.136.44
Dec 21 20:45:55 phils8560 ntpd[817]: receive: Unexpected origin timestamp 0xe92f2219.40a5dda9 does not match aorg 0000000000.00000000 from server@45.79.1.70 xmt 0xe92f76e3.a4ec3084
Dec 21 20:45:55 phils8560 ntpd[817]: receive: Unexpected origin timestamp 0xe92f2219.409f0b3d does not match aorg 0000000000.00000000 from server@217.180.209.214 xmt 0xe92f76e3.a864

Can anyone suggest a fix for this?

I'll provide any info you need..

Thanks,

phil

lvm_ · 12-22-2023, 07:50 AM

I'd start with checking the time zone settings of xfce clock plugin https://docs.xfce.org/xfce/xfce4-panel/clock

shortarcflyer · 12-22-2023, 08:19 AM

You may also try this in a terminal to reset your time.

Code:

sudo dpkg-reconfigure tzdata

michaelk · 12-22-2023, 08:35 AM

If the output of the date command shows the correct time and time zone information then as suggested I would look at xfce clock plugin. The timezone setting could be different from the system setting. I would not be concerned with the ntp warning. I would expect ntp to disregard those two servers.

To see if ntp is "working" look at the output of the command:
ntpq -p

pedpup2 · 12-22-2023, 11:39 AM

Thank you, lvm, shortarcflyer and MichaelK,

I checked the Time&date settings in the clock plugin. Right except of course
it reads 11:31:12 PM, but it's actually 11:31:12 AM...

MichaelK here is the output of ntpq -p but I do not know how to read this...

Code:

ntpq -p
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
 0.debian.pool.n .POOL.          16 p    -   64    0    0.000    0.000   0.000
 1.debian.pool.n .POOL.          16 p    -   64    0    0.000    0.000   0.000
 2.debian.pool.n .POOL.          16 p    -   64    0    0.000    0.000   0.000
 3.debian.pool.n .POOL.          16 p    -   64    0    0.000    0.000   0.000
*65-100-46-166.d .SOCK.           1 u  124 1024  377   64.525    1.899   1.796
+t1.time.bf1.yah 98.139.133.62    2 u  607 1024  357   33.195    1.287   6.482
+mailman.shaunc. 132.163.97.6     2 u  302 1024  377   28.846    3.103   2.749
+mailhost.netads 206.108.0.131    2 u   73 1024  377   37.460    0.881   1.195
-45.84.199.136 ( 36.224.68.195    2 u  741 1024  175  120.210    3.996   5.646
-108.61.23.93 (1 108.61.56.35     3 u  652 1024  377   34.020   -0.966   1.561

In "Timezone", in the clock plugin settings, it read 6 ( I am in the same zone as Chicago, IL, USA ).
But I noticed they seem to expect a string , like "America/Chicago" in that box.
So I changed it to that...

And...suddenly it's working! Now the time is correct. I'm still not certain what I did to correct it, though.

Linux - a continual learning experience.

Anyway, Thank you all again.

michaelk · 12-22-2023, 12:21 PM

I assume originally the desktop was configured to default to system time and no idea how it was changed. It looks like the desktop "understands" a fixed offset as well as time zones. Since America/Chicago is -06:00 offset (CST) and the desktop was configured as +6:00 offset so the time displayed was 12 hours fast.

Code:

     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
*65-100-46-166.d .SOCK.           1 u  124 1024  377   64.525    1.899   1.796