#10851: libinput-1.11.0
-------------------------+-----------------------
Reporter: bdubbs | Owner: ken@…
Type: enhancement | Status: assigned
Priority: normal | Milestone: 8.3
Component: BOOK | Version: SVN
Severity: normal | Resolution:
Keywords: |
-------------------------+-----------------------
Comment (by ken@…):
Not convinced.
On a build from 20180531 on another machine, I used 1.10.7. From time to
time (sometimes when machine seemed to be idle, other times when it was
flat-out compiling) keyboard input would disappear (type a word or two,
some letters eventually appears, but not all of them; tab to a different
window and nothing happened although the mouse seemed to work) and at
other times no visible result would suddenly turn into a *lot* of repeated
characters - either spaces, or one letter.
Using 1.11.0 I've now seen similar issues on the current (2018-06-15)
build.
Most of the time, both systems work ok.
I see intermittent similar reports for libinput over the years (some of
them on Wayland), but no guidance of where the problem might lie. One
(Wayland) report got a suggestion from PH to run /usr/libexec/libinput
/libinput-debug-events to see if that reported missed events. But that
needs to be left running and every keypress/release or mouse movement is
reported in normal use - so it would have to be open, and visible, on the
current desktop at the time the problem occurred.
The real trouble is that because it is mostly ok, it becomes very hard to
determine if a particular release is ok, let alone to try bisecting.
--
Ticket URL: <http://wiki.linuxfromscratch.org/blfs/ticket/10851#comment:2>
BLFS Trac <http://wiki.linuxfromscratch.org/blfs>
Beyond Linux From Scratch
--
http://lists.linuxfromscratch.org/listinfo/blfs-book
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
