| Summary: | KDE neon (Live from USB) changes clock under Windows 10 | ||
|---|---|---|---|
| Product: | [KDE Neon] neon | Reporter: | BOF <bugs_kde_org.5.kuru> |
| Component: | Live/Install images | Assignee: | Neon Bugs <neon-bugs-null> |
| Status: | REPORTED --- | ||
| Severity: | normal | CC: | jr, neon-bugs-null, sitter |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Microsoft Windows | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | KDE neon 5.22 versions | ||
|
Description
BOF
2021-09-11 16:24:30 UTC
I just booted into Windows 10 after testing with a lice system using Zorin OS 16. I got the same result and my clock changed -2 hours. So maybe it's not only KDE neon. I had some time to test the live system again. The time was correct until I connected the PC to the internet. At that point I got the -2 hours again. Then I changed the time zone to the one I'm in and the clock showed the correct time. After reboot I logged in into Windows 10 and I got the same changed clock again. Does the live system really set the BIOS/UEFI clock to GMT 0 even you have a different timezone? Again: IMHO a live system should never touch a setting unless specifically told so. Created attachment 141744 [details]
KDE neon 5.22 versions
The version list from the system menu as promised
Today I noticed a problem that I noticed before: When you run the live system and it changes the clock, the Windows 10 clock will auto update, but this takes some time and will also only work if you connected to the internet. The problem I had: I thought the clock was accurate (on Windows 10) and trusted it (because I didn't kept this bug in mind). I was working on the PC and wondered why today I was doing the same things, yet had so much more time than usual. This was followed by a huge _Oh sh!t_ moment when I took a look at my phone's clock. I re-tested this today and the problem still exists. |