[keymap] "rfkill button" does nothing on Samsung NP53U3C with Ubuntu raring

[Karolis Labrencis]

I'm using Samsung NP53U3C AMD-based ultrabook and the wireless/bluetooth kill button (Fn+F12) does nothing. After some research I came to a conclusion that there is a problem in udev, which does not know about such key press (as seen in dmesg). The dmesg error shown below.

Steps to reproduce:
Press Fn+F12

Expected result:
Wireless and bluetooth turns on or off

Actual result:
This line in dmesg:
[65983.993398] atkbd serio0: Unknown key pressed (translated set 2, code 0xd5 on isa0060/serio0).

Exact laptop model: SAMSUNG ELECTRONICS CO., LTD. 535U3C

[Martin Pitt (pitti)]

I pushed the fix upstream: http://cgit.freedesktop.org/systemd/systemd/commit/?id=64b2a4

[Launchpad Janitor (janitor)]

This bug was fixed in the package systemd - 204-0ubuntu10

---------------
systemd (204-0ubuntu10) saucy; urgency=low

  * debian/systemd-services.install: Install systemd-multi-seat-x
    (LP: #1214146)
  * debian/local/78-graphics-card.rules: Also recognize vmwgfx driver. Thanks
    Reagan Sanders! (LP: #1208024)
  * Add 0000-upstream-hwdb-updates.patch: Update to latest upstream fixes of
    hwdb, to get proper keyboard support.
  * Move to hwdb keymap database to be able to continue to sync to upstream,
    and benefit from the improved speed and eased maintenance:
    - Drop 0000-upstream-keymaps.patch.
    - Add 0000-upstream-hwdb-keyboard.patch to backport the "keymap" builtin.
    - Add debian/extra/60-keyboard.hwdb (straight copy from upstream master),
      install in debian/udev.install.
    - debian/rules: Configure with --disable-keymap to not build/install the
      old keymap stuff any more.
    - Adds keymap for Samsung NP53U3C (LP: #1203853)
 -- Martin Pitt <email address hidden> Tue, 27 Aug 2013 13:09:08 +0200