Auto-hibernate due to inactivity results in a resumed session with hanged gnome-power-manager preventing the system from entering hibernate again

Bug #311860 reported by jasonwc
6
Affects Status Importance Assigned to Milestone
gnome-power-manager (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: gnome-power-manager

1) Ubuntu 8.10 (Intrepid)
2) 2.24.0-0ubuntu8.1
3) I expected the system to resume from hibernate properly without outputting error messages or hanging gnome-power-manager.

4) I am able to manually hibernate the system from the GNOME menu and resume without issue. However, if the system hibernates automatically after a period of inactivity, when the system is resumed I see the below error message. In addition, it appears that gnome-power-manager has hanged because selecting hibernate from the GNOME menu does nothing. In addition, when I attempt to shut down I am warned that gnome-power-manager is not responding. Killing gnome-power-manager and restarting it restores hibernate functionality.

Error Message: http://img48.imageshack.us/img48/495/hibernatewarningpq2.png

Revision history for this message
jasonwc (jwittlincohen) wrote :
description: updated
description: updated
description: updated
description: updated
Revision history for this message
jasonwc (jwittlincohen) wrote :

WORKAROUND:

This issue doesn't arise if the system uses uswsusp rather than the kernel's method of hibernation. So, the fix is to force gnome-power-management to use s2disk rather than the kernel method. This is fairly simple to do:

Download the attached script "hal-system-power-hibernate-linux"

sudo apt-get install uswsusp
sudo s2disk ##Test to see if s2disk works. CAUTION: make sure data is saved for this test!

sudo mv /usr/lib/hal/scripts/linux/hal-system-power-hibernate-linux /usr/lib/hal/scripts/linux/hal-system-power-hibernate-linux.backup
sudo cp hal-system-* /usr/lib/hal/scripts/linux/
sudo chmod 755 /usr/lib/hal/scripts/linux/*

Now, gnome-power-manager should use s2disk to hibernate fixing my reported issue.

Note: I found these instructions from http://blog.paulbetts.org/index.php/2007/02/11/fixing-software-suspend-hibernate-with-uswsusp-in-ubuntu-feisty-and-edgy/#comment-17671. The only change I made was to modify the script to reflect the location of the s2disk binary in Ubuntu 8.10.

Revision history for this message
jasonwc (jwittlincohen) wrote :

BETTER WORKAROUND:

sudo apt-get install uswsusp
sudo dpkg-divert --rename --divert /usr/sbin/pmi-disabled /usr/sbin/pmi

To undo:

sudo dpkg-divert --rename --remove /usr/sbin/pmi

See http://blog.paulbetts.org/index.php/2007/02/11/fixing-software-suspend-hibernate-with-uswsusp-in-ubuntu-feisty-and-edgy/#comment-17671 (Comment by Robin Battey)

Revision history for this message
dotnetCarpenter (activ876) wrote :

Hi Jason.

Do you think it would be foolish of me to try your workaround for my problem?
https://bugs.launchpad.net/ubuntu/+bug/313724

Sorry a noob when it comes to linux/ubuntu

Revision history for this message
Scott Howard (showard314) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue that you reported is one that should be reproducible with the live environment of the Desktop CD of the development release - Karmic Koala. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at http://www.ubuntu.com/testing/. Thanks again and we appreciate your help.

Changed in gnome-power-manager (Ubuntu):
status: New → Incomplete
Revision history for this message
Victor Vargas (kamus) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem. Please reopen it if you encounter that this issue is still occurring or even better if you can check in latest Ubuntu Karmic version. To reopen the bug report you can click under the Status column, and change the Status back to "New". Thanks again!

Changed in gnome-power-manager (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.