-
-
Notifications
You must be signed in to change notification settings - Fork 149
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can’t autoload Logitech USB Receiver rules when I insert USB Receiver #857
Comments
Adding a quote of my comment on a possibly related issue as it might help with yours.
|
I got this error after the patch
Sorry, I am very inexperienced Python user |
Yeah, it’s definitely a circular dependency. More confused at how I’m NOT getting an error than how you are. Could go a different path (event passing), but having trouble keeping it simple. The device disconnect event may not be “shared with the team”. Still a total noob to the codebase and asyncio. Will see what I can figure out, but no promises. |
Thanks. Take your time, I report this issue mostly as feedback, I have a workaround (by re-running the app). Your app is amazing and makes my life everyday better (as a dad I often have only one had and can do copy-paste with extra buttons of the mouse). |
I just found that the problem is happening only with USB received switching off. Bluetooth disconnection, etc doesn’t have this issue. |
When I start the system with inserted Logitech USB Receiver loads its rules. But if I eject it and insert again, rules stop working.
The issue can be fixed by running GTK app and load rules manually.
System Information and logs
input-remapper-control --version
Fedora 39
GNOME
sudo ls -l /proc/1/exe
to check if you are using systemdcat ~/.config/input-remapper-2/config.json
to see if the "autoload" config is written correctlysystemctl status input-remapper -n 50
the service has to be runningTesting the setup
input-remapper-control --command hello
sudo pkill -f input-remapper-service && sudo input-remapper-service -d & sleep 2 && input-remapper-control --command autoload
, are your keys mapped now?Yes
sudo evtest
and search for a device suffixed by "mapped". Select it, does it report any events? Share the output.Yes
sudo udevadm control --log-priority=debug && sudo udevadm control --reload-rules && journalctl -f | grep input-remapper
, now plug in the device that should autoloadThe text was updated successfully, but these errors were encountered: