On 6 February 2018 at 05:21, Peter Hutterer
wrote:
> This looks like a libinput bug (well, it does say "libinput bug" on the
> package) but it hasn't been that for a long time. The cause is almost
> always
> insufficient motivation to call libinput_dispatch() by the caller, or at
> least
> not do
This looks like a libinput bug (well, it does say "libinput bug" on the
package) but it hasn't been that for a long time. The cause is almost always
insufficient motivation to call libinput_dispatch() by the caller, or at least
not doing it with the celerity libinput demands (and deserves, if I may
