I'm not sure if that is posible, as it seems gnome-screensaver surpresses the keyevent after it has catched it.
I think the problem here is that the screensaver is responsible for locking the screen, whereas the gnome-power-manager is responsible for saving power by turning dpms off.
At least the screensaver should send and event to the gnome-power-manager to decide if the screen should be turned off.
I think this bug does NOT concern acpi, but a combination of gnome-screensaver and gnome-power-manager!
Personaly I set up a acpi event catching Fn+F1 to call screenblank.sh, which works as predicted. Fn+F1 is still handled by acpid. But this is just a workaround!
I'm not sure if that is posible, as it seems gnome-screensaver surpresses the keyevent after it has catched it.
I think the problem here is that the screensaver is responsible for locking the screen, whereas the gnome-power-manager is responsible for saving power by turning dpms off.
At least the screensaver should send and event to the gnome-power-manager to decide if the screen should be turned off.
I think this bug does NOT concern acpi, but a combination of gnome-screensaver and gnome-power- manager!
Personaly I set up a acpi event catching Fn+F1 to call screenblank.sh, which works as predicted. Fn+F1 is still handled by acpid. But this is just a workaround!