[Bug 97161] Re: Time mismatch when hw clock is not UTC

[BKD]

My goodness. This still exists in precise and quantal.

This creates a lot of problems when the system has two ubuntu installs
side-by-side, and each time I boot into one ubuntu and do a sudo
ntpdate, the h/w clock is updated along with the system clock, and the
second ubuntu's time is messed up.

As a simple fix, when the installer asks for timezone, the clock can be
fixed once a timezone value is available.

-- 
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/97161

Title:
  Time mismatch when hw clock is not UTC

Status in “ubiquity” package in Ubuntu:
  Confirmed

Bug description:
  During Feisty Beta install there is step for setting time zone:
  The zone is predefined to "Europe/Prague (SELC, GMT+2)"
  but on this (the same) window is actual live time shown: 2 hours in future
  (like it would be in GMT+4)..

  In gnome clock applet there is correct time although

  (from comments: The hw clock is in local time, but Ubiquity assumes
  UTC, so it adds the +2 hour modifier a second time)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/97161/+subscriptions