time selector sets hardware clock to UTC even if it defaults to UTC=no later

Bug #66531 reported by Martin Pitt
18
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

A friend of mine just installed Dapper on a box with already installed Windows. After that, the clock was off by two hours in *both* operating systems.

I tracked this down a bit over the phone:

 - /etc/adjtime said 'local' (since ubiquity correctly defaults to UTC=no if Windows is found)
 -the hardware clock was set from localtime to UTC during installation. I can only assume that this happened when selecting the time zone in step 2 of ubiquity.

After fixing the hardware clock to be the true local time again, both Ubuntu and Windows were fine.

Revision history for this message
Matthew Woerly (nattgew) wrote :

Thanks for your report. Is this still present in Hardy?

Revision history for this message
seisen1 (seisen-deactivatedaccount-deactivatedaccount) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Ubuntu release? Thanks in advance.

Changed in ubiquity:
status: New → Incomplete
Revision history for this message
Too Late (late2008) wrote :

This bug still exists in Hardy. At least with the ubuntu-8.04.1-desktop-i386 installation media which I do have. I've installed it twice and both times there was this issue. NTP service (with default priviledged port 123) is not working for me due to issues apart from my machine.

People with working NTP service won't probably never found this bug, if the NTP checks the correct time before the actual copying of the files starts (I'm not sure if that happens). But for me, the first chance to set the BIOS hardware clock is during the first (and only) reboot after the installation. Therefore, every file that was created during the installation, has a timestamp three hours ahead (my time zone is EEST which is UTC +3).

Revision history for this message
Shriramana Sharma (jamadagni) wrote :

Confirming this bug on Kubuntu Hardy 8.04.1 and IIRC Kubuntu Intrepid Alpha 5 too. The installer (I always do a hdinstall) never asks me whether my hardware clock is set to UTC or local time. It assumes it is UTC and *changes* it to local time. Thus, when the actual local time is 1500, and I set my location to India with offset UTC+0530, after the installation and boot into newly installed system, the time is shown as 1500+0530=2030 hours, both in Kubuntu and Windows.

Changed in ubiquity:
status: Incomplete → Confirmed
Revision history for this message
steltenpower (ubuntu-steltenpower) wrote :

I'm not sure if it's the same bug, but almost certainly related to the least.
I had wubi install ubuntu, ran it and now my time in Windows is 6 hours behind (haven't checked time in Ubuntu).
I'm in the Amsterdam timezone

Revision history for this message
Marcus Tomlinson (marcustomlinson) wrote :

This release of Ubuntu is no longer receiving maintenance updates. If this is still an issue on a maintained version of Ubuntu please let us know.

Changed in ubiquity (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]

Changed in ubiquity (Ubuntu):
status: Incomplete → Expired
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.