[Bug 427822] Re: UTC should be "no" when installing under VirtualBox

[Dmitrijs Ledkovs]

It seems to me this is now resolved in virtualbox upsream, e2fsprogs and
linux kernel. Thus making ubiquity tasks redundant. Please correct this
status if there is still something left to do on ubiquity side.

** Changed in: ubiquity (Ubuntu)
       Status: New => Invalid

** Changed in: ubiquity (Ubuntu Karmic)
       Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubiquity in Ubuntu.
https://bugs.launchpad.net/bugs/427822

Title:
  UTC should be "no" when installing under VirtualBox

Status in Virtualbox:
  Invalid
Status in “e2fsprogs” package in Ubuntu:
  Invalid
Status in “linux” package in Ubuntu:
  Fix Released
Status in “ubiquity” package in Ubuntu:
  Invalid
Status in “e2fsprogs” source package in Karmic:
  Invalid
Status in “linux” source package in Karmic:
  Fix Released
Status in “ubiquity” source package in Karmic:
  Invalid

Bug description:
  Binary package hint: e2fsprogs

  When you are East of UTC, and your hardware clock is in localtime not
  UTC, and you have to force power down, fsck fails on boot because the
  last write time is in the future.

  This is caused by a bug in the ext3/4 filesystem code in kernel, where
  it updates the superblock last write time from the system clock after
  replaying the journal - but the system clock contains localtime not
  UTC since we haven't had an opportunity to correct it yet.

  Ted Tso (ext3/4 upstream) is working on a fix to not write this time
  when the filesystem is read-only

To manage notifications about this bug go to:
https://bugs.launchpad.net/virtualbox/+bug/427822/+subscriptions