waycrate
libinput bug: Event for missing capability CAP_POINTER on device "swhkd virtual output"
Version Information:
- Distribution Information: Linux artix 5.18.10-artix1-1 #1 SMP PREEMPT_DYNAMIC Fri, 08 Jul 2022 07:26:22 +0000 x86_64 GNU/Linux
- swhkd version: swhkd 1.1.7
Describe the bug:
Getting this log when I run sudo libinput debug-events and click my Logitech G502 Lightspeed in wireless mode. The mouse doesn't work at all (except for this click error) when wireless and it works fine when wired. When I stop swhkd the mouse starts working when wireless.
Expected behavior: I'd like to be able to use my mouse in wireless mode.
Actual behavior:
My mouse doesn't work in wireless mode while swhkd is working.
To Reproduce: Difficult to reproduce. You'd probably need that same mouse (or maybe any wireless mouse, I'm not sure).
Additional information: If you point me in the right direction, I will attempt to fix this using my mouse.
Expected behavior: I'd like to be able to use my mouse in wireless mode.
Hi, currently we simply check if a device has enter key and grab the device.
This was initially reported in (this issue.)[https://github.com/waycrate/swhkd/issues/126] I believe you're experiencing the same problem as them.
We currently don't have a reliable keyboard detection algorithm in place but I'm willing to accept one if you send a patch.
The current workaround is to simply use the --device argument as stated in man swhkd
to manually specify the devices you want to be grabbed by swhkd.
I came up with a (concept)[https://github.com/waycrate/swhkd/issues/137] of --add-device or --ignore-device so you don't need to specify the entire list every single time with --device incase you just want 1 or 2 devices gone/added. Maybe you can help out with this if you want?
I hope this answered your question.
Aakash Sen Sharma.
@ivandimitrov8080 Would you be interested in giving this a try again now that we have support for re-emitting events since #163 got merged?
