-
-
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
Won't auto-start, have to manually start for each device on every login #879
Comments
Adding onto this, I'm having the same issue of Input Remapper not starting the daemon on boot.
Workaround:Running
After rebooting, Input Remapper was working correctly. Additional infoI tested installing Input Remapper on a different computer running Fedora 39 with X11 instead of Wayland. It works fine there. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Please install the newest version from source to see if the problem has already been solved.
System Information and logs
input-remapper-control --version
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?sudo evtest
and search for a device suffixed by "mapped". Select it, does it report any events? Share the output.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: