ight place. It turns out I wasn't: you're absolutely right
about this being a 'libinput' issue.
All I had to do was issue "downgrade libinput" and choose v1.8.3.
After relaunching X, the problem went away.
I will inform the 'libinput' crew about all of this sh
o the code have been made in the last few months; maybe one
of them is responsible for the problem I'm having.
Have I supplied enough information in this report? If not, let me
know what else you need. I'm also happy to run some further tests if
desired. BTW, I'm currently using v4
