I can't give you the requested output at the moment but will do that soon.
But please re-read my comment above. The problem is definitely *not* with ACPI. The ACPI-events are generated, and the right scripts are executed.
The problem is with acpi_fakekey which generates fake input layer events (/dev/input/eventX). I can only assume that those events are then captured by hal or something else. Whatever it is that should be responding to these events in /dev/input/eventX is not working (at least in Kubuntu).
I think in breezy the ACPI-scripts just called the hibernation script directly, and there it worked. And I think it also worked under *U*buntu Dapper.
Hi, Paul!
I can't give you the requested output at the moment but will do that soon.
But please re-read my comment above. The problem is definitely *not* with ACPI. The ACPI-events are generated, and the right scripts are executed.
The problem is with acpi_fakekey which generates fake input layer events (/dev/input/ eventX) . I can only assume that those events are then captured by hal or something else. Whatever it is that should be responding to these events in /dev/input/eventX is not working (at least in Kubuntu).
I think in breezy the ACPI-scripts just called the hibernation script directly, and there it worked. And I think it also worked under *U*buntu Dapper.
Regards,
Mika