Hibernate hotkey (fn + ...) triggers suspend to ram

Status changed to 'Confirmed' because the bug affects multiple users.

I can confirm this on Thinkpad T61p running Oneiric final (upgraded from Natty). The hotkey was working perfectly on Natty.

Thank you for your bug report, what event does "xev" reports for that key? Is the keybinding correctly assigned in the system settings?

attached is xev output.

by system settings, do you mean the System Settings app? That contains Power and Keyboard at least that might
be relevant. I see no keyboard related stuff under Power nor any hibernate/suspend related stuff under Keyboard->Shortcuts->System.

Could you run dconf-editor, go to org.gnome.settings-daemon.plugins.power and set "button-sleep" to key to "suspend", does it change the behaviour?

sorry ignore that, I confused several issues there

This is caused by a mistake in the 49_fix_suspend_media_key.patch patch.

The gnome-settings-daemon package currently in -proposed should fix the issue.

Could someone please try the gnome-settings-daemon package in -proposed and comment here if it is now fixed?

I have the proposed repository enabled and the updates today broke the suspend (Fn+F4) and the hibernate (Fn+F12) hotkeys completely. Nothing happens with a hotkey press. Before the updates the suspend key was working as expected, but, as per the bug report, the hibernate hotkey resulted in the suspend action.

right, that's bug #878076, there is another update on its way

I just updated with the proposed repository enabled and fn+f12 still suspends. The gnome-settings-daemon changelog is dated
19 Oct 2011.

I am also affected by this issue. I use a Thinkpad T400 Model 6474-19G. I updated from Natty 64Bit (Fn+F12 worked) to Oneiric 64Bit and since the update Fn+F12 no longer works.

I need to be more precise: Fn+F12 leads to StandBy (SubspendToRAM) and not to Hibernate (SuspendToDisk) since updating to 11.10. In 11.04 all worked as expected.

I am also affected. Using a Thinkpad T60. On 11.04 Fn+F12 triggered suspend to disk, since the upgrade to 11.10 it triggers only suspend to RAM.

Hey Martin, I know you debugged similar issues in the past, do you have any clue what informations would be useful there? I guess to start having the keyevent sent would be useful, is xev the right thing to use there (I think not but I don't remember which one we should use instead ;-). Do you know how to check also if there is something in the lower level component that could be triggering the suspend?

Can you please exercise the "Fixing broken keys" section in /usr/share/doc/udev/README.keymap.txt ? I suppose we are assigning the wrong key code to the key. Thanks!

does not work for me:
benjamin@benjamin-ThinkPad-T400:/lib/udev$ ./findkeyboards
AT keyboard: no device node found
benjamin@benjamin-ThinkPad-T400:/lib/udev$ sudo ./findkeyboards
[sudo] password for benjamin:
AT keyboard: no device node found

Benjamin: Can you please try the "keymap -i" part with all devices from input/event1, input/event2, etc. until you hit one which reacts to the suspend key? Also, if you attach the "udevadm info --export-db" output, I might be able to fix findkeyboard to also work on that model.

benjamin@benjamin-ThinkPad-T400:~$ sudo /lib/udev/keymap -i input/event5
Press ESC to finish, or Control-C if this device is not your primary keyboard
scan code: 0x0B key code: suspend

Same here on a ThinkPad X220.

I have the same issue on Ubuntu Precise but as others have pointed out this worked fine in Ubuntu Natty and the regression occurred in Oneiric.

The key for hibernate on my Dell Precision is Fn+F1 and in the udev dell keymap it is listed as "0x8A suspend" but it suspends to ram not to disc so clearly the command is not executing the correct task.

Same on a T520 using Ubuntu 12.04 "precise". Suspend (Fn+F4) leads to scan code 0x03 "sleep", hibernate (Fn + F12) emits scan code 0x0B "suspend".
I tried to set the power-keys in org.gnome.gnome-settings-daemon.power like this:
button-hibernate: hibernate
button-sleep: sleep
button-suspend: hibernate

However, my system just enters sleep in any case.

My desktop is gnome-shell, i do not know if this has some influence on this issue.

Addendum: After a restart, it works. I have no clue why, but the setup in #22 has just to be swapped, by assigning this new configuration, it works:
button-sleep: hibernate
button-suspend: suspend

Just to keep the record complete, the changes markusj suggested didn't work on my R61. I'd imagine this is probably the case for others too. For now, I've worked around it by using CompizConfig Settings Manager to assign Super-F12 to a command that invokes hibernate, but this seems like it ought to be a silly regression that should be easy to sort out at the code level...

The same wrong behaviour of Fn-F12 with precise on T500.

Nothing changed in 12.10 as for today.

Confirmed wrong behaviour in 12.10 on a R61.

I noticed that pressing Fn+F4 (suspend) actually triggers hibernate, while Fn+F12 triggers suspend. I have set all power-keys to hibernate as hinted in #22.

Keycode for Fn+F12 is:

~ $ sudo /lib/udev/keymap -i input/event4
Press ESC to finish, or Control-C if this device is not your primary keyboard
scan code: 0x0B key code: suspend

while Fn+F4 is:

scan code: 0x03 key code: sleep

Re-testing on 13.10 initially I found that nothing changed however I revisited this bug and followed the suggestion in #22.

Using dconf-editor I checked "org.gnome.gnome-settings-daemon.plugin.power" key and found "button-suspend: suspend" so I changed it to "button-suspend: hibernate" and my Fn+F1 button now works properly again!

Note in 13.10 `/lib/udev/keymap` is no longer available and you will need to install and run `evtest`

I can confirm this on 15.04 and T420. Initially both sleep and hibernate buttons sent computer to sleep. Changing suspend value in org.gnome.settings-daemon.plugins.power did not change anything. Changing sleep value to hibernate made both buttons to send to hibernate.
Evtest shows that sleep button is sleep, and hibernate button is suspend.