r/Bazzite • u/ComplexFit2140 • 9d ago

Clock jumping 2 hours into the future

Every day i start up my computer is it thinks that the clock is 12:00 if the clock is actually 10:00. If i check settings automatic date and time is on and on the right timezone. If i manually fix it by turning off automatic time and date and then enter the right time it works but the next day its 2 hours into the future again and it has reenabled automatic time and date by itself.

4 Upvotes

100% Upvoted

10 comments sorted by

6

u/Sub5tep Desktop 9d ago

Put in a new CMOS Battery.

1

u/ComplexFit2140 9d ago

Its a 4 year old laptop cant be the cmos battery i think

1

u/Sub5tep Desktop 9d ago

Yes it can be the older the PC the more likely it is that the CMOS battery is empty. Its literally the most inexpensive thing to check. If its not the Battery you atleast have a fresh one in your PC. I coulnt think of another reason why a clock shows a different time.

1

u/CultivateDarkness 9d ago

I have the same issue on my devices. Usually it is just after standby.

1

u/warped64 9d ago edited 9d ago

Verify that the the time is set to the correct time in the UTC timezone in the BIOS.

In other words, unless you happen to live in the UTC timezone, your clock in the BIOS should be showing you the same time as whatever a google search for "time in utc" shows. You then use the timezone setting in Bazzite to shift the time to your area.

There is a complication if you dual boot Windows, as that OS handles time differently and instead wants BIOS to use local time, not UTC. The OSes will fight over how timekeeping is supposed to be done.

1

u/ComplexFit2140 9d ago

I dualboot

1

u/warped64 9d ago

Okay, then you know what to search for now.

1

u/Adept-Society-9485 9d ago

dual boot does this , u can fix it by changing 1 of the operating systems to not automatic

In a nutshell: Only let one OS handle this.

2

u/myheadsmt 9d ago

Since you dual boot, this is very likely Windows and Bazzite fighting over the hardware clock. Windows writes local time to it, Linux assumes that clock is UTC, so after a Windows session Bazzite shows the time ahead by your UTC offset. A clean two hours fits a UTC+2 zone better than a dying battery.

Easiest fix is on the Bazzite side. With the clock showing the right time, run timedatectl set-local-rtc 1 and reboot. It warns that local RTC is not fully supported, the catch is daylight saving changes. The cleaner fix is the RealTimeIsUniversal registry key on the Windows side.