-
Notifications
You must be signed in to change notification settings - Fork 25
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
Does not map keys when using razerkbd
driver
#29
Comments
Thanks for reporting! I suspect that the keyboard is the problem. Have you tried another keyboard? Could you please post the output of |
In 2.1.2 a mistake slipped in, so it did not load the config from the .config directory anymore. This was fixed in 2.1.3. |
My keyboard has several event devices.
And the one that is grabbed ( /dev/input/event3 supported events
/dev/input/event4 supported events
/dev/input/event6 supported events
I use the openrazer driver and from what I recall from looking at it last, it mostly just passes events through. |
Sorry my bad. I'll delete it 😅 |
Additionally, In my case, while debugging keymapperd debug outputThe first loaded config has mouse mappings and the second does not have mouse mappings.
/dev/input/event3 supported events
/dev/input/event4 supported events
/dev/input/event5 supported events
|
I noticed that RegEx isn't implemented for device names, perhaps a short-term fix could be to allow RegEx matching some specific event device? |
Thank you for your thorough report!
I did not want to grab devices with EV_ABS because I thought that only joysticks,... had these and I suspect that it is not so easy to forward them correctly. Maybe I could also get my hands on such a device and implement it properly. This would likely fix this issue.
That is how it is supposed to work. Mice are only grabbed when mappings exist.
that it set zero active contexts, which is quite suspicious. I will investigate how this is possible. Thanks! |
In the case of my devices, I think that is just Razer just misreporting devices because no matter what I press that event device doesn't actually emit any events for me. I was just saying if other devices misreport their capabilities that might be an issue.
Oh, I hadn't noticed that, Just so you know. I don't think it's directly related to the mappings not working when just ran the test again, albeit without `keymapperd --verbose`
`keymapper --verbose` Without any mouse key mappings
`keymapper --verbose` With mouse key mappings
|
Sorry, completly forgot about this issue. I can confirm this is a Razer problem. The razerkbd driver from openrazer cause the issue. When unloading it ( |
razerkbd
driver
After further investigation, I believe that this would fix this issue (at least in my case). For completeness, I believe it would also be possible to remove |
Is it also possible that this should be fixed on openrazers side? I don't know if this is clear, but razerkbd is an inofficial driver from openrazer. AFAIK it should only control RGB, I don't know why it is messing with keystrokes |
From what I know, Typically So it's possible, but some keyboards do appear to use the part that messes with |
@G-M0N3Y-2503 thanks for the clarification. I also think that |
Version: 1.10.0
OS: Manjaro, installed from AUR
keymapper -v output:
sudo keymapperd -v output:
Config file:
But no keys are mapped, they just behave like normal.
The text was updated successfully, but these errors were encountered: