Comment 16 for bug 89069

Steps to reproduce:

Suppose the current time is 9:00 GMT, and you're in Shanghai, and your computer is connected to the Internet:

1. Enter BIOS and set RTC to 17:00, which is China Standard time GMT+800.

2. Boot feisty-desktop-i386 CD. You'll notice that the Gnome clock shows 9:00+, the current GMT time obtained from a time server by a script invoked by dhcp-client.

3. Start Install. Choose Asia/Shanghai as your timezone.

4. Shortly after installation step 7, you'll notice that the Gnome clock changes to 17:00+. Type date in gnome-terminal, you'll see that it's 17:00 UTC.

5. After Ubiquity installer finishes its job, type "sudo tune2fs -l <rootdevice>", you'll see that the last mount/write time is 17:00+. Since the current timezone is UTC, the last mount/write times are 8 hours ahead of current time.

6. Upon the first boot, fsck complains the last write/mount times are in the future and forces a filesystem check and a system reboot.

Proposed fix: Ubiquity shouldn't touch the system clock. Leave it alone and all is set.