The udev keymaps are correct. As I said, on the kernel level there is
only KEY_SLEEP (suspend to RAM) and KEY_SUSPEND (suspend to disk, aka
hibernate).
On the X.org level, /usr/share/X11/xkb/keycodes/evdev assigns <I150> to
KEY_SLEEP and <I213> to KEY_SUSPEND. /usr/share/X11/xkb/symbols/inet
then maps <I150> to XF86Sleep and <I213> to XF86Suspend, mirroring the
evdev naming. There is also an entry
key <I255> { [ XF86Hibernate ] }; //
KEY_HIBERNATE
But this isn't defined in /usr/share/X11/xkb/keycodes/evdev. Per the
"evdev code + 8" mapping, this would correspond to KEY_RFKILL and thus
be wrong.
So there are two things which can happen here:
* Change the xkb mapping of <I213> to XF86Hibernate. This seems to be
what KDE expects, and GNOME gets along with it as well (it handles both
XF86Hibernate and XF86Suspend).
* Change KDE to accept XF86Suspend for hibernation as well, in
addition to XF86Hibernate (which is never emitted right now).
** Package changed: systemd (Ubuntu) => xkeyboard-config (Ubuntu)
** Changed in: xkeyboard-config (Ubuntu)
Status: New => Triaged
** Summary changed:
- [keymap] Dell Latitude D830: hibernate key
+ KEY_SUSPEND should mean "hibernate"/XF86Hibernate
** Also affects: kde4libs (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1167869
Title:
KEY_SUSPEND should mean "hibernate"/XF86Hibernate
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kde4libs/+bug/1167869/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
