Time set incorrectly

hi,
I think I configured everything correctly:

  • timedatectl in sys-net gives the correct time and says system clock synchronized, ntp service active
  • ive set clockvm in global settings to sys-net

but nevertheless system time is off by 2 hours and 2 minutes :frowning:
it seems to be the rtc time + 2h and rtc time in sys-net is 2 minutes after local time in sys-net

in dom0, universal time = rtc time and local time is rtc time +2

this is on verified hardware (a nitropad)

I’m seeing this as well.

Actually, I started seeing weird problems with time already couple of weeks ago, but since yesterday this +2 hours thingie.

2 Likes

update: it fixed itself a few h (?) after i changed clockvm to sys-net (after which I had rebooted to no avail)

The clock has always been finicky for me. Sometimes changing dom 0 doesn’t work or doesn’t stick, and if so instead right clicking on the clock and changing timezones and the clock that way works or vice versa. I haven’t figured it out completely.

1 Like

No idea why. Try the following:

  • right-click on the clock » properties » timezone (add your timezone)

?

The clock is wrong for me too. (Fresh install of Qubes 4.1)

timedatectl gives the correct output in sys-net but is off by one hour in dom0.
Note that I am in UTC + 1 and so shifts by one hour usually mean that timezones are incorrectly applied.

[user@sys-net ~]$ timedatectl 
               Local time: Fri 2022-02-11 17:46:12 CET
           Universal time: Fri 2022-02-11 16:46:12 UTC
                 RTC time: Fri 2022-02-11 16:46:13
                Time zone: Europe/Berlin (CET, +0100)
System clock synchronized: yes
              NTP service: active
          RTC in local TZ: no

and then when I try in dom0

dom0 ~]$ timedatectl 
               Local time: Fri 2022-02-11 16:50:21 CET
           Universal time: Fri 2022-02-11 15:50:21 UTC
                 RTC time: Fri 2022-02-11 15:50:21    
                Time zone: Europe/Berlin (CET, +0100) 
System clock synchronized: no                         
              NTP service: inactive                   
          RTC in local TZ: no 

(ignore the minutes, it is off precisely by one hour.)

Update: It fixed itself. The time in dom0 has jumped forward. No idea what triggered it.

1 Like