this post was submitted on 01 Dec 2025
52 points (100.0% liked)

Linux

10644 readers
464 users here now

A community for everything relating to the GNU/Linux operating system (except the memes!)

Also, check out:

Original icon base courtesy of lewing@isc.tamu.edu and The GIMP

founded 2 years ago
MODERATORS
Ategon@programming.dev
anzo@programming.dev
dwraf_of_ignorance@programming.dev
52
Fedora KDE keeps pushing my clock 8 hours ahead whenever I come back home from school (sopuli.xyz)
submitted 2 weeks ago* (last edited 2 weeks ago) by sbeak@sopuli.xyz to c/linux@programming.dev
19 comments fedilink hide all child comments
 

update: The issue has been fixed! Turns out all I had to do was set the clock to use UTC time using "timedatectl set-local-rtc 0"...

For some odd reason, whenever I come home (16:00), the clock is set 8 hours ahead (0:00, date jumps to the next day). I have to set my clock manually every time or restart my computer to get the correct time again. ~~There isn't any weird time zone shenanigans~~, the automatic time zone is still correct, and I don't live somewhere with daylight savings. What's wrong with my clock???

I am using Fedora 43 KDE (note: the issue was a thing in 42 KDE as well, but not with 42 Workstation. Either this is a KDE bug or there is some weird conflict with the remnants of gnome stuff. Or maybe I borked something I shouldn't have, idk)

edit: It is time zone shenanigans! My timezone is GMT+8. I have ran "timedatectl set-local-rtc 0" (the warning mentioned this when I ran "timedatectl status" as one person said to do) so let's see if that fixes it

you are viewing a single comment's thread
view the rest of the comments
[–] edralzar@programming.dev 4 points 2 weeks ago

I'm not an expert but I had a similar problem, except it was visible after each time I was rebooting to windows. Linux by default interprets the hardware clock as UTC, whereas windows interprets as local time. The warning you see is when your linux distro is instead configured to behave like windows does (local time).

In your case, it doesn't seem as obvious what is the culprit (no windows to write the local time to the RTC) but perhaps the distro's update changed that parameter somehow ?

Setting the flag to 0 shouldn't cause more trouble than what you've already seen I think... So that's worth trying out for a few days ;)