[Bug 66531] Re: time selector sets hardware clock to UTC even if it defaults to UTC=no later

[Launchpad Bug Tracker]

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

** Changed in: ubiquity (Ubuntu)
       Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubiquity in Ubuntu.
https://bugs.launchpad.net/bugs/66531

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

Status in ubiquity package in Ubuntu:
  Expired

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 manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/66531/+subscriptions