I can reproduce this bug. The keys for Hibernation (Fn+12) and Suspend-to-RAM (Fn+F4) don't work. This is an IBM Thinkpad R40 2722-CDG.
The produce IBM-specific events, which are caught by /etc/acpi/events/ibm-hibernatebtn and /etc/acpi/events/ibm-sleepbtn.
Those scripts in turn call /etc/acpi/hibernatebtn.sh and /etc/acpi/sleepbtn.sh.
Those scripts call acpi_fakekey $KEY_SUSPEND or acpi_fakekey $KEY_SUSPEND
where $KEY_SUSPEND = 205 and $KEY_SLEEP = 142 (from /usr/share/acpi-support/key-constants).
The calls to acpi_fakekey do nothing, even when I issue them on the command line. That seems to be the problem here...
If I call /etc/acpi/hibernate.sh or /etc/acpi/sleep.sh manually hibernation and STR work as expected.
I can reproduce this bug. The keys for Hibernation (Fn+12) and Suspend-to-RAM (Fn+F4) don't work. This is an IBM Thinkpad R40 2722-CDG.
The produce IBM-specific events, which are caught by /etc/acpi/ events/ ibm-hibernatebt n and /etc/acpi/ events/ ibm-sleepbtn. hibernatebtn. sh and /etc/acpi/ sleepbtn. sh. acpi-support/ key-constants) .
Those scripts in turn call /etc/acpi/
Those scripts call acpi_fakekey $KEY_SUSPEND or acpi_fakekey $KEY_SUSPEND
where $KEY_SUSPEND = 205 and $KEY_SLEEP = 142 (from /usr/share/
The calls to acpi_fakekey do nothing, even when I issue them on the command line. That seems to be the problem here...
If I call /etc/acpi/ hibernate. sh or /etc/acpi/sleep.sh manually hibernation and STR work as expected.
This is on Kubuntu Dapper.
Regards,
Mika