Description of problem: When suspending for a prolonged period of time, gnome-power-manager would erroneously hibernate the machine right after resuming. This is regardless of battery level. Version-Release number of selected component (if applicable): gnome-power-manager-2.25.2-1.fc11.x86_64 How reproducible: Always Steps to Reproduce: 1. Suspend (close the lid on battery power, or click on notification applet and select the action) 2. Wait 1 hour or so 3. Resume Actual results: After resuming, within a few seconds (enough time to unlock the screen saver) g-p-m would hibernate the machine Expected results: No hibernation (try killing gnome-power-manager and verify that, on resume, hibernation does not get triggered) Additional info: Dell Inspiron 1318, Intel Core 2 Duo with Rawhide x86_64.
s|volume|power Additional information: - if the power adapter is plugged in when resuming, this behavior is not observed - if resuming while on battery power, gnome-volume-control-applet dies; additionally, the GNOME theme and font information also gets reset to the default until the Appearance capplet is run.
The volume control applet issue is unrelated. The Rawhide g-p-m appears to have fixed this issue, but now that I'm back on F-10, I can report that the same problem occurs here. gnome-power-manager-2.24.3-1.fc10.x86_64 (battery level is at 90%, after I suspended, the machine hibernated on resume, and I booted it up again, and the power management profile is to hibernate only when battery level is critical)
I can reproduce the exact same behavior as Michel on a T61 (laptop hibernates after long suspends, only when running on battery power). Let me know if I can provide any logs or test any new updates to fix this :-)
Still happens with F11?
I am unfortunately exclusively on Rawhide now (meant to keep my netbook on F-11, but then all the gnome-shell and Moblin goodness landed). Ricky?
I have not left my laptop suspended for long amount of time in the past few months, but I will start to do so very often in the coming month or so, so I'll report back if I see this happen again.
This message is a reminder that Fedora 10 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 10. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '10'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 10's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 10 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.