Logid systemd service doesn't work on boot (Manjaro/Arch)

[Maikuh]

On every boot, the service fails to start, below you can see the log:

Aug 18 17:23:49 mangy systemd[1]: Started Logitech Configuration Daemon.
Aug 18 17:23:51 mangy logid[523]: [WARN] Error adding device /dev/hidraw2: open failed: No such file or directory
Aug 18 17:23:52 mangy logid[523]: [WARN] Error adding device /dev/hidraw1: std::exception
Aug 18 17:23:52 mangy logid[523]: [WARN] Error adding device /dev/hidraw0: Invalid sub ID
Aug 18 17:23:54 mangy logid[523]: [WARN] Error adding device /dev/hidraw1: std::exception
Aug 18 17:23:54 mangy logid[523]: [WARN] Error adding device /dev/hidraw1: std::exception
Aug 18 13:36:11 mangy logid[523]: [ERROR] Caught HID++ 1.0 error while trying to initialize /dev/hidraw0:1: Resource error
Aug 18 13:36:11 mangy logid[523]: [ERROR] Caught HID++ 1.0 error while trying to initialize /dev/hidraw0:1: Resource error
Aug 18 13:38:14 mangy logid[523]: [ERROR] Caught HID++ 1.0 error while trying to initialize /dev/hidraw0:1: Resource error
Aug 18 13:38:41 mangy logid[523]: [ERROR] Caught HID++ 1.0 error while trying to initialize /dev/hidraw0:1: Resource error
Aug 18 13:39:02 mangy logid[523]: [ERROR] Caught HID++ 1.0 error while trying to initialize /dev/hidraw0:1: Resource error
Aug 18 13:39:03 mangy logid[523]: [ERROR] Caught HID++ 1.0 error while trying to initialize /dev/hidraw0:1: Resource error
Aug 18 13:40:38 mangy logid[523]: [ERROR] Caught HID++ 1.0 error while trying to initialize /dev/hidraw0:1: Resource error
Aug 18 14:32:11 mangy systemd[1]: Stopping Logitech Configuration Daemon...
Aug 18 14:32:12 mangy systemd[1]: logid.service: Deactivated successfully.

This only happens on boot, since whenever I restart the service (using sudo systemctl restart logid) or run logid via terminal (like logid -v) it works fine until I reboot again and have to manually restart it.

I'm currently using Manjaro GNOME 21.1.0, but I was using Pop-OS 21.04 until recently and this didn't happen.

[karlitos]

This happens for me as well on the Elementary Os 6, which is basically Ubuntu 20.04 LTS

sudo systemctl status logid.service 
● logid.service - Logitech Configuration Daemon
     Loaded: loaded (/lib/systemd/system/logid.service; enabled; vendor preset: enabled)
     Active: active (running) since Fri 2021-10-22 08:24:09 CEST; 1min 30s ago
   Main PID: 586 (logid)
      Tasks: 7 (limit: 9330)
     Memory: 2.1M
     CGroup: /system.slice/logid.service
             └─586 /usr/local/bin/logid

Okt 22 08:24:09 HPSpectrex360 systemd[1]: Started Logitech Configuration Daemon.
Okt 22 08:24:11 HPSpectrex360 logid[586]: [WARN] Error adding device /dev/hidraw1: std::exception
Okt 22 08:24:14 HPSpectrex360 logid[586]: [WARN] Error adding device /dev/hidraw4: std::exception
Okt 22 08:24:14 HPSpectrex360 logid[586]: [WARN] Error adding device /dev/hidraw2: std::exception
Okt 22 08:24:16 HPSpectrex360 logid[586]: [WARN] Error adding device /dev/hidraw2: std::exception
Okt 22 08:24:17 HPSpectrex360 logid[586]: [WARN] Error adding device /dev/hidraw1: std::exception
Okt 22 08:24:19 HPSpectrex360 logid[586]: [WARN] Error adding device /dev/hidraw3: std::exception
Okt 22 08:24:19 HPSpectrex360 logid[586]: [WARN] Error adding device /dev/hidraw3: std::exception
Okt 22 08:24:21 HPSpectrex360 logid[586]: [WARN] Error adding device /dev/hidraw4: std::exception
Okt 22 08:24:21 HPSpectrex360 logid[586]: [WARN] Error adding device /dev/hidraw0: Invalid sub ID

Restarting the service manually fixes the issue

[avasyub]

This issue seems to be fixed in master (https://github.com/PixlOne/logiops/pull/246), but is not yet released as a version.

Try using logiops-git from AUR or build it from source.

I've been using logiops-git for the past few days and logid starts up just fine on boot. No restarting needed.

[chomosuke]

This issue seems to be fixed in master (#246), but is not yet released as a version.

Try using logiops-git from AUR or build it from source.

I've been using logiops-git for the past few days and logid starts up just fine on boot. No restarting needed.

Hmmm for me restart is still needed every single time I boot. I'm using the latest master commit. I can provide more info if needed.