Won't auto-start, have to manually start for each device on every login
Please install the newest version from source to see if the problem has already been solved.
System Information and logs
-
input-remapper-control --version - which linux distro (ubuntu 20.04, manjaro, etc.)
- which desktop environment (gnome, plasma, xfce4, etc.)
-
sudo ls -l /proc/1/exeto check if you are using systemd -
cat ~/.config/input-remapper-2/config.jsonto see if the "autoload" config is written correctly -
systemctl status input-remapper -n 50the service has to be running
Testing 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? - (while the previous command is still running)
sudo evtestand 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 autoload
Adding onto this, I'm having the same issue of Input Remapper not starting the daemon on boot.
- Distro: Nobara (based on Fedora 39).
- Desktop environment: KDE Plasma 6.0.4, using Wayland
- Using systemd.
- The autoload:
hewux@Room-TV-PC:~$ cat ~/.config/input-remapper-2/config.json
{
"version": "2.0.1",
"autoload": {
"ELECOM TrackBall Mouse DEFT Pro TrackBall": "BTN_LEFT on EXTRA"
}
}
- The service:
hewux@Room-TV-PC:~$ systemctl status input-remapper -n 50
â—‹ input-remapper.service - Service to inject keycodes without the GUI application
Loaded: loaded (/usr/lib/systemd/system/input-remapper.service; disabled; preset: disabled)
Drop-In: /usr/lib/systemd/system/service.d
└─10-timeout-abort.conf
Active: inactive (dead)
Workaround:
Running sudo systemctl enable input-remapper
For me, it output the following:
hewux@Room-TV-PC:~$ sudo systemctl enable input-remapper
Created symlink /etc/systemd/system/default.target.wants/input-remapper.service → /usr/lib/systemd/system/input-remapper.service.
After rebooting, Input Remapper was working correctly.
Additional info
I tested installing Input Remapper on a different computer running Fedora 39 with X11 instead of Wayland. It works fine there.
I'm also on Nobara (Gnome edition, though) and for me, despite systemctl, after the latest update my bluetooth stops being remapped every time I wake my laptop from sleep...
I think the cause of this is using the manual install instead of the package manager. I don't think I had a problem with this using Fedora instructions, but with the manual install it doesn't start properly.
For clarification, I used the package manager for both Nobara and Fedora installs. Potentially the bug lies with Nobara's method of installing the package, despite it using Fedora's repository.