Permission Denied on VirtualDeviceBuilder::new().unwrap()

[agoodshort]

Description

When starting makima I receive the following error message:

    Finished dev [unoptimized + debuginfo] target(s) in 0.04s
     Running `target/debug/makima`
Parsing config file:
"/home/abiencourt/.config/makima/Keychron Keychron Q10.toml"

Running on sway, active window detection enabled.
thread 'tokio-runtime-worker' panicked at src/udev_monitor.rs:131:52:
called `Result::unwrap()` on an `Err` value: Os { code: 13, kind: PermissionDenied, message: "Permission denied" }
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Steps to reproduce

1. Create config file .config/makima/Keychron Keychron Q10.toml
2. Run sudo usermod -aG input <username>
3. Logout / login
4. Clone the repo
5. cargo run

Troubleshooting steps so far

• groups

  network power docker rfkill video lp input wheel abiencourt

• ls -l /dev/input

  total 0
  drwxr-xr-x 2 root root     340 Jan  3 21:34 by-id
  drwxr-xr-x 2 root root     820 Jan  3 21:34 by-path
  crw-rw---- 1 root input 13, 64 Jan  3 21:34 event0
  crw-rw---- 1 root input 13, 65 Jan  3 21:34 event1
  crw-rw---- 1 root input 13, 74 Jan  3 21:34 event10
  crw-rw---- 1 root input 13, 75 Jan  3 21:34 event11
  crw-rw---- 1 root input 13, 76 Jan  3 21:34 event12
  crw-rw---- 1 root input 13, 77 Jan  3 21:34 event13
  crw-rw---- 1 root input 13, 78 Jan  3 21:34 event14
  crw-rw---- 1 root input 13, 79 Jan  3 21:34 event15
  crw-rw---- 1 root input 13, 80 Jan  3 21:34 event16
  crw-rw---- 1 root input 13, 81 Jan  3 21:34 event17
  crw-rw---- 1 root input 13, 82 Jan  3 21:34 event18
  crw-rw---- 1 root input 13, 83 Jan  3 21:34 event19
  crw-rw---- 1 root input 13, 66 Jan  3 21:34 event2
  crw-rw---- 1 root input 13, 84 Jan  3 21:34 event20
  crw-rw---- 1 root input 13, 85 Jan  3 21:34 event21
  crw-rw---- 1 root input 13, 86 Jan  3 21:34 event22
  crw-rw---- 1 root input 13, 87 Jan  3 21:34 event23
  crw-rw---- 1 root input 13, 88 Jan  3 21:34 event24
  crw-rw---- 1 root input 13, 89 Jan  3 21:34 event25
  crw-rw---- 1 root input 13, 90 Jan  3 21:34 event26
  crw-rw---- 1 root input 13, 91 Jan  3 21:34 event27
  crw-rw---- 1 root input 13, 92 Jan  3 21:34 event28
  crw-rw---- 1 root input 13, 93 Jan  3 21:34 event29
  crw-rw---- 1 root input 13, 67 Jan  3 21:34 event3
  crw-rw---- 1 root input 13, 94 Jan  3 21:34 event30
  crw-rw---- 1 root input 13, 95 Jan  3 21:35 event31
  crw-rw---- 1 root input 13, 68 Jan  3 21:34 event4
  crw-rw---- 1 root input 13, 69 Jan  3 21:34 event5
  crw-rw---- 1 root input 13, 70 Jan  3 21:34 event6
  crw-rw---- 1 root input 13, 71 Jan  3 21:34 event7
  crw-rw---- 1 root input 13, 72 Jan  3 21:34 event8
  crw-rw---- 1 root input 13, 73 Jan  3 21:34 event9
  crw-rw---- 1 root input 13, 63 Jan  3 21:34 mice
  crw-rw---- 1 root input 13, 32 Jan  3 21:34 mouse0
  crw-rw---- 1 root input 13, 33 Jan  3 21:34 mouse1
  crw-rw---- 1 root input 13, 34 Jan  3 21:34 mouse2
  crw-rw---- 1 root input 13, 35 Jan  3 21:34 mouse3
  crw-rw---- 1 root input 13, 36 Jan  3 21:34 mouse4
  crw-rw---- 1 root input 13, 37 Jan  3 21:34 mouse5

• evtest

  No device specified, trying to scan all of /dev/input/event*
  Not running as root, no devices may be available.
  Available devices:
  /dev/input/event0:      Lid Switch
  /dev/input/event1:      Power Button
  /dev/input/event10:     Contour Design RollerMouse PRO2 Keyboard
  /dev/input/event11:     Keychron Keychron Q10
  /dev/input/event12:     Keychron Keychron Q10 Mouse
  /dev/input/event13:     Keychron Keychron Q10 System Control
  /dev/input/event14:     Keychron Keychron Q10 Consumer Control
  /dev/input/event15:     Keychron Keychron Q10 Keyboard
  /dev/input/event16:     Intel HID events
  /dev/input/event17:     Intel HID 5 button array
  /dev/input/event18:     PC Speaker
  /dev/input/event19:     Dell WMI hotkeys
  /dev/input/event2:      Sleep Button
  /dev/input/event20:     Integrated_Webcam_HD: Integrate
  /dev/input/event21:     HD Pro Webcam C920
  /dev/input/event22:     DELL0919:00 0488:121F Mouse
  /dev/input/event23:     DELL0919:00 0488:121F Touchpad
  /dev/input/event24:     DELL0919:00 0488:121F UNKNOWN
  /dev/input/event25:     PS/2 Generic Mouse
  /dev/input/event26:     Video Bus
  /dev/input/event27:     HDA Intel PCH Headphone Mic
  /dev/input/event28:     HDA Intel PCH HDMI/DP,pcm=3
  /dev/input/event29:     HDA Intel PCH HDMI/DP,pcm=7
  /dev/input/event3:      AT Translated Set 2 keyboard
  /dev/input/event30:     HDA Intel PCH HDMI/DP,pcm=8
  /dev/input/event31:     DP-3
  /dev/input/event4:      Telink Wireless Receiver Mouse
  /dev/input/event5:      Telink Wireless Receiver Consumer Control
  /dev/input/event6:      Telink Wireless Receiver System Control
  /dev/input/event7:      Telink Wireless Receiver
  /dev/input/event8:      CalDigit, Inc. CalDigit Thunderbolt 3 Audio
  /dev/input/event9:      Contour Design RollerMouse PRO2 Mouse
  Select the device event number [0-31]:

[cyber-sushi]

When a new instance of VirtualDeviceBuilder is created, it first makes sure that you have both read and write permissions on /dev/uinput, can you check if you have those?

It could also be possible that the uinput kernel module isn't loaded, what if you use sudo modprobe uinput and then try running Makima again?

[agoodshort]

Thanks so much for the quick response.

sudo modprobe uinput does the trick. I'm fairly new to kernel stuff, I guess I have some reading to do on these topics :laughing:

Is there anything that could be done on the app to avoid this or should I just load uinput on my own?

[cyber-sushi]

Makima can't load kernel modules since it doesn't have sudo privileges, but if you want you can automatically load uinput on boot.

Create /etc/modules-load.d/uinput.conf and inside that file just write uinput, then save and reboot.

Let me know if this works; if it does, I'll add it to the docs tomorrow.

[agoodshort]

So I did a bit more testing:

1. I did not update my modules-load.d and simply rebooted my machine
2. lsmod | grep uiput returns nothing
3. Start makima
4. lsmod | grep uinput shows that the module is now loaded

I'm not sure what happened earlier, but it looks like everything works as expected now. Maybe sudo usermod -aG input <username> requires a reboot instead of a logout / login. I could try to investigate a bit and reproduce if you want me to, but otherwise I'd leave this issue as a one-off and close.

[cyber-sushi]

I don't think usermod -aG input <username> needs a reboot because you were able to use evtest which requires you to be in the input group to work, but maybe loading uinput requires a reboot? In any case, I'm adding it to the docs, it could be useful to other users

And thank you a lot for your cooperation!