FS#5444 - After installation, wrong time in the hardware clock if it's in local time

Attached to Project: Arch Linux
Opened by Dimos Dimoulis (dimosd) - Monday, 25 September 2006, 12:49 GMT
Task Type Bug Report
Category System
Status Closed
Assigned To Aaron Griffin (phrakture)
Architecture not specified
Severity Low
Priority Normal
Reported Version 0.7.2 Gimmick
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

After installing Arch, I found the clock of my computer a few hours off (it's in local time).

The installer initially assumes the hardware clock is in UTC. When the user selects local time and a time zone, the system clock is now a few hours off and yet this wrong time is written back to the hardware clock.

The easiest fix would be to skip writing the time back to the hardware clock during shutdown. Alternatively, read the hardware clock again as soon as the user has changed the setting to local time.
This task depends upon

Closed by  Roman Kyrylych (Romashka)
Wednesday, 29 November 2006, 22:49 GMT
Reason for closing:  Fixed
Comment by Tobias Powalowski (tpowa) - Monday, 25 September 2006, 15:55 GMT
is this still valid in those isos?
http://www.archlinux.org/~tpowa/newisos/
Comment by Dimos Dimoulis (dimosd) - Tuesday, 17 October 2006, 14:25 GMT
5529 reports the same problem and gives some extra info. The time in BIOS is still valid after first boot (according to that bug report), but is corrupted on first boot.

Perhaps zoneinfo is wrong on first boot (e.g. linked to GMT)?
Comment by Roman Kyrylych (Romashka) - Saturday, 11 November 2006, 13:35 GMT
dimosd, please confirm this fix: http://bugs.archlinux.org/task/5529#comment12432

Loading...