[Wayland-bugs] [Bug 93474] libinput doesn't work with keyboard function exposed by anker 8200 laser mouse

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Tue Dec 22 03:02:22 PST 2015


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

            Bug ID: 93474
           Summary: libinput doesn't work with keyboard function exposed
                    by anker 8200 laser mouse
           Product: Wayland
           Version: unspecified
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: libinput
          Assignee: wayland-bugs at lists.freedesktop.org
          Reporter: wengxt at gmail.com

Mouse product link: http://www.anker.com/product/98ANDS2368-BA
lsusb output: Bus 001 Device 004: ID 04d9:fa50 Holtek Semiconductor, Inc. 

This mouse is programmable and can bind some mouse button as a keyboard key. It
used to work without problem with xf86-input-evdev, but keyboard simulation
fails to work with xf86-input-libinput, only pointer and mouse button works.

Also tried it with wayland, it still fails to work under wayland.

After inspect xorg.0.log, there's some error log with "Failed to create a
device for /dev/input/event...". libinput-debug-events --device also failes to
initialize the device.

When using xf86-input-evdev, xinput list shows it as:
⎡ Virtual core pointer                          id=2    [master pointer  (3)]
⎜   ↳ USB Laser Game Mouse                      id=9    [slave  pointer  (2)]
⎜   ↳ USB Laser Game Mouse                      id=11   [slave  pointer  (2)]
⎣ Virtual core keyboard                         id=3    [master keyboard (2)]
    ↳ USB Laser Game Mouse                      id=10   [slave  keyboard (3)]

The problematic device for libinput is the one with id 11. Id 11 device is
captured by 'MatchIsKeyboard "true"' rule, but considered as pointer by
xf86-input-evdev. But it actually sends key event as shown by "xinput test-xi2
11". "xinput test-xi2" 10 shows that id=10 device doesn't do anything. Maybe
that's why it fails to work with libinput.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/wayland-bugs/attachments/20151222/8561ce49/attachment.html>


More information about the wayland-bugs mailing list