Ubuntu
gnome-power-manager package

[gutsy] suspend / hibernate works fine, but after resume, I get a "Failed to suspend" popup

Bug #137738 reported by Jens
42
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-power-manager (Fedora)
Fix Released
Low
gnome-power-manager (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

I just installed Gutsy from a 2007-09-05 ISO snapshot from cdimage.ubuntu.com, and this is my fourth bug report :-)

When I suspend or hibernate, and then resume, everything works fine. But:

- during hibernate, my notebook's LCD backlight is still on. This is not necessary (IMHO) ... switch it off early, and save battery power!

- during hibernate, because the screen is still on, I get a huge truckload of USB kernel warnings spewed all over my console. They don't have any (visible) effect but they generate the impression that something is "wrong" or "unfinished" in Ubuntu. IMHO.

- after resume, I get a GNOME popup speech bubble wrongly claiming that the suspend process failed, and asking me whether I want to visit a "quirks website".

I truly appreciate the effort of making this more user friendly and trying to detect failed suspends and the like, however - something is wrong in this detection, because my notebook _does_ suspend fine. Here are its hardware specs:

0000:00:00.0 Host bridge: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller (rev 02)
0000:00:00.1 System peripheral: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller (rev 02)
0000:00:00.3 System peripheral: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller (rev 02)
0000:00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02)
0000:00:02.1 Display controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02)
0000:00:1d.0 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 (rev 03)
0000:00:1d.1 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 (rev 03)
0000:00:1d.2 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 (rev 03)
0000:00:1d.7 USB Controller: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB2 EHCI Controller (rev 03)
0000:00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 83)
0000:00:1f.0 ISA bridge: Intel Corporation 82801DBM (ICH4-M) LPC Interface Bridge (rev 03)
0000:00:1f.1 IDE interface: Intel Corporation 82801DBM (ICH4-M) IDE Controller (rev 03)
0000:00:1f.3 SMBus: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) SMBus Controller (rev 03)
0000:00:1f.5 Multimedia audio controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 03)
0000:00:1f.6 Modem: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Modem Controller (rev 03)
0000:01:03.0 CardBus bridge: Texas Instruments PCI1410 PC card Cardbus Controller (rev 02)
0000:01:07.0 Network controller: Intel Corporation PRO/Wireless 2200BG (rev 05)
0000:01:0a.0 FireWire (IEEE 1394): Texas Instruments TSB43AB22/A IEEE-1394a-2000 Controller (PHY/Link)
0000:01:0c.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)

Revision history for this message
teedog (teedog) wrote :

Could this bug be related?
https://bugs.launchpad.net/ubuntu/+source/acpi-support/+bug/137477
So far 3 different people with resume problems, but slightly different symptoms. :(

Revision history for this message
Gert Kulyk (gkulyk) wrote :

Confirming this on my HPNX6110.

Revision history for this message
Gert Kulyk (gkulyk) wrote :

Sorry, as I've seen later on I have to be slightly more precise:

I can confirm that after resuming from suspend the error-message appears, although suspend seems to work fine. For me LCD-Backlight-issue does not apply, don't think that the above mentioned bug is related to #137477.

Revision history for this message
Joss Winn (josswinn) wrote :

I get this message now after moving from Feisty to Gutsy. Didn't get it before. Interestingly, I've looked on the Quicks website and it recommends some tests using the command 'pm-suspend' but this command/package does not seem to be available on any Ubuntu release. It would be ncie to get rid of this message or understand what the 'problem' is. I'm using a Lenovo 3000 N100 0768FPG

Revision history for this message
In , Matthew (matthew-redhat-bugs) wrote :

Description of problem:
I hibernate my Thinkpad T61 and that seems to work fine, but on resume the pm
applet pops up a balloon saying it failed.

Version-Release number of selected component (if applicable):
pm-utils-0.99.4-3.fc8

How reproducible:
Always

Steps to Reproduce:
1. Hibernate using pm applet.
2. Resume.
3.

Actual results:
Error balloon pops up claiming hibernate failed.

Expected results:
No error ballon. (Either because it worked or because whatever error occured
has been fixed...)

Additional info:

I'm attaching pm-suspend.log and relevant secctions of messages. I had SELinux
in permissive mode for this test, but you will see some AVCs in the log.

(Looking at the log, I'm not sure if this is a pm-utils issue or a kernel issue,
but I'll file here first.)

Revision history for this message
In , Matthew (matthew-redhat-bugs) wrote :

Created attachment 211441
pm-suspend log from "failed" hibernate

Revision history for this message
In , Matthew (matthew-redhat-bugs) wrote :

Created attachment 211451
portion of /var/log/messages related to "failed" hibernate

Revision history for this message
In , Till (till-redhat-bugs) wrote :

Afaik, the applet belongs to gnome-power-manager, the pm-suspend does not
contain any warnings, therefore I guess it is an applet issue.
Maybe you need to increase verbosity to get a helping log, because the critical
log entries seem to be:

Sep 29 18:02:37 valkyrie gnome-power-manager: (mjs) Resuming computer
Sep 29 18:02:37 valkyrie gnome-power-manager: (mjs) hibernate failed

But a reason why it failed is missing.

Revision history for this message
In , Matthew (matthew-redhat-bugs) wrote :

OK How do I get better debug logs? Thanks.

Revision history for this message
In , Matthias (matthias-redhat-bugs) wrote :

David, any clue about this ?

Revision history for this message
In , David (david-redhat-bugs) wrote :

g-p-m is expect the wrong return types from hal; so I wrote a patch (will attach
in the next comment) but for some reason beyond me I still get the "Sleep
problem" dialog from g-p-m. Richard, what gives?

FWIW, it works fine using dbus-send:

[davidz@oneill ~]$ dbus-send --print-reply --system --dest=org.freedesktop.Hal
/org/freedesktop/Hal/devices/computer
org.freedesktop.DBus.Introspectable.Introspect |grep -2 Suspend
  </interface>
  <interface name="org.freedesktop.Hal.Device.SystemPowerManagement">
    <method name="Suspend">
      <arg name="num_seconds_to_sleep" direction="in" type="i"/>
      <arg name="return_code" direction="out" type="i"/>
    </method>
    <method name="SuspendHybrid">
      <arg name="num_seconds_to_sleep" direction="in" type="i"/>
      <arg name="return_code" direction="out" type="i"/>
[davidz@oneill ~]$
[davidz@oneill ~]$
[davidz@oneill ~]$ dbus-send --print-reply --system --dest=org.freedesktop.Hal
/org/freedesktop/Hal/devices/computer
org.freedesktop.Hal.Device.SystemPowerManagement.Suspend int32:0
method return sender=:1.4 -> dest=:1.434 reply_serial=2
   int32 0
[davidz@oneill ~]$
[davidz@oneill ~]$
[davidz@oneill ~]$ dbus-send --print-reply --system --dest=org.freedesktop.Hal
/org/freedesktop/Hal/devices/computer
org.freedesktop.DBus.Introspectable.Introspect |grep -2 Hibernate
      <arg name="return_code" direction="out" type="i"/>
    </method>
    <method name="Hibernate">
      <arg name="return_code" direction="out" type="i"/>
    </method>
[davidz@oneill ~]$ dbus-send --print-reply --system --dest=org.freedesktop.Hal
/org/freedesktop/Hal/devices/computer
org.freedesktop.Hal.Device.SystemPowerManagement.Hibernate
[davidz@oneill ~]$
[davidz@oneill ~]$
[davidz@oneill ~]$ dbus-send --print-reply --system --dest=org.freedesktop.Hal
/org/freedesktop/Hal/devices/computer
org.freedesktop.Hal.Device.SystemPowerManagement.Hibernate
method return sender=:1.4 -> dest=:1.487 reply_serial=2
   int32 0

Revision history for this message
In , David (david-redhat-bugs) wrote :

Created attachment 217621
Patch to fix expected return types

This patch should go upstream.

Revision history for this message
In , David (david-redhat-bugs) wrote :

OK, so it turns out we're getting a D-Bus timeout. Actually g-p-m got codepaths
to handle this [1] but the call site passes NULL for the GError so we never get
to examine this and properly handle timeouts. This patch

http://cvs.fedoraproject.org/viewcvs/devel/gnome-power-manager/gnome-power-manager-2.20.0-use-gerror.patch?rev=1.1&view=auto

takes care of that. I've tested and it works. Also, there's an update of the
patch in comment 7; you want this one instead

http://cvs.fedoraproject.org/viewcvs/devel/gnome-power-manager/gnome-power-manager-2.20.0-expected-return-types.patch?rev=1.1&view=auto

So this is fixed in -3 which is building right now. You can beat the rush and
get the 0day warez right here

http://koji.fedoraproject.org/koji/taskinfo?taskID=184871

Thanks.

[1] : because dbus-glib sucks and don't let you specify INT_MAX or a magic
sentinel to say "unlimited" as a timeout; this is really needed because the
(wall-clock) time between when Hibernate() is invoked and when it returns (e.g.
when the system resumes) can be infinitely long.

Revision history for this message
In , Matthew (matthew-redhat-bugs) wrote :

OK Got it. A quick hibernate-resume seems to work fine.

Revision history for this message
Joss Winn (josswinn) wrote :

I'm still getting this when closing my lid or using my suspend hotkey. I don't get the warning when selecting the suspend icon. Using an up-to-date Gutsy installation.

Revision history for this message
Gert Kulyk (gkulyk) wrote :

Confirming that the error-message does not pop up after resume if using log-out-dialog, but when lid-closed or suspend-button used. Maybe a bug in g-p-m?

Revision history for this message
Gert Kulyk (gkulyk) wrote :

Seems like it really is a gnome-power-manager bug. E.g. https://bugzilla.redhat.com/show_bug.cgi?id=312761, dealing with hibernation, but should apply to suspend, too. This commit to gnome svn trunk should fix this, will try it later on:

http://svn.gnome.org/viewcvs/gnome-power-manager/trunk/src/gpm-manager.c?r1=2384&r2=2523

Revision history for this message
Gert Kulyk (gkulyk) wrote :

The mentioned patch fixes the issue for me, applies cleanly to ubuntu sources. If there will be no new upstream package before the final gutsy release, please consider it for inclusion because the message may confuse users.

Bug Watch Updater (bug-watch-updater)
Changed in gnome-power-manager:
status: Unknown → Fix Released
Revision history for this message
Sebastien Bacher (seb128) wrote :

I've uploaded a package revision with the patch from svn

Changed in gnome-power-manager:
status: Confirmed → Fix Committed
Revision history for this message
Sebastien Bacher (seb128) wrote :

gnome-power-manager (2.20.0-0ubuntu4) gutsy; urgency=low

  * debian/patches/90-from-svn-fix-incorrect-suspend-error.patch:
    - patch from SVN, fix suspend error being displayed incorrectly
      (LP: #137738)

 -- Sebastien Bacher <email address hidden> Wed, 10 Oct 2007 20:05:03 +0200

Changed in gnome-power-manager:
status: Fix Committed → Fix Released
Revision history for this message
In , David (david-redhat-bugs) wrote :

*** Bug 330191 has been marked as a duplicate of this bug. ***

Revision history for this message
soccerboy (man88soccer) wrote :

I am using a Toshiba Satellite M55 and when I set my power management preferences to suspend my computer, and the computer sleeps, my computer goes haywire. When I wake it up, it returns to the desktop for about 15-20 seconds saying that the suspend did not work correctly and then it goes to a black screen with a lot of lines saying stuff about usb. Then the computer turns off. When I turn it back on, and log in, the computer returns to the state that it was in when it suspended except for the fact that network manager can't connect to my wireless network. I have the same problem when my computer hibernates as a result of running low on battery.

I'll provide more information if you need it but am not sure what I need to provide to make solving the problem easier.

Revision history for this message
In , Andrew (andrew-redhat-bugs) wrote :

quick hibername-resumes are the easy part, you need to leave it overnight for a
correct test.

gnome-power-manager-2.20.0-6.fc8 still fails.

Revision history for this message
In , Jeremy (jeremy-redhat-bugs) wrote :

I just hibernated and then set my clock forward two months (party like it's
December 29th! :-) and resumed and things are fine.

Andrew -- If you're still seeing a failure message, it's likely due to something
actually failing. Please open another report and include
/var/log/pm-suspend.log from when it says it fails.

Revision history for this message
Nicholas Stack (nickstack) wrote : Re: [gutsy] now in Hardy suspend / hibernate works fine, but after resume, I get a "Failed to suspend" popup

Binary package hint: gnome-power-manager

My Desktop hibernates /resumes fine, although after each resume I get a bubble notification saying "Your computer failed to suspend".

It seems like this should have been fixed a long time ago and now is back in Hardy. Let me know if there is any other information I can provide.

Revision history for this message
In , Andrew (andrew-redhat-bugs) wrote :

(sorry for the late reply). Confirming fixed, as I've not seen this in months.

Revision history for this message
Juan Lucas Rey (juanlucasrey) wrote :

Hello I had the same problem. After going to system->power management->general, I deactivated the "use sound to notify etc.." and it worked perfectly, without even giving an error message in text mode.

Maybe this could help tracking the problem: the sound feature would be responsible for the bug??!

Revision history for this message
Jonathan Avraham (shambler-com) wrote :

I'm having this problem in a updated Jaunty on an AMD Athlon XP 1900 with Geforce4 MX 440 (nvidia proprietary drivers).

Bug Watch Updater (bug-watch-updater)
Changed in gnome-power-manager (Fedora):
importance: Unknown → Low
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

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