"system clock set to local" horked in breezy installer

[Akkana Peck]

Breezy installer, expert mode, on a machine that has the system clock set to
local time.
If GMTTIME is the current time in GMT, and LOCALTIME is the current local time,
it prints:

The hardware clock says the time is now LOCALTIME.
Is the hardware clock set to GMT?

I say No, and select my time zone. It says:

Local time is now: LOCALTIME-TZ
Universal time is now: LOCALTIME
Time zone is set to: US/Pacific

Trying again doesn't help. But what does work strangely, is that if I say the
system clock IS in GMT (it gives me, as expected, the wrong answer), say this is
not correct, then go back and tell it the system clock is NOT in GMT, that time
it works. It only works with system clock in localtime after I've once
incorrectly told it that the system clock is in GMT.

[Peter Whittaker (pwwnow)]

Is this related to 23216 and 29704?

[Colin Watson (cjwatson)]

Please try this with dapper. The installer no longer attempts to set the hardware clock while it's running, and so no longer displays the current time; I believe deferring this to the first boot as we now do should work better, but I would appreciate testing.

[Carthik Sharma (carthik)]

I am closing this bug since Colin had said a couple of months ago that there is a fix that has been released and needs testing. If this issue still persists for you, please reopen this bug.
Thank you for reporting this issue.