Comment 3 for bug 788415

Instructions here don't work:
http://www.vyvy.org/main/en/node/219

And trying to define a custom key launcher in gnome keyboard settings don't work (you have to press the key to define it).

I have crashed the system a few times now trying to test if it is disabled.

You apparently can't disable it in /etc/default/acpi-support because if gnome-power daemon is running it ignores its own settings and sends the message there.

There was a time when I had linux system uptimes of over a year. Regression like this is not acceptable. Some people have gone as far as removing the suspend/hibernate options from the shutdown menu on systems where suspend/resume is unreliable. And some disable suspend buttons on critical systems that should never be allowed to suspend.

upowerd is running, but doesn't seem (from its documentation) to do anything actually useful, just engage in dbus masturbation.

you probably can't disable it in xmodkeymap since it is probably intercepted by acpi.

How many programs are involved in handling the keyboard power button? BIOS ACPI, acpid, X keymap, upowerd, dbus, gnome-power, gconf, pm-utils (on some distributions), powerdevil, pm-suspend, pm-hibernate, /etc/acpi/*, etc. And no documentation.

Trying:
sudo perl -p -i -n -e "s/acpi_fakekey/#acpi_fakekey/" /etc/acpi/sleepbtn.sh
Of course, when I test this, it will kill the web browser where I am posting this.