-
Notifications
You must be signed in to change notification settings - Fork 304
Open
Labels
Description
Describe the bug
When trying to start plover while keyd is running, it is unable to connect to the keyboard as an input.
To Reproduce
Steps to reproduce the behavior:
Environment: Fedora 43 Sway, fcitx5, keyd
Expected behavior
The app works
Operating system
- OS: Fedora 43 Sway
- Plover Version 5.1.0
Hardware
Laptop with wacky keyboard that if I don't have keyd then it is completely unusable.
Logs
2026-01-10 18:51:54,086 [Dummy-1] ERROR: engine start failed
Traceback (most recent call last):
File "/home/runner/work/plover/plover/build/appimage/plover.AppDir/usr/lib/python3.13/site-packages/plover/engine.py", line 151, in run
File "/home/runner/work/plover/plover/build/appimage/plover.AppDir/usr/lib/python3.13/site-packages/plover/engine.py", line 171, in _start
File "/home/runner/work/plover/plover/build/appimage/plover.AppDir/usr/lib/python3.13/site-packages/plover/engine.py", line 264, in _update
File "/home/runner/work/plover/plover/build/appimage/plover.AppDir/usr/lib/python3.13/site-packages/plover/machine/keyboard.py", line 94, in start_capture
File "/home/runner/work/plover/plover/build/appimage/plover.AppDir/usr/lib/python3.13/site-packages/plover/oslayer/linux/keyboardcontrol_uinput.py", line 505, in start
File "/home/runner/work/plover/plover/build/appimage/plover.AppDir/usr/lib/python3.13/site-packages/plover/oslayer/linux/keyboardcontrol_uinput.py", line 490, in _grab_devices
File "/home/runner/work/plover/plover/build/appimage/plover.AppDir/usr/lib/python3.13/site-packages/evdev/device.py", line 318, in grab
OSError: [Errno 16] Device or resource busy
Reactions are currently unavailable