One successful run with MX Master 3S and following failures

[pkesso]

I got 1 (one) successful run of v0.3.4 with MX Master 3S. Timeout was set to 50000 at that moment, but it doesn't seems to be important - mouse connected less than in 1 second. However, next times I tried to run it with the same config, the only thing I got was:

# time ./logid -v
[DEBUG] Unsupported device /dev/hidraw0 ignored
[DEBUG] Unsupported device /dev/hidraw1 ignored
[INFO] Detected receiver at /dev/hidraw2
[DEBUG] Unsupported device /dev/hidraw3 ignored

real    0m0,257s
user    0m0,007s
sys     0m0,012s

and exit code was 0.
There was no processes running in background, and reboot did not helped. What could it be?

Timeout parameter is also missing in config example btw.

[johnnogaj]

Sorry this is old but I was having a similar issue recently where I was able to get my MX Master 3S to connect and work one time, but anytime I would restart or shutdown and reboot the mouse would not work at all. I could see it connected via bluetooth but the logid service would not show it connected in the log.

Changing the logid.service to the following now works for my setup:

[Unit]
Description=Logitech Configuration Daemon
StartLimitIntervalSec=0
After=bluetooth.target
Wants=multi-user.target

[Service]
Type=simple
ExecStart=/usr/bin/logid
User=root
ExecReload=/bin/kill -HUP $MAINPID
Restart=on-failure

[Install]
WantedBy=graphical.target

The key item that I changed was to set the service to start After=bluetooth.target and this now seems to work well. I am connecting the mouse via bluetooth and not with the unifying receiver however, so this may not be applicable for connecting with a unifying receiver.

Don't forget to systemctl daemon-reload after changing the service file definition and then restart the logid service. I am on Ubuntu 24.04

[pkesso]

@johnnogaj I got a new laptop; with the same, but freshly installed version of fedora and logid it works now.

Thank you for tip, however I don't think it is the same problem, since I dont use nor bluetooth connection, neither systemd. I had a problem using usb dongle (with the green symbol, new type) and manually started logid.