openstenoproject
Logitech MX Master mouse is stuck when upgrading Plover from 4 to 5
Describe the bug
When starting Plover using machine keyboard the mouse input freezes and cannot be used (no clicking, scrolling, pointing) unless the keyboard is disconnected physically. Regardless of whether the output in Plover is disabled or enabled.
This happens on Hyprland using the latest 5.0.0 appimage, the rc1 and dev appimage are both also effected. Connecting the mx master mouse via bluetooth or dongle both freeze. Connecting a USB dumb mouse works fine.
To Reproduce
Steps to reproduce the behavior:
- Run plover through command-line.
- Attempt to move mouse and observe it is stuck.
- Unplug keyboard
- Mouse is no longer stuck, plover should error saying keyboard capture error, no such device.
Expected behavior
Mouse should not be stuck.
Screenshots N/A
Operating system
- OS: Linux
- Plover Version 5.0.0
Hardware
Standard USB keyboard, logitech MX master mouse via dongle and bluetooth.
Edit: This issue was recreated on both Hyprland (wayland) and i3 (X11).
Which Plover v4 exactly did you upgrade from? Just to potentially exclude some changes.
Sadly I don't have a computer with Hyprland to test this.
Sorry, I should've specified, it was release 4.0.3. I actually have two machines and just tested this out on my X11 machine and the issue is on both.
I have a Logitech X PRO superlight connected with powerplay mousemat, the mouse freeze only works when keyboard is set as the "Machine", doesnt matter if output is enabled/disabled
