https://bugs.freedesktop.org/show_bug.cgi?id=106798
Peter Hutterer <peter.hutte...@who-t.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |NEEDINFO
CC| |peter.hutte...@who-t.net
--- Comment #1 from Peter Hutterer <peter.hutte...@who-t.net> ---
fwiw, the X device IDs and the event nodes are not the same. Your device says:
Device Node (268): "/dev/input/event12"
this is one of the reasons why we discourage using device IDs with xinput and
suggest using the device name instead, see
https://who-t.blogspot.com.au/2016/07/xinput-resolves-device-names-and.html
Other than that: I'll need the libinput debug-events --verbose output, this
often prints out enough information to pin-pint where things are going wrong.
dwt related issues are an interaction between the touchpad and the keyboard so
a single event recording usually doesn't tell us quite enough. Hopefully the
debug-events output has more info here.
Also: bugzilla doesn't support markup, please don't use bbcode or markdown or
other styles. Since we can't edit comments here either, it just makes it harder
to read. There is a Preview button above the text area though.
--
You are receiving this mail because:
You are the assignee for the bug._______________________________________________
wayland-bugs mailing list
wayland-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
