logiops icon indicating copy to clipboard operation
logiops copied to clipboard

Drop settings by lost connections

Open meugr opened this issue 4 years ago • 7 comments

Hi there! Debian 10, KDE If I switch my MX Master 3 on/off OR switch Bluetooth on/off, logid doesn't work correctly. My settings are dropped and I need to run forced systemclt restart logid

systemctl status logid MAYBE write me [WARN] Error ignored on detached thread/task: _readReport read failed: Input/output error (like a #180 )

meugr avatar May 03 '21 08:05 meugr

Same on Ubuntu 18.04 and the logid didn't report any WARN or ERROR.

ArtisticZhao avatar Sep 06 '21 06:09 ArtisticZhao

@meugr I had a temporary solution.

Add an udev rules in /etc/udev/rules.d/90-my.rules

# /etc/udev/rules.d/90-my.rules
ACTION=="add", SUBSYSTEM=="bluetooth", RUN{program}="/bin/systemctl  restart logid.service"

and call

> sudo udevadm control --reload

This will restart logid service when a new bluetooth device added. If your mouse use the usb, you can modify "bluetooth" to "usb".

ArtisticZhao avatar Sep 07 '21 02:09 ArtisticZhao

@ArtisticZhao Thanks, nice temporary hack. It's absolutely working for me

meugr avatar Sep 07 '21 08:09 meugr

I have this issue with my MX master 3 mac.. the logid service is only outputing the following log after "Started Logitech Configuration Daemon"

logid[14471]: [WARN] Error ignored on detached thread/task: _readReport read failed: Input/output error

fredsco avatar Feb 15 '22 15:02 fredsco

A bit better solution:

ACTION=="add", SUBSYSTEM=="input", ATTRS{id/vendor}=="046d", RUN{program}="/bin/systemctl restart logid.service"

this will trigger only when a Logitech device is connected. The previously suggested rule will trigger on any Bluetooth device (including non-Logitech ones)

if you want to be more granular you can use ATTRS{id/product}=="b019" (MX Master 2S in this example) or ATTRS{phys}=="00:11:22:33:44:55" to filter by a specific mac address. ATTRS{name}=="MX Master 2S Mouse" is also an option

dumbasPL avatar Feb 18 '22 08:02 dumbasPL

This did not solve my issue...

fredsco avatar Feb 21 '22 18:02 fredsco

A bit better solution:

ACTION=="add", SUBSYSTEM=="input", ATTRS{id/vendor}=="046d", RUN{program}="/bin/systemctl restart logid.service"

this will trigger only when a Logitech device is connected. The previously suggested rule will trigger on any Bluetooth device (including non-Logitech ones)

if you want to be more granular you can use ATTRS{id/product}=="b019" (MX Master 2S in this example) or ATTRS{phys}=="00:11:22:33:44:55" to filter by a specific mac address. ATTRS{name}=="MX Master 2S Mouse" is also an option

That solve the issue for me.

diegodario88 avatar Sep 17 '23 14:09 diegodario88