Ubuntu
hal package

gpm refuses to suspend to ram after some time

Bug #49442 reported by Kasper Peeters
This bug report is a duplicate of:  Bug #53984: hal cannot obtain list of devices. Edit Remove
6
Affects Status Importance Assigned to Milestone
hal (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: gnome-power-manager

After a fresh boot, suspending my laptop works fine (by closing the lid or by choosing suspend from the logout menu). However, after some time (I haven't yet been able to determine which actions triggers this problem), gnome-power-manager does not recognise anymore that I have allowed the machine to suspend. Closing the lid does nothing anymore, and when I choose 'logout' from the menu there is no option anymore to suspend the machine.

Killing g-p-m and calling /etc/acpi/sleep.sh by hand still works, and the machine still wakes up fine after that, so it is definitely a g-p-m problem.

Any suggestions on how to debug this further?

Revision history for this message
Kasper Peeters (kasper-peeters) wrote :

It just happened again. I re-opened the lid and typed lshal, which gave

  lshal: Couldn't obtain list of devices

(typed from memory, might be slightly different).

Now for the weird part: I then ran 'lshal -m', ctrl-c'ed it, 'lshal' again (no change), checked that lshald and dbus are running (they were). Then, upon one last try, 'lshal' now all of a sudden showed all the devices again!
And suspending also worked again.

Revision history for this message
Kasper Peeters (kasper-peeters) wrote :

Pinned down to a problem with hal not being able to obtain the device list.

Revision history for this message
Mark Reitblatt (mark-reitblatt) wrote :

So do you have a fix? Do you still have this problem?

Revision history for this message
Kasper Peeters (kasper-peeters) wrote :

Yes, this problem is still there. It's tricky since it only occurs on one machine (all other Dapper machines work fine, but they have different hardware too, so it may be a driver issue somewhere which triggers a bug in gpm). In any case, I'm attaching a gpm log file in case that helps the debugging process. It contains some **WARNING** lines which perhaps help to pin down what's going on. I can't see anything very useful in the daemon.log (with hald output), but I'll attach that too.

Revision history for this message
Kasper Peeters (kasper-peeters) wrote :
Revision history for this message
Rich Johnson (nixternal) wrote :

Are you still experiencing these issues with any of the latest updates or any of the latest stable releases?

Changed in hal:
status: Unconfirmed → Needs Info
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for hal (Ubuntu) because there has been no activity for 60 days.]

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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