Description of problem: Just installed F16 and find that the computer never suspends after inactivity. I have explicitly set the power management options using DConf: org.gnome.settings-daemon.plugins.power sleep-inactive-ac true sleep-inactive-ac-timeout 60 Additionally, the power button appears to be configured to perform a suspend but when I press it a shutdown is performed. From the looks of it, either power management just isn't running at all or the configuration is being ignored. Version-Release number of selected component (if applicable): 3.2.1-1 How reproducible: Always Steps to Reproduce: 1. Use dconf-editor to set org.gnome.settings-daemon.plugins.power sleep-inactive-ac to true and sleep-inactive-ac-timeout 60 2. Close dconf-editor 3. Wait a couple of minutes Actual results: Nothing happens Expected results: Computer should have suspended
I'm extremely surprised that this has not gotten any attention. I recently upgraded (via preupgrade) my wife to F16 and it appears all of her power settings are being completely ignored. Nothing happens when the lid of her laptop is closed and if she forces it to sleep it doesn't come back up (although that's probably a kernel bug).
As larry said in the first comment, also the power-* settings are ignored. This might be easier to reproduce than waiting.
(In reply to comment #2) > As larry said in the first comment, also the power-* settings are ignored. This > might be easier to reproduce than waiting. I'm not sure what you mean. Unless someone else offers a solution or workaround, I don't have much choice but to wait for a response from the person responsible for this package/component.
just wanted to mention that with a recent upgrade the power-* settings started to work for me in F16 even though I didn't see a gnome-power-manager update (maybe acpid?).
The root cause of the problem may be the same as this bug I reported: https://bugzilla.redhat.com/show_bug.cgi?id=773681 Have you checked to make sure gnome-settings-daemon is running after you log in? I had to move ~/.local to a backup and let it get recreated and both the mouse and power settings started working. The annoying part is that there was no obvious error message that gnome-settings-daemon was failing to start or crashing (not sure which was happening).
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. 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 '16'. 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 16'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 16 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, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. 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 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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.