Launchpad has imported 14 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=312761.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2007-09-29T22:21:48+00:00 Matthew 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.) Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-power- manager/+bug/137738/comments/5 ------------------------------------------------------------------------ On 2007-09-29T22:25:09+00:00 Matthew wrote: Created attachment 211441 pm-suspend log from "failed" hibernate Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-power- manager/+bug/137738/comments/6 ------------------------------------------------------------------------ On 2007-09-29T22:26:07+00:00 Matthew wrote: Created attachment 211451 portion of /var/log/messages related to "failed" hibernate Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-power- manager/+bug/137738/comments/7 ------------------------------------------------------------------------ On 2007-09-30T09:38:31+00:00 Till 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. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-power- manager/+bug/137738/comments/8 ------------------------------------------------------------------------ On 2007-09-30T21:15:37+00:00 Matthew wrote: OK How do I get better debug logs? Thanks. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-power- manager/+bug/137738/comments/9 ------------------------------------------------------------------------ On 2007-10-05T03:15:33+00:00 Matthias wrote: David, any clue about this ? Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-power- manager/+bug/137738/comments/10 ------------------------------------------------------------------------ On 2007-10-05T15:17:39+00:00 David 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 Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/137738/comments/11 ------------------------------------------------------------------------ On 2007-10-05T15:18:54+00:00 David wrote: Created attachment 217621 Patch to fix expected return types This patch should go upstream. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-power- manager/+bug/137738/comments/12 ------------------------------------------------------------------------ On 2007-10-05T18:28:08+00:00 David 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. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/137738/comments/13 ------------------------------------------------------------------------ On 2007-10-05T20:39:29+00:00 Matthew wrote: OK Got it. A quick hibernate-resume seems to work fine. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/137738/comments/14 ------------------------------------------------------------------------ On 2007-10-12T22:49:00+00:00 David wrote: *** Bug 330191 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-power- manager/+bug/137738/comments/21 ------------------------------------------------------------------------ On 2007-10-29T20:39:07+00:00 Andrew 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. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/137738/comments/23 ------------------------------------------------------------------------ On 2007-10-29T21:43:16+00:00 Jeremy 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. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-power- manager/+bug/137738/comments/24 ------------------------------------------------------------------------ On 2008-07-17T22:17:43+00:00 Andrew wrote: (sorry for the late reply). Confirming fixed, as I've not seen this in months. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-power- manager/+bug/137738/comments/26 ** Changed in: gnome-power-manager (Fedora) Importance: Unknown => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/137738 Title: [gutsy] suspend / hibernate works fine, but after resume, I get a "Failed to suspend" popup Status in gnome-power-manager package in Ubuntu: Fix Released Status in gnome-power-manager package in Fedora: Fix Released 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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/137738/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
