Red Hat Bugzilla – Bug 443130
System doesn't suspend if previous suspend/hibernate failed
Last modified: 2015-03-04 20:19:53 EST
Description of problem:
If, while suspended, my laptop does not properly "unsuspend" (say the battery
died) and I do a fresh power-on, the pm-utils lockfile is not removed from
/var/run/pm-utils/locks and subsequent attempts to suspend silently exit.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Put machine to sleep
2. Kill the power and boot from cold
3. Attempt to put machine to sleep again
pm-suspend exits without any warning. The lockfile never gets removed and
nothing ever warns me that the lockfile is still there
I should get notified that my attempt to suspend has failed (with a "stale lock
detected" warning) or something should detect and remove stale lockfiles.
Maybe an initscript could detect stale locks during a cold boot and delete them.
Or storing a PID or somesuch in the lockfile and doing a comparison in order to
detect a stale lock. Anything that's better than pm-suspend just exiting with a
1 no matter what you try (even "pm-suspend --help" silently exits) while the
lockfile is there.
Which version of initscripts are you using? This should be fixed in
initscripts-8.70-1 (see bug #442178)
initscripts-8.70-1 does fix the issue.
I had been travelling and hadn't been getting updates for the past couple of
days and only just caught up with updates. Thanks!