I use dwm on Arch and in my autostart.sh I start KMonad. This requires me to be member in the uinput group (what I am). Since a few days starting KMonad fails with:

kmonad: /dev/uinput: openFd: permission denied (Permission denied)

(Same when I try to start it manually.)

The workaround is to run sudo modprobe uinput and then to start kmonad (again).

I just don’t understand why this is necessary now. I have this udev rule defined:

/etc/udev/rules.d/90-kmonad.rules:

KERNEL=="uinput", MODE="0660", GROUP="uinput", OPTIONS+="static_node=uinput"

I guess this broke because of a sudo pacman -Syu. Has anything changed in the last few days? I can’t find anything that looks related on Arch Linux.

  • Responsabilidade@lemmy.eco.br
    1·
    3 years ago

    Looks like your uinput module isn’t being loaded at boot

    Have you added a file uinput.conf with uinput as its content at /etc/modules-load.d?

    • MaxGyver83@feddit.deOP
      1·
      3 years ago

      I have tried this but the problem persists after a reboot.

      UPDATE: I have tested this again. I forgot to mention that it’s even worse with an /etc/modules-load.d/uinput.conf. After a reboot, I get the same error as before but a sudo modprobe uinput doesn’t help anymore. I have to run sudo modprobe -r uinput; sudo modprobe uinput to fix the openFd: permission denied error (temporarily).

      • Responsabilidade@lemmy.eco.br
        3·
        3 years ago

        Try change your udev rule to

        KERNEL=="uinput", MODE="0660", GROUP="uinput", TAG+="uaccess", OPTIONS+="static_node=uinput"

        Maybe you don’t grant uaccess to your device

        I have an uinput device configured as well and my setup is:

        KERNEL=="uinput", SUBSYSTEM=="misc", TAG+="uaccess", OPTIONS+="static_node=uinput"