[Wayland-bugs] [Bug 104415] My wireless all-in-one (keyboard/mouse) requires a triple-tap to highlight a word

[bugzilla-daemon at freedesktop.org]

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

            Bug ID: 104415
           Summary: My wireless all-in-one (keyboard/mouse) requires a
                    triple-tap to highlight a word
           Product: Wayland
           Version: unspecified
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: minor
          Priority: medium
         Component: libinput
          Assignee: wayland-bugs at lists.freedesktop.org
          Reporter: xavion.0 at gmail.com

For the last several weeks, my Microsoft (wireless) All-in-One Media Keyboard
has required a triple-tap on the trackpad to highlight a single word of text. 
It only used to need a double-tap (as you'd expect), so I know this is a fairly
recent bug.

It has nothing to do with my desktop environment (KDE), as the problem
occurs in LXDE too.  Both run on X, BTW: I don't use Wayland yet.  I have
obviously tested it using different applications (i.e. not just my web browser)
as well.

It's important to note that it only happens with tapping (i.e. not
clicking).  If I double-click on the same part of the trackpad, the
word is highlighted as expected.  However, if I instead double-tap,
nothing happens.

The relevant output from the "usb-devices" command is as follows:
    T:  Bus=02 Lev=01 Prnt=01 Port=11 Cnt=01 Dev#=  5 Spd=12  MxCh= 0
    D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
    P:  Vendor=045e ProdID=0800 Rev=09.34
    S:  Manufacturer=Microsoft
    S:  Product=Microsoft® Nano Transceiver v2.0
    C:  #Ifs= 3 Cfg#= 1 Atr=a0 MxPwr=100mA
    I:  If#=0x0 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=01 Prot=01 Driver=usbhid
    I:  If#=0x1 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=01 Prot=02 Driver=usbhid
    I:  If#=0x2 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=00 Prot=00 Driver=usbhid

I originally reported this bug to the 'linux-usb' mailing list.  They suggested
it might instead be a 'libinput' problem, which it is.  After issuing
"downgrade libinput" (on Arch Linux), choosing v1.8.3, and relaunching X, the
problem went away.

Jumping (back) up to v1.9.1 (or newer) made it reappear.  This means the
offending section of code was incorporated somewhere between those versions. 
Let me know if you need me to narrow it down further.  I'm happy to run more
tests and/or supply additional information.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/wayland-bugs/attachments/20171230/3c2d3ec8/attachment-0001.html>