Bug 690485

I'm seeing this sometimes too on my 3 year all Dell Latitude 6400, which can still run for 4 hours + on its battery sometimes when it just comes out of suspend for some reason the battery reads 0 charge (or very close to it). It returns to a normal reading shortly after resuming from suspend, but sometimes it is too late since upower has already decided to hibernate the system.

I agree with the original reporter, that it would be a good idea to take some time for the battery reading to "settle" when coming out of suspend, before deciding to hibernate the system.

I also think there needs to be a way to dismiss or delay the hibernation.

I will often be working on my laptop when it suddenly decides I have 5% battery left (having been 15% just a moment previous), and it will warn about impending hibernation. It seems that no matter how quickly I grab the AC adapter and plug it in, it has already initiated the hibernation and can't be cancelled. Occasionally if I can get it plugged in within 10 seconds or so it won't hibernate, but it's really too short a delay. If I were able to press a "wait 60 seconds" button that'd be much better.

It would also be nice if user control and ability to abort hibernation were still possible later in the hibernation sequence. Once dirty pages have been swapped to disk and the files to trigger thawing have been created, it should be relatively safe to allow the system to run for a few more seconds pending an AC charge event.

This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19

This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.