Get notification about sleep failed even though it seems to have gone well after suspend

[Thomas Novin]

When I do a suspend / standby it seems to go well but after waking up I get a notification about that sleep failed. I'm attaching info from syslog.conf which happens after I resume and also output from gnome-power-bugreport.sh.

$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=8.04
DISTRIB_CODENAME=hardy
DISTRIB_DESCRIPTION="Ubuntu hardy (development branch)"

[Thomas Novin (thomasn80)]

Maybe the sleep isn't 100% successful after all. Last night my computer automatically went to suspend mode because of critical battery. After suspend was done I shut the lid.

This morning when I plugged it in (still the lid closed) it woke up immediately and resumed where it was last night (playing a movie). I again got the notification about sleep failing.

$ lshal -m

Start monitoring devicelist:
-------------------------------------------------
08:46:36.315: computer_power_supply property ac_adapter.present = false
08:46:36.409: computer property power_management.is_powersave_set = true
08:46:38.354: computer_power_supply_0 property battery.remaining_time = 4352 (0x1100)
08:46:38.357: computer_power_supply_0 property battery.charge_level.current = 2720 (0xaa0)
08:46:38.358: computer_power_supply_0 property battery.reporting.current = 2720 (0xaa0)
08:46:38.359: computer_power_supply_0 property battery.rechargeable.is_discharging = true
08:46:38.360: computer_power_supply_0 property battery.rechargeable.is_charging = false
08:46:38.361: computer_power_supply_0 property battery.current = 2653 (0xa5d)
08:46:38.362: computer_power_supply_0 property battery.voltage.current = 15526 (0x3ca6)

[Thomas Novin (thomasn80)]

..but the following two sleeps I did didn't give me any popup about failing sleep. Difference is that these sleeps I manually triggered by issuing 'gnome-power-cmd.sh suspend'.

I get this when I do it from console every time though:

$ gnome-power-cmd.sh suspend
+ [ suspend = suspend ]
+ echo Suspending
Suspending
+ execute_dbus_method Suspend
+ dbus-send --session --dest=org.freedesktop.PowerManagement --type=method_call --print-reply --reply-timeout=2000 /org/freedesktop/PowerManagement org.freedesktop.PowerManagement.Suspend
Error org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
+ [ 1 -eq 0 ]

[Chris Jones (cmsj)]

fwiw, I've seen this intermittantly on a Thinkpad X40. It's certainly not obviously reproducible for me and I've never noticed any pattern to it.

[Elladan (elladan)]

This happens every time with my Compal CL56. Sleep works fine, but I get a screeching noise and a message that sleep failed when I resume.

[plomlund (jonas-iki)]

I get the same problem as Justin on his Compal on my old and trusty T42. I also get errors about stopping the Network Interface Plugging daemon fails. Here is the output from gnome-power-cmd.sh:

Suspending
Error org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

[Elladan (elladan)]

Update: This isn't every single time on my Compal CL56, but it is at least 50% of the time.

Looking through the logs, I see this show up occasionally:

Jun 9 23:32:17 thyme gnome-power-manager: (elladan) Suspending computer. Reason: The lid has been closed on ac power.
Jun 9 23:32:22 thyme kernel: [ 1685.691942] ADDRCONF(NETDEV_UP): eth1: link is not ready <-------------------------------
Jun 9 23:32:22 thyme kernel: [ 632.230603] ACPI: PCI interrupt for device 0000:02:01.0 disabled
Jun 9 23:32:22 thyme kernel: [ 843.114072] ACPI: PCI interrupt for device 0000:02:02.0 disabled
Jun 9 23:32:24 thyme kernel: [ 634.372406] Syncing filesystems ... done.
Jun 10 21:17:49 thyme kernel: [ 634.372719] Freezing user space processes ... (elapsed 0.00 seconds) done.

Also, this often shows up, but not always (I haven't verified that it's related):

Jun 8 16:20:02 thyme NetworkManager: <info> Deactivating device eth1.
Jun 8 16:20:03 thyme NetworkManager: <WARN> nm_device_802_11_wireless_get_mode(): error getting card mode on eth1: No such device

eth1 is my ipw2200 / Intel Centrino wifi chip.

[Paul Vinson Brown (paulminnabrown)]

Hi - first timer, so forgive my ignorance -- should this be marked as a copy of 199088? I guess this bug (195095) was reported first (assuming the numbers get bigger and not smaller...), but it seems that 199088 has a lot more activity and logs reported. Being so new here, I wasn't comfortable marking the change, but maybe someone with a bit more experience?

In any case, if you happened to find this bug, and would like to see a related (if not the same) one, go here:

https://bugs.launchpad.net/ubuntu/+source/hal/+bug/199088

ALSO, on the subject of the AWFUL screeching sound you get when waking up the computer -- it's due to this little guy right here: /usr/share/gnome-power-manager/gpm-suspend-failure.wav

It's interesting that the other "warning" sounds there are barely noticable clicks, boops and bips, but this one will knock your teeth out -- and usually in the MORNING of all times. But hey, at least I'm awake now.

In 199088 there's mention of how to disable sounds for failure situations, but I think a better solution might be to just replace that wav file with something a little more tame.