Comment 2 for bug 665806

OK, scrap the thing about JACK. It must have been luck before, but now I was able to get the forced hibernation without jackd running at all. The rather infurinating thing is that I get dialog that tells about the fact and offers "OK" and "Cancel" buttons... which have no effect on the action being taken. It might be nice if "Cancel" being pressed withing some time frame would cancel the hibernation process. I even triggered multiple hibernations in a row (unplug, plug, unplug). Causing the laptop to go to sleep again right after waking up.

Anyhow: When unplugging from wall power, I get this notification blended onto the desktop about battery state ... and it tells me about 0:02 of battery runtime, 99% .. which somewhat contradicts the information when clicking on the battery applet, there I get 99%, OK, but also the much more sensible estimated runtime of 1:59 or so.

Still, this seems to be a timing issue, perhaps the ACPI information doesn't change atomically, or there is just an error in the runtime calculation using an outdated value of whatnot. I suspect, that this might be worked around by waiting some seconds and then recomputing the remaining runtime -- and only triggering the emergency if the situation is confirmed.

I do wonder though, if nobody else can reproduce this. Is the MSI Wind U100 BIOS just broken? I'm remined of the strange issues with the webcam and USB, or the Bluetooth/WLAN switch not working correctly by chance (gladly, it works in the Maverick install, as opposed to the live system from USB).