logiops
logiops copied to clipboard
PixlOne
logid stops working after mouse is idle for a while
Hi, I use logid for an MX Master 3 connected over bluetooth mostly to make the thumb button a real mouse button. This works nicely (thanks!!), however, logid stops working when the mouse is idle for a while (somewhere between 5 minutes and half an hour). The output of logid gives no indication and the logid process keeps running. I see
cert ~ 8> sudo logid -v -c ~/.logid.cfg
[DEBUG] Unsupported device /dev/hidraw0 ignored
[DEBUG] Unsupported device /dev/hidraw1 ignored
[INFO] Device found: Wireless Mouse MX Master 3 on /dev/hidraw2:255
[DEBUG] /dev/hidraw2:255 remappable buttons:
[DEBUG] CID | reprog? | fn key? | mouse key? | gesture support?
[DEBUG] 0x50 | | | YES |
[DEBUG] 0x51 | | | YES |
[DEBUG] 0x52 | YES | | YES | YES
[DEBUG] 0x53 | YES | | YES | YES
[DEBUG] 0x56 | YES | | YES | YES
[DEBUG] 0xc3 | YES | | YES | YES
[DEBUG] 0xc4 | YES | | YES | YES
[DEBUG] 0xd7 | YES | | | YES
[DEBUG] Thumb wheel detected (0x2150), capabilities:
[DEBUG] timestamp | touch | proximity | single tap
[DEBUG] YES | YES | YES | YES
[DEBUG] Thumb wheel resolution: native (18), diverted (120)
where the thumb wheel line directly appears after starting and then there is no more output.
Restarting logid fixes the problem (until the next longer idle time) and meanwhile I have a window manager shortcut for that. Nevertheless it is a nuisance when the favorite mouse button stoped working after returning from the whiteboard.
I would appreciate any hints about how to fix or debug this problem. Thanks!
I see somethinmg similar where my mouse wheel acceleration turns off after my desktop idles. It sounds similar to this issue someone reported on reddit a year ago (not using logiops): https://www.reddit.com/r/kde/comments/bk6u5z/scroll_button_speed_slow_after_wake_up_from_sleep/
I would love a fix for this because it is absolutely infuriating. I am not sure where the fault lies, however.
I don't see the problem anymore and I have not changed anything in logiops or its configuration. But I regularly updated my system. This seems to indicate that there was either a bug in the system or a communication problem with logiops that is not triggered any more.
That is the case for me, yes, though I haven't tested thoroughly with the unify receiver.
pixl [email protected] writes:
Does this only happen when you connect your mouse over Bluetooth?
Yes, I connect my mouse over bluetooth. I have not tested with a different connection. So it happens with bluetooth, but I cannot tell whether it only happens with bluetooth.
Hendrik
As I wrote on Sept 30, the issue went away, apparently without changing logiops. @mankyd: Can you still reproduce? Otherwise I suggest to close this.
Add /lib/systemd/system-sleep/logid.sh with content:
#!/bin/sh
systemctl restart logid
It will restart logid.service on WakeUp, so driver will work after idle and resuming from suspend
