You are not logged in.
Hello, everyone. So I think I just encountered the same exact issue discussed in this thread.
My system and hardware clocks are both correct, here is the output:
$ timedatectl
Local time: Thu 2022-07-14 23:12:37 UTC
Universal time: Thu 2022-07-14 23:12:37 UTC
RTC time: Thu 2022-07-14 23:12:37
Time zone: UTC (UTC, +0000)
System clock synchronized: no
NTP service: inactive
RTC in local TZ: no
# hwclock --show
2022-07-14 23:13:30.242201+00:00Although, any website (e.g. gmail, facebook, etc.) on Chrome shows 2h behind. As well as the emails on Thunderbird.
Any idea how to solve this? Thank you in advance.
Last edited by ordinary.schreiber (2022-07-17 08:43:17)
Offline
Um, that message posted at 14:14 PDT (UTC-7), which would have been 21:14 UTC. Your post indicates system clock says UTC was 23:13 which would have been off by two hours, so I disagree with your assertion that the system clock and hardware clock are correct.
Are you, by chance, 2 timezones east of 0 degrees?
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way
Offline
https://bbs.archlinux.org/viewtopic.php?id=273548
Tiscali only operates in Italy, CEST (one TZ + DST)
@ordinary.schreiber, your system clock might show the same numbers as your wall clock, but it's configured for Newton's home in Winter, not Italy in summer.
When you fix your https://wiki.archlinux.org/title/System_time#Time_zone you'll notice that the system clock is 2h ahead of your wall clock, so you want to fix that, too.
https://wiki.archlinux.org/title/Catego … e_Protocol
If there's a parallel windows installation driving the system clock "ahead", there's a section about that in the system time article as well.
Offline
When you fix your https://wiki.archlinux.org/title/System_time#Time_zone you'll notice that the system clock is 2h ahead of your wall clock, so you want to fix that, too
Thank you, it is now fixed.
Offline