I think this is an acpi-support bug (i.e., this bug is caused by acpi-support being here at all) - acpi-support is set up to synthesize a 'sleep' key event when pressing Fn+F4, but the kernel already handles synthesizing this event, so we end up with *two* hal sleep events showing up on two different input devices.
Whether the hal events are what g-p-m or kpowersave should be listening for is a separate question - but we definitely shouldn't be emitting two sleep events for one key press.
Conveniently, it happens that I've already committed a fix for this to the acpi-support bzr branch, and will upload soon. In the meantime, users can verify that this fixes the problem by running 'sudo /etc/init.d/acpid stop' and then suspending with Fn+F4.
> 15:12:41.659: computer_ logicaldev_ input_3 condition ButtonPressed = sleep i8042_i8042_ KBD_port_ logicaldev_ input condition ButtonPressed = sleep
> 15:12:41.690: platform_
I think this is an acpi-support bug (i.e., this bug is caused by acpi-support being here at all) - acpi-support is set up to synthesize a 'sleep' key event when pressing Fn+F4, but the kernel already handles synthesizing this event, so we end up with *two* hal sleep events showing up on two different input devices.
Whether the hal events are what g-p-m or kpowersave should be listening for is a separate question - but we definitely shouldn't be emitting two sleep events for one key press.
Conveniently, it happens that I've already committed a fix for this to the acpi-support bzr branch, and will upload soon. In the meantime, users can verify that this fixes the problem by running 'sudo /etc/init.d/acpid stop' and then suspending with Fn+F4.