[systemd-bugs] [Bug 75875] systemd-udevd: Error calling EVIOCSKEYCODE (scan code 0xNNNNN, key code MMM): Invalid argument

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=75875

Martin Pitt <martin.pitt at ubuntu.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |NEEDINFO

--- Comment #5 from Martin Pitt <martin.pitt at ubuntu.com> ---
These were translated from the original udev rules, which were

ENV{ID_VENDOR}=="Logitech*", ATTRS{name}=="Logitech USB Multimedia Keyboard",
RUN+="keymap $name logitech-wave"
ENV{ID_VENDOR}=="Logitech*", ATTRS{name}=="Logitech USB Receiver", RUN+="keymap
$name logitech-wave-cordless"

Since hwdb doesn't support his kind of matches, I used
http://www.linux-usb.org/usb.ids to look up the corresponding product IDs. Both
C317 and C517 exist as keyboards, and Gerardo confirmed that this is a
keyboard/mouse combo. So supposedly this USB device hasa two different
interfaces, and the setkeycode is applied to the wrong one.

Gerardo/David, do all of the special keys (zoom in/out, media, wordprocessor,
calendar, etc.) actually work? (In the sense of opening the corresponding
programs, or at least giving proper keycode names in "evtest")?

Can you please do

  udevadm info --export-db > /tmp/udev.txt

and attach /tmp/udev.txt here? That will give more insight than the lspci dump.

Thanks!

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-bugs/attachments/20140827/712cfd61/attachment.html>