time selector sets hardware clock to UTC even if it defaults to UTC=no later
Bug #66531 reported by
Martin Pitt
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.
To post a comment you must log in.
Thanks for your report. Is this still present in Hardy?