There is another workaround for this, though you will have to have a
root password for a fsck run at the end of daylight savings time: Set
the BIOS clock to local time, run sudo dpkg-reconfigure tzdata, set the
timezone to Universal or whatever they call it (I forgot the exact
designation), making sure that local time and GMT are listed as the same
time. Then, set the machine time as shown in gnome-panel to current
local time(otherwise the hardware clock might be the one that changes,
as you will see a wrong local time). Now, there is only one time in the
machine-and no clock changes during the boot process to foul things up.
You will have to set the clock back and forth for Daylight Saving Time
if used in your area, and there are a few things like astronomical and
navigation work for which this is not suited, but it worked for me when
nothing else would and I did not know about the "buggy init scripts"
workaround.
On my Atom laptop, this bug also was leaving me with the clock set
hours ahead unless I clicked on the clock to open the calender anyway,
so this fix solved that problem as well. This indicates the bug is NOT
in mountall but somewhere else, as the clock should not be getting moved
after boot to a wrong time anyway.
--
UNEXPECTED INCONSISTENCY: fails to boot ("last mount time is in the future")
https://bugs.launchpad.net/bugs/432070
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
