This is fixed in utopic.

** Changed in: systemd (Ubuntu)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1247676

Title:
  [keymap] high scan codes don't work on 32 bit platforms

Status in “systemd” package in Ubuntu:
  Fix Released

Bug description:
  In Ubuntu 12.04 64-bit I used the following udev rules to make
  Plantrinics buttons work:

  **************************************************
  ACTION!="add|change", GOTO="xorg_plantronics_end"
  KERNEL!="event*", GOTO="xorg_plantronics_end"

  ENV{ID_VENDOR_ID}=="047f", ENV{ID_MODEL_ID}=="c013", ENV{ID_INPUT_KEY}="1"
  ENV{ID_VENDOR_ID}=="047f", ENV{ID_MODEL_ID}=="c013", RUN+="keymap $name 
0xFFA000B1 volumeup 0xFFA000B2 volumedown 0xffa000b5 micmute 0xffa000b7 phone 
0xffa000ab unknown"

  LABEL="xorg_plantronics_end"
  **************************************************

  However there is no keymap (systemd ) since Saucy anymore and
  setkeycodes can't map such codes as: 0xFFA000B1, 0xFFA000B2,
  0xffa000b5, 0xffa000b7, and 0xffa000ab

  Debian still has keymap even in sid (unstable). Changelog of systemd
  package in Ubuntu has the following note:

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

  ...
      - debian/rules: Configure with --disable-keymap to not build/install the
        old keymap stuff any more.
  ...
  **************************************************

  So keymap is dropped and there is no equivalent replacement yet.
  Any ideas how to make these buttons work again?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1247676/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to