Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mouse not initialized unless being moved #469

Open
jbeckman1974 opened this issue Aug 11, 2024 · 1 comment
Open

Mouse not initialized unless being moved #469

jbeckman1974 opened this issue Aug 11, 2024 · 1 comment

Comments

@jbeckman1974
Copy link

jbeckman1974 commented Aug 11, 2024

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 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:

[DEBUG] Unsupported device /dev/hidraw2 ignored
[DEBUG] Unsupported device /dev/hidraw3 ignored
[DEBUG] Unsupported device /dev/hidraw4 ignored
[DEBUG] Unsupported device /dev/hidraw5 ignored
[DEBUG] Unsupported device /dev/hidraw6 ignored
[DEBUG] Unsupported device /dev/hidraw7 ignored
[INFO] Detected receiver at /dev/hidraw8
[DEBUG] Unsupported device /dev/hidraw9 ignored
[DEBUG] Unsupported device /dev/hidraw1 ignored
[DEBUG] Unsupported device /dev/hidraw0 ignored

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.

@murkl
Copy link

murkl commented Oct 7, 2024

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)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants