| 2007-03-27 21:23:30 |
Roman Polach |
bug |
|
|
added bug |
| 2007-03-29 12:57:58 |
Brian Murray |
None: statusexplanation |
|
|
|
| 2008-09-14 18:49:53 |
Colin Watson |
ubiquity: status |
New |
Confirmed |
|
| 2008-09-14 18:49:53 |
Colin Watson |
ubiquity: statusexplanation |
|
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). |
|
| 2009-08-28 18:35:19 |
Michael Terry |
summary |
feisty installer: time zone mismatch |
Time mismatch when hw clock is not UTC |
|
| 2009-08-28 18:36:39 |
Michael Terry |
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 |
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) |
|
| 2012-10-30 23:22:16 |
ભાવિન દોશી |
bug |
|
|
added subscriber BKD |
| 2020-03-05 12:02:56 |
Marcus Tomlinson |
ubiquity (Ubuntu): status |
Confirmed |
Incomplete |
|
| 2020-05-05 04:47:58 |
Launchpad Janitor |
ubiquity (Ubuntu): status |
Incomplete |
Expired |
|
