-
-
Notifications
You must be signed in to change notification settings - Fork 47
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
/dev/input/mouse1
: Inappropriate ioctl for device
#230
Comments
Is it related to #137. Caz I run Logitech K230+M350 with the same unifying receiver. |
/dev/input/mouse1
: Inappropriate ioctl for device
I do not have a unifying receiver so I don't think I can test this. If anyone with this hardware can send a patch, that would be amazing. |
I'm willing to |
I'm not too sure since I don't have that kind of hardware. Only a trial and error can suffice. |
+1 for this. I'm currently using an ELECOM HUGE Trackball Mouse and it gets swallowed by swhkd, making it unusable atm. I'd be willing to test out any available branch and report back. |
Being author of this issue I couldn't help you caz right now I've stopped using swhkd, because of the reasons for stubborn |
Hi we have a flag to ignore particular devices I believe. Can you try that? |
You're absolutely correct and I understand your pain point, it's part of our gsoc program. |
@Shinyzenith Would you point me in the direction of the docs that describe how to use the flag? The |
I believe you can just pass the name of the device. The names are emitted after: "attempting to find all keyboard file descriptors" in the logs. |
Version Information:
uname -a
)swhkd -V
)Describe the bug:
Mouse works fine, not sure what this issue is.
The text was updated successfully, but these errors were encountered: