[keymap] hwdb keymaps don't support numeric keycodes

Your UdevDb.txt shows that you did the hwdb mangling successfully, i. e. your input/event12 has "E: KEYBOARD_KEY_700E3=middle". However, "middle" will definitively not work, as udev only knows about "KEY_*" constants, not "BTN_* constants" (admittedly this is the first time I head that someone remaps buttons).

I assume in Ubuntu 13.04 and earlier you had an udev rule which assigned the key code (274) directly, not the key name? Please confirm this.

So I suppose what broke is that you are not able to directly specify a key code any more, only a name?

It might be best if you could just copy&paste the old udev rule which called "keymap"? The code there wasn't really different, so I wonder how using a key code worked back then.

Ok, first of all, the keymap which I had stored in /lib/udev/keymaps in a
file named logitech-t400 is like follows:

0x700E3 0x112

And here is my old udev rule which used the keymap program:

ACTION=="remove", GOTO="mouse_end"
KERNEL!="event*", GOTO="mouse_end"
ENV{ID_INPUT_KEY}=="", GOTO="mouse_end"
SUBSYSTEMS=="bluetooth", GOTO="mouse_end"

SUBSYSTEMS=="usb", IMPORT{builtin}="usb_id"
SUBSYSTEMS=="usb", GOTO="mouse_usbcheck"

LABEL="mouse_usbcheck"

SUBSYSTEM=="input", ENV{ID_VENDOR}=="Logitech*", ATTRS{name}=="Logitech
Unifying Device*", RUN+="keymap $name logitech-t400"

LABEL="mouse_end"

LABEL="mouse_modulecheck"

2013/11/4 Martin Pitt <email address hidden>

> It might be best if you could just copy&paste the old udev rule which
> called "keymap"? The code there wasn't really different, so I wonder how
> using a key code worked back then.
>
> ** Changed in: systemd (Ubuntu)
> Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1247584
>
> Title:
> [keymap] Since upgrade to Ubuntu 13.10, udev doesn't map middle mouse
> button.
>
> Status in “systemd” package in Ubuntu:
> Incomplete
>
> Bug description:
> On Ubuntu 13.04 I had the middle mouse button of my Logitech T400
> mapped correctly, but after upgrading to 13.10 the /lib/udev/kemap
> utility has disappeared and now I can no longer assign the middle
> button to the middle button function. This mouse has assigned by
> default the middle button to the left_meta keyboard key (super key).
> That's very annoying because I can't do middle clicking with this
> mouse. This mouse has two middle buttons, in the trackpad that serves
> as middle wheel, but the button that currently serves as middle click
> it's in a very uncomfortable position, and the button with the
> left_meta functionality is the one I'd like to use as middle button.
>
> I tried modifying the file at /lib/udev/hwdb.d/60-keyboard.hwdb with
> this rule:
>
> keyboard:usb:v046DpC52B*
> KEYBOARD_KEY_700E3=middle
>
> and also with
>
> keyboard:usb:v046DpC52B*
> KEYBOARD_KEY_700E3=274
>
> evtest returns the following results and codes:
>
> BUTTON I WANT TO ASSIGN:
> Event: time 1383485540.705610, type 4 (EV_MSC), code 4 (MSC_SCAN), value
> 700e3
> Event: time 1383485540.705610, type 1 (EV_KEY), code 125 (KEY_LEFTMETA),
> value 1
> Event: time 1383485540.705610, -------------- SYN_REPORT ------------
> Event: time 1383485540.809618, type 4 (EV_MSC), code 4 (MSC_SCAN), value
> 700e3
> Event: time 1383485540.809618, type 1 (EV_KEY), code 125 (KEY_LEFTMETA),
> value 0
> Event: time 1383485540.809618, -------------- SYN_REPORT ------------
>
> THE BUTTON IN UNCOMFORTABLE POSITION
> Event: time 1383485765.956075, type 4 (EV_MSC), code 4 (MSC_SCAN), value
> 90003
> Event: time 1383485765.956075, type 1 (EV_KEY), code 274 (BTN_MIDDLE),
> value 1
> Event: time 1383485765.956075, -------------- SYN_REPORT ------------
> Event: time 1383485766.173978, type 4 (EV_MSC), code 4 (MSC_SCAN), value
> 90003
> Event: time 1383485766.173978, type 1 (EV_KEY), code 274 (BTN...

I'm not sure if this is the same issue, but my middle click also stopped working after 13.10 upgrade.
I'm using Lenovo X1 Carbon and it has a hardware middle mouse button. Here's the xev output when I press that button:

KeymapNotify event, serial 37, synthetic NO, window 0x0,
    keys: 4294967198 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
           0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

ButtonPress event, serial 37, synthetic NO, window 0x5c00001,
    root 0x9e, subw 0x0, time 4160630, (19,6), root:(127,1108),
    state 0x0, button 2, same_screen YES

ButtonRelease event, serial 37, synthetic NO, window 0x5c00001,
    root 0x9e, subw 0x0, time 4160630, (19,6), root:(127,1108),
    state 0x200, button 2, same_screen YES

So it gets recognized as "button 2" but for some reason the middle click action never happens.
However if I connect a USB mouse with a scroll wheel, the middle click action works. Here's xev output for USB mouse middle click:

KeymapNotify event, serial 37, synthetic NO, window 0x0,
    keys: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
           0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

ButtonPress event, serial 37, synthetic NO, window 0x5c00001,
    root 0x9e, subw 0x0, time 4248704, (146,11), root:(254,1113),
    state 0x0, button 2, same_screen YES

ButtonRelease event, serial 37, synthetic NO, window 0x5c00001,
    root 0x9e, subw 0x0, time 4248959, (146,11), root:(254,1113),
    state 0x200, button 2, same_screen YES

The only difference that I see is the weird value in the KeymapNotify event but it doesn't make any sense to me. Somebody please help, I'm so used to my middle button!

Ok this is weird, but now that I have posted this comment and checked again it works. It may be a specific program blocking intercepting the key. I'll write back if the issue persists for me.

> Ok, first of all, the keymap which I had stored in /lib/udev/keymaps in a file named logitech-t400 is like follows:
> 0x700E3 0x112

Right. So what happens if you do the same in the hwdb file, i. e.

keyboard:usb:v046DpC52B*
 KEYBOARD_KEY_700E3=274

Do you see the numeric value in "udevadm info --export-db" then?

[Expired for systemd (Ubuntu) because there has been no activity for 60 days.]

I have the exact same issue while running 14.04 with the Logitech Zone Touch T400 mouse.

I can remap the button using udev to another key but udev won't remap to the middle button.

$ sudo udevadm --debug test-builtin keyboard /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.2/0003:046D:C52B.0030/input/input41/event6
calling: test-builtin
=== trie on-disk ===
tool version: 204
file size: 5771951 bytes
header size 80 bytes
strings 1271231 bytes
nodes 4500640 bytes
load module index
device 0xa8b860 has devpath '/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.2/0003:046D:C52B.0030/input/input41/event6'
device 0xa8b860 filled with db file data
Error, unknown key identifier 'middle'
keyboard: mapping scan code 786616 (0xc00b8) to key code 161 (0xa1)
keyboard: mapping scan code 786819 (0xc0183) to key code 226 (0xe2)
keyboard: mapping scan code 786820 (0xc0184) to key code 421 (0x1a5)
keyboard: mapping scan code 786822 (0xc0186) to key code 423 (0x1a7)
keyboard: mapping scan code 786826 (0xc018a) to key code 155 (0x9b)
keyboard: mapping scan code 786830 (0xc018e) to key code 397 (0x18d)
keyboard: mapping scan code 786870 (0xc01b6) to key code 212 (0xd4)
keyboard: mapping scan code 786876 (0xc01bc) to key code 430 (0x1ae)
keyboard: mapping scan code 786977 (0xc0221) to key code 217 (0xd9)
keyboard: mapping scan code 786979 (0xc0223) to key code 172 (0xac)
keyboard: mapping scan code 786989 (0xc022d) to key code 418 (0x1a2)
keyboard: mapping scan code 786990 (0xc022e) to key code 419 (0x1a3)

Notice the line "Error, unknown key identifier 'middle'", I get the same error no matter if I use "middle", "274" or "0x112" (as suggested above by Martin)

This is a regression from the older udev (which used keymaps), which allowed specifying numeric values for the mappings.

I posted here in order not to lose context but I see that the last activity in the bug is from 2013 so if I should open a new bug let me know.

Thanks!

I've written a small patch to allow specifying key codes as numeric values (decimal, octal and hex). I'm attachind the debdiff.

Unsubscribing sponsors, I'd like to handle this via upstream and the Debian packaging git.

I fixed this upstream in http://cgit.freedesktop.org/systemd/systemd/commit/?id=7925709c9, loosely based on Mircea's patch. Thanks!

This bug was fixed in the package systemd - 208-8ubuntu2

---------------
systemd (208-8ubuntu2) utopic; urgency=medium

  [ Ben Howard ]
  * 75-persistent-net-generator.rules: Fix matches of HyperV. (LP: #1361272)

  [ Martin Pitt ]
  * Add new autopkgtest boot_and_services which reboots the testbed with
    systemd as init and verifies that the most critical services like lightdm,
    D-BUS, NetworkManager, and cron work. (To be extended in the future)
  * Fix udev path in udev(7). (LP: #1357782)
  * path_id: suppress ID_PATH for devices with an unknown parent device type.
    (LP: #1321816)
  * udev-builtin-keyboard: Allow numeric key codes. (LP: #1247584)
 -- Martin Pitt <email address hidden> Mon, 08 Sep 2014 14:44:35 +0200