Closed 1player closed 7 months ago
Hi, thanks for reporting.
I cannot see anything uncommon in your evtest
output.
Did another keyboard work as expected on your machine?
Could you start sudo keymapperd -v
in one and keymapper -v
in another terminal and copy the output here, thanks!
Works, the issue was due to my weird setup.
I run Fedora Silverblue and keymapper is installed and running in a privileged Arch Linux distrobox container. When I run keymapperd -v
, the only visible device event file is the one for my mouse. If I run sudo keymapperd -v
, all device event files are accessible, and works as intended.
When checking the permissions of /dev/input/event*
on my machine, since the container is a different distro than the host, the gid for the group input doesn't map exactly, so the unprivileged keymapperd cannot open the event files for all my hardware.
As a possible improvement, it would be nice if keymapperd would print out a notice if the /dev/input/event files can't be read because of permission problems.
Testing with this configuration
evtest shows four devices for this keyboard:
Keyboard data is emitted through the
event2
device, sample output: