Ubuntu corrupts Windows clock

Bug #56750 reported by Erdal Ronahi
12
Affects Status Importance Assigned to Milestone
Ubuntu
Invalid
Undecided
Unassigned

Bug Description

I am using Ubuntu since Breezy through Dapper on several computers from different vendors in dual-boot mode with Windows XP. All releases and all computers have one problem:

After working in Ubuntu, if I reboot into Windows XP, the clock is two hours back. If I correct it, it will be corrupted after the next Ubuntu session again.

My timezone is Europe/Berlin, so I think the BIOS-clock may be reset to GMT. That would explain the 2 hours difference.

Revision history for this message
istoyanov (istoyanov) wrote :

Change the line in /etc/default/rcS that says "UTC=yes" to "UTC=no" and time shouldn't change anymore between OSes.

Revision history for this message
istoyanov (istoyanov) wrote :

The corresponding question -- whether to set system clock to UTC -- is also being asked during setup, so if you do future installs that should run on a dual boot (Linux/Windows) system just answer "NO" to that question.

Revision history for this message
Erdal Ronahi (erdalronahi) wrote :

I changed the line to "UTC=no".

However, I do not remember to have answered "yes" to the corresponding question. I do not even remember the question, so I stil suspect a bug.

How is Ubuntu able to change the system clock anyway so it influences other OSes? I think it shouldn't do that.

Revision history for this message
Martey Dodoo (martey) wrote :

"How is Ubuntu able to change the system clock anyway so it influences other OSes? I think it shouldn't do that."

Ubuntu and other flavors of Linux use a UTC clock by default (I assume so that changing timezones does not change your hardware clock); Windows does not.

Revision history for this message
Erdal Ronahi (erdalronahi) wrote :

To clarify: I use the same timezone in both OSes. I do not change it at all. Just booting into Ubuntu is enough to change the time in Windows.

Revision history for this message
Vassilis Pandis (pandisv) wrote :

Thanks for reporting this. It's not really a bug probably (unless you've set UTC to 'no' and it still happens) so I'm closing this report.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.