Hi Graziano,No, gnome-power-manager shouldn't be needed. It should just work. Could you try replacing /etc/acpi/sleep.sh by the attached version, then pressing the sleep button, and then send me the contents of /tmp/sleeplog? This will show me what's going on.
Cheers, Bart Obi wrote:
Hello Bart, thanks for the quick response! I don't have gnome-power-manager running: I used to but no longer. And I can try to run acpi_fakekey from the command line (sudo of course) and nothing happens. Do I need to have gnome-power-manager running to have it working? cheers graziano On Sun, Jun 03, 2007 at 12:48:09PM +0200, Bart Samwel wrote:Hi there, "Works for me", so I'm going to try and "remote debug" this. The reason for the two-stage thing (sending an acpi_fakekey from the button) is that when gnome-power-manager is running, it listens to these events and handles them. When gnome-power-manager or klaptopdaemon are running, the acpi-support sleep.sh script does nothing. To test if the problem lies with gnome-power-manager/klaptopdaemon, could you try the following: In /etc/acpi/events/sleepbtn, change the "action" line from: action=/etc/acpi/sleep.sh to action=/etc/acpi/sleep.sh force This will make the sleep script completely ignore gnome-power-manager/klaptopdaemon. If the sleep button then works again, the problem lies with gnome-power-manager/klaptopdaemon. If it doesn't, then the problem lies with acpi-support. Cheers, Bart
sleep.sh
Description: application/shellscript
