Hardware clock is modified when not required
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| clock-setup (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: clock-setup
During a minimal installation, the installer asks if the system clock is set to UTC. The hardware clock is in UTC and the current timezone is BST ( which switching to the console and running 'date' shows the correct local time. However, regardless of whether I select 'yes' or 'no' the installer runs the following command ( from 10clock-setup ):
log-output -t clock-setup chroot /target hwclock --systohc --debug &
which results in the hardware clock being changed an hour forward ( so it is localtime ).
There are no other systems installed on this machine so changing the hardware clock is unnecessary. If I remove this line during the installation ( before that script gets executed ), the hardware clock is unaltered, but the time is correct when booting into the freshly installed system ( i.e. it behaves as I would expect ).
