Comment 1 for bug 555585

There were also no warnings about low-battery conditions. As my battery ran out, the system unexpectedly tried to suspend (as evidenced by a dialog saying it failed to), and later went into sudden shutdown.

The shutdown also caused other problems: the real-time clock was reset to the distant past (sometime before 2001), the system failed to recover a usable clock setting once it was working again, the filesystem needed fsck, the fsck message on the boot screen was broken, and the fsck failed; I'll file separate bugs for those issues.