Bug 93983 - libinput + yubikey = no DWT
Summary: libinput + yubikey = no DWT
Status: RESOLVED FIXED
Alias: None
Product: Wayland
Classification: Unclassified
Component: libinput (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Peter Hutterer
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-02-03 11:46 UTC by Mario
Modified: 2016-02-07 22:57 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
log of a touch during typing with yubikey inserted (31.87 KB, text/plain)
2016-02-03 11:46 UTC, Mario
Details
evemu log (regular typing than a tap) (96.85 KB, text/plain)
2016-02-04 12:04 UTC, Mario
Details
evemu log of keyboard (9.72 KB, text/plain)
2016-02-05 10:08 UTC, Mario
Details

Description Mario 2016-02-03 11:46:09 UTC
Created attachment 121488 [details]
log of a touch during typing with yubikey inserted

I'm using libinput 1.1.5 on Arch Linux with xorg on a Dell XPS 13 9350.
In order to quickly unlock my password manager I always keep a nano YubiKey in one USB slot. It looks to interfere with the DWT mechanism.

In attachment a log produced by 'sudo libinput-debug-events --enable-dwt --verbose' during an experiment where a touch is wrongly allowed during some keyboard activities (holding a key).

$ uname -a
Linux hostname 4.4.0-4 #1 SMP PREEMPT Tue Jan 26 19:59:05 CET 2016 x86_64 GNU/Linux

$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 005: ID 0c45:670c Microdia 
Bus 001 Device 004: ID 04f3:20d0 Elan Microelectronics Corp. 
Bus 001 Device 003: ID 0a5c:6412 Broadcom Corp. 
Bus 001 Device 002: ID 1050:0116 Yubico.com Yubikey NEO(-N) OTP+U2F+CCID
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Comment 1 Peter Hutterer 2016-02-04 01:13:37 UTC
Please attach an evemu describe from your keyboard and the touchpad. Thanks
Comment 2 Mario 2016-02-04 12:04:19 UTC
Created attachment 121517 [details]
evemu log (regular typing than a tap)

I hope this is what you are looking for.
Comment 3 Peter Hutterer 2016-02-04 21:44:21 UTC
thanks, I need the evemu-describe from your keyboard too, just to double-check something. no need for events, just the description is enough.
Comment 4 Peter Hutterer 2016-02-04 23:25:30 UTC
commit 0b0150e08d4e3e88d7a81a7429306d8dca2fe4c8
Author: Peter Hutterer <peter.hutterer@who-t.net>
Date:   Thu Feb 4 11:20:38 2016 +1000

    touchpad: if we have a serio keyboard, override any previous dwt pairing



fwiw, still would like the keyboard description here, thanks.
Comment 5 Mario 2016-02-05 10:08:17 UTC
I can confirm that actual master on the git repository fixed my problem with dwt and yubikey.

On first attempt the DWT is associated with the yubikey, then with the regular keyboard:
....
input device 'DLL0704:01 06CB:76AE Touchpad', /dev/input/event14 is tagged by udev as: Touchpad
thumb: enabled thumb detection on 'DLL0704:01 06CB:76AE Touchpad'
input device 'DLL0704:01 06CB:76AE Touchpad', /dev/input/event14 is a touchpad
palm: dwt activated with DLL0704:01 06CB:76AE Touchpad<->Yubico Yubikey NEO OTP+U2F+CCID
input device 'HDA Intel PCH HDMI/DP,pcm=8', /dev/input/event10 not tagged as input device
failed to create input device '/dev/input/event10'.
input device 'HDA Digital PCBeep', /dev/input/event6 not tagged as input device
failed to create input device '/dev/input/event6'.
input device 'HDA Intel PCH Headphone Mic', /dev/input/event7 not tagged as input device
failed to create input device '/dev/input/event7'.
input device 'HDA Intel PCH HDMI/DP,pcm=3', /dev/input/event8 not tagged as input device
failed to create input device '/dev/input/event8'.
input device 'HDA Intel PCH HDMI/DP,pcm=7', /dev/input/event9 not tagged as input device
failed to create input device '/dev/input/event9'.
input device 'AT Translated Set 2 keyboard', /dev/input/event11 is tagged by udev as: Keyboard
input device 'AT Translated Set 2 keyboard', /dev/input/event11 is a keyboard
palm: dwt activated with DLL0704:01 06CB:76AE Touchpad<->AT Translated Set 2 keyboard
input device 'PC Speaker', /dev/input/event5 not tagged as input device
....

In attachment the log of evemu on the internal keyboard.
Comment 6 Mario 2016-02-05 10:08:48 UTC
Created attachment 121535 [details]
evemu log of keyboard
Comment 7 Peter Hutterer 2016-02-07 22:57:52 UTC
Cool, thanks for testing and the recording. Fwiw, this is part of the 1.1.6 release now too.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.