-
Recently I have been working on a new project on NixOS for styling my DE but I also wanted to bring it onto my physical hardware as well. I've been using Kanata for nearly a year now and just can't break from it, but when I decided to enable OpenRazer on my system, Kanata just fails to work entirely, and it won't even find a keyboard based off the output with Kanata. Even manually trying to set the device in my configuration doesn't work. This issue has hit a major roadblock for me on my progress for taking my customization to where I'd like for them to be. Has anyone ran into this issue before or would happen to know how to fix this? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
You should ask the openrazer project how it manages kernel devices and how other software should be hooking in. E.g. Kanata grabs devices from |
Beta Was this translation helpful? Give feedback.
-
After long hours of looking around, I was able to find a fix, Open Razer requires you to have a group called "openrazer" turns out on NixOS with Kanata, It creates a new user for the kanata service such as |
Beta Was this translation helpful? Give feedback.
After long hours of looking around, I was able to find a fix, Open Razer requires you to have a group called "openrazer" turns out on NixOS with Kanata, It creates a new user for the kanata service such as
kanata-<DEVICENAME>
where device name is what you set in NixOS. The fix to all this was putting that user underhardware.openrazer.users = [];
and pointing kanata to the device manuallyDon't know if that's requiredNow everything works!