Dual boot Windows time inconsistency #27
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Source: Stack Exchange
is a workaround.
Output:
Output:
Tracked at Benjamin_Loison/windows/issues/14.
+20
I executed above command while being connected to Shotbow and got after about an hour:
Happened again maybe when I sent a chat message.
Without
sudo
:Cannot the server return an arbitrary value, hence run as
root
an arbitrary command? Maybe not thanks to"$(...)"
.Related to Benjamin-Loison/gitea/issues/117.
Maybe related to Benjamin-Loison/gitea/issues/118.
Related to Benjamin_Loison/Debian/issues/81.
Maybe face a similar issue on my Debian 12 GNOME work laptop as it has a Windows 11 and Ubuntu 24.04.1 as well.
while on my Fairphone 4 Termux:
as far as I experienced it does not hold for long.
I enabled Automatic Time Zone and manually correct Date & Time again, let us see if the see issue is raised again at some point.
I also suspects 2 minutes time shift making TOTP not work.
wget
command solves the issue.I have one hour shift again.
Just rebooting my Debian 12 GNOME work laptop seems to lead to the issue.
While already have:
I had to check my phone to ensure the time was correctly set (it was).
Does not seem related to secure boot as seems to have the issue on both states, related to Benjamin-Loison/cinnamon/issues/178 and Benjamin-Loison/obs-studio/issues/24.
Let us verify if Ubuntu and Windows also face the issue, let us update them as I do not regularly use them.
Have to reboot them to be accurate I would say.
Unlocking session may help. Waiting Internet access may be appropriate.
No issue on Ubuntu.
Face the same issue on Windows but may have BitLocker recovery bias, as have disabled secure boot I guess.
Maybe will have to dig BIOS.
Should try to firmware update from Debian or Ubuntu.
To be on time for work it is a very important issue.
Output:
on Debian 12 GNOME.
sudo
does not help.https://duckduckgo.com/?t=ftsa&q=CET+time&ia=web
https://time.is/UTC+1
both above state 14:21.
may be a workaround.
Well can set it along automatic time zone, let us restart to check.
I still have correct time (14:25) after reboot.
It ended up at some point (possibly with reboots) no more being at the right time again.
DuckDuckGo search *Debian incorrect time while correct time zone *.
Output:
same output (including prompts) if execute again.
Output:
Source: the Unix Stack Exchange answer 273113
Output:
corrects the time.
Let us verify that it holds a reboot.
Maybe no more having battery is involved.
It holds a reboot.
I still have the issue after some time...
It's now a 2 hours time shift...
To be able to investigate when the time shift occurs, let us add to
crontab
:should then make an algorithm to detect significant shift.
How to be notified in real-time when the issue happens? Could leverage an always running server notifying if notice an offset of more than half an hour. This should not lead to false alarms as the time on resuming from suspension should be correct as tested but it happens sometimes to be incorrect.
Could add
ntpdate
tovisudo
, done:Can somehow get time of motherboard, see Wikipedia: Real-time clock? Which should be stable without OS change.
With Proton VPN at Amsterdam:
I received a notification that time has changed.