Ubuntu
ubiquity package

Time mismatch when hw clock is not UTC

Bug #97161 reported by Roman Polach
28
This bug affects 3 people
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Expired
Undecided
Unassigned

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)

See original description
Revision history for this message
Roman Polach (rpolach) wrote :

shouldn't this bug be targeted to Feisty?

Revision history for this message
Roman Polach (rpolach) wrote :

Problem still present in Feisty final...

Revision history for this message
Roman Polach (rpolach) wrote :

Problem still present in Gutsy final...

Revision history for this message
Roman Polach (rpolach) wrote :

This is probably due to installer does not respect that hw clock is in local time zone
(although clock applet respect it), so it add +2 hours two times...

Revision history for this message
Roman Polach (rpolach) wrote :

Still problem in Hardy final.
After an year, nobody still confirms this bug.

Revision history for this message
Colin Watson (cjwatson) wrote :

Sure, it's a problem, but there's no certain way to tell that the hardware clock is in local time rather than UTC short of getting the correct time by NTP (which the installer does now do if it can).

Changed in ubiquity:
status: New → Confirmed
Revision history for this message
Roman Polach (rpolach) wrote :

I understand. Maybe user can be asked if the clock is in local or UTC
when he set the city for the time zone? Or better there could be some
checkbox for local/UTC hidden in some "Advanced" section/dialog?

Michael Terry (mterry)
summary: - feisty installer: time zone mismatch
+ Time mismatch when hw clock is not UTC
description: updated
Revision history for this message
ભાવિન દોશી (bkd-online) wrote :

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.

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

Subscribing...

Other bug subscribers

Remote bug watches

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