Hide Forgot
In GNOME 3.2 ACPI events from laptop buttons are misinterpreted. The gnome-power-manager settings are as follow: $ gsettings get org.gnome.settings-daemon.plugins.power button-power 'interactive' $ gsettings get org.gnome.settings-daemon.plugins.power button-sleep 'suspend' $ gsettings get org.gnome.settings-daemon.plugins.power button-suspend 'suspend' The suspend button on my laptop (Dell Vostro 3700) does nothing. I mean system isn't suspended. On the other hand after pressing power button there is no interactive dialog, but system shuts down. Version-Release number of selected component (if applicable): gnome-power-manager-3.2.1-1.fc16.x86_64 acpid-2.0.11-1.fc16.x86_64 How reproducible: always Steps to Reproduce: 1. Press suspend button or 1. Press power button Actual results: Described above. Expected results: Laptop should go to sleep after suspend button being pressed and show interactive dialog when power button is pressed. Additional info: Suspend is full supported on my system. I can put laptop to sleep from GNOME menu or with `pm-suspend` command. Sleep button event is catched by ACPI $ acpi_listen button/sleep SBTN 00000080 00000000 I don't know what about power button as system shuts down immediately. I'll be happy to provide more information if it's needed.
After update to acpid-2.0.13-1.fc16.x86_64 suspend button seems to work as expected. But strange thing happens when power button is pressed. I mean, the interactive dialog is shown, but after half a second system shuts down without waiting for user's action. Concerning the above scenario, I'm no longer sure it's acpid bug, but have no idea what component should I assign the issue to.
I see the same thing (interactive dialog shown, but no wait for interaction) on my Sony Vaio VPCEB17FX, but in my case the delay appears to be less than a tenth of a second.
I'm now running: gnome-power-manager-3.2.1-1.fc16.x86_64 acpid-2.0.14-1.fc16.x86_64 kernel-3.3.1-3.fc16.x86_64 and everything (suspend button, power button, interactive dialog) is working well on my Dell Vostro 3700. It's almost 5 months since I first reported the issue and I really don't remember when and how it was eventually fixed, but my guess would be kernel bumped up to 3.3.
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.