Comment 4 for bug 89069

I think I have located the root cause of the problem. Ubiquity updates
the system clock to local time without changing the timezone accordingly,
which causes the last mount/write time 8 hours ahead in my case.
Everybody live in GMT + timezones shall experience the problem.

Colin, I think it's a separate bug from bug 63175, which shall be experienced
by users in the GMT minus timezones only. It is caused by the fact the kernel
considers the RTC time (the hardware clock) as UTC time, which makes the
initial system clock a couple of hours behind the UTC time for people living
in GMT minus timezones. Only after S50hwclock.sh does this mistake get corrected.