--- Comment #5 from Peter Hutterer <peter.hutte...@who-t.net> ---
in libinput, touchpads and mice are completely separate so please let's not mix
the two issues. If it is a libinput bug, it cannot be the same because there's
virtually no overlapping code.
The debug log here shows that the button state is correct, you get a press
followed by a release event, the seat count is correct too. So if that
triggered a stuck button, the issue is in the compositor or on the client side.
But either way, this needs a separate bug report please.
You are receiving this mail because:
You are the assignee for the bug.
wayland-bugs mailing list