You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using a Master MX 3S running on OpenSUSE Tumbleweed with Plasma 6 (all latest from Tumbleweed repo's). I've noticed that when booting up, or coming out of hibernation, that if the mouse wasn't moving during the initialization that it doesn't initialize. If I execute a systemctl restart logidwhile moving the mouse it will restart the daemon and everything will work fine. If i rerun systemctl restart logid and do not move the mouse it will go back to the uninitialized state, with one small caveat that the mouse dpi seems to be remembered (buttons revert to pre-logid settings but dpi is retained). I can tell it's not working in the beginning because the mouse is so slow, I have dpi: 3000 which seems to work well for me, but when it's not working it's similar to dpi: 1000 in its movement. I also have the thumb buttons (below the wheel) set to move to next / previous workspace, as opposed to the default (without logiopt installed) of forward / back. So when I log in the mouse is slow, and the buttons are forward / back. If I restart the daemon (or turn the mouse off/on) everything works as expected. But, if I run systemctl restart logid while not moving the mouse the buttons reset to forward / back but the dpi does seem to stick. I'm not sure if any of this is related, but wanted to give the info just in case it helps.
A way to get it to initialize without movement from the mouse would be great. Below is the output of logid -v and I've confirmed its the same both with the mouse config working and not:
Lastly I looked in dmesg and found nothing out of the ordinary, just a single line: [ 16.301878] [ T1793] input: LogiOps Virtual Input as /devices/virtual/input/input41
Any help is appreciated, the Master MX 3S isn't really that usable without LogiOps so thank you.
The text was updated successfully, but these errors were encountered:
I have the same problem under Arch Linux. Most of the time the mouse is recognized after starting the PC, but sometimes not. Then I have to restart the service and move the mouse in the meantime. I am currently testing whether the timeout solves the problem: #446 (comment)
I am using a Master MX 3S running on OpenSUSE Tumbleweed with Plasma 6 (all latest from Tumbleweed repo's). I've noticed that when booting up, or coming out of hibernation, that if the mouse wasn't moving during the initialization that it doesn't initialize. If I execute a
systemctl restart logid
while moving the mouse it will restart the daemon and everything will work fine. If i rerunsystemctl restart logid
and do not move the mouse it will go back to the uninitialized state, with one small caveat that the mouse dpi seems to be remembered (buttons revert to pre-logid settings but dpi is retained). I can tell it's not working in the beginning because the mouse is so slow, I havedpi: 3000
which seems to work well for me, but when it's not working it's similar todpi: 1000
in its movement. I also have the thumb buttons (below the wheel) set to move to next / previous workspace, as opposed to the default (without logiopt installed) of forward / back. So when I log in the mouse is slow, and the buttons are forward / back. If I restart the daemon (or turn the mouse off/on) everything works as expected. But, if I runsystemctl restart logid
while not moving the mouse the buttons reset to forward / back but the dpi does seem to stick. I'm not sure if any of this is related, but wanted to give the info just in case it helps.A way to get it to initialize without movement from the mouse would be great. Below is the output of
logid -v
and I've confirmed its the same both with the mouse config working and not:Lastly I looked in
dmesg
and found nothing out of the ordinary, just a single line:[ 16.301878] [ T1793] input: LogiOps Virtual Input as /devices/virtual/input/input41
Any help is appreciated, the Master MX 3S isn't really that usable without LogiOps so thank you.
The text was updated successfully, but these errors were encountered: