I decided to do a reinstall as well. Sometimes it’s just better. a Clean slate.
If you do it, though, I suggest you take note of what you can do differently, better. And actually do it. Otherwise, it’ll only happen again. And again. As long as you learnt something.
Hey guy thanks for all the help!
Something along the way fixed it, i don’t know when but last night I looked the time its was wrong then after a while after doing some stuff - not related to the problem - I glanced at it again and it was right!
All I did was mess around with anbox before I noticed it was corrected and I wonder if it had something to do with anbox?
Here is what timedatectl status outputs now:
Local time: Sat 2021-12-11 08:31:32 IST
Universal time: Sat 2021-12-11 03:01:32 UTC
RTC time: Sat 2021-12-11 14:01:36
Time zone: Asia/Kolkata (IST, +0530)
System clock synchronized: yes
NTP service: active
RTC in local TZ: yes
Warning: The system is configured to read the RTC time in the local time zone.
This mode cannot be fully supported. It will create various problems
with time zone changes and daylight saving time adjustments. The RTC
time is never updated, it relies on external facilities to maintain it.
If at all possible, use RTC in UTC by calling
'timedatectl set-local-rtc 0'.
and here is what timedatectl show-timesync --all outputs now:
timedatectl status
Local time: Sa 2021-12-11 07:49:48 CET
Universal time: Sa 2021-12-11 06:49:48 UTC
RTC time: Sa 2021-12-11 06:49:48
Time zone: Europe/Berlin (CET, +0100)
System clock synchronized: yes
NTP service: active
RTC in local TZ: no
(This is like it should look like ! (See, no WARNING))
The ARCH-Wiki suggests to use Universal the same as RTC !
(or otherwise Local same as RTC)
The warning is not a real problem. Since the OP uses a Dualboot, it is either that or the OP needs to edit the Windows registry as described in the Arch Wiki.
However both ways aren’t supported or recommended and can result in issues. It is up to the OP to decide which method it should be.
However, if RTC is set to local, it needs to be this time. Which is apparently not. This needs to be fixed by the OP. A command to set the RTC in local time, requires that the local time from timedatectl status is correct.
Ok thanks I ran the command with sudo and here is the output from timedatectl status
Local time: Sat 2021-12-11 21:43:04 IST
Universal time: Sat 2021-12-11 16:13:04 UTC
RTC time: Sat 2021-12-11 21:43:04
Time zone: Asia/Kolkata (IST, +0530)
System clock synchronized: no
NTP service: active
RTC in local TZ: yes
Warning: The system is configured to read the RTC time in the local time zone.
This mode cannot be fully supported. It will create various problems
with time zone changes and daylight saving time adjustments. The RTC
time is never updated, it relies on external facilities to maintain it.
If at all possible, use RTC in UTC by calling
'timedatectl set-local-rtc 0'.
oh and by the way it is anbox! starting anbox fixes the problem! I don’t know how or why but it is!
After a restart my time was wrong then when I opened anbox it corrected itself.
I sent this reply not noticing my time was wrong again. Then when I noticed that the time was wrong I started anbox and the time changed right before my eyes. and checking timedatectl status
Local time: Sat 2021-12-11 17:36:02 IST
Universal time: Sat 2021-12-11 12:06:02 UTC
RTC time: Sat 2021-12-11 17:36:02
Time zone: Asia/Kolkata (IST, +0530)
System clock synchronized: yes
NTP service: active
RTC in local TZ: yes
Warning: The system is configured to read the RTC time in the local time zone.
This mode cannot be fully supported. It will create various problems
with time zone changes and daylight saving time adjustments. The RTC
time is never updated, it relies on external facilities to maintain it.
If at all possible, use RTC in UTC by calling
'timedatectl set-local-rtc 0'.