Hello!
I set hardware.wooting.enable to true, but Wootility still won’t detect my keyboard. I also made sure to add my user to the “inputs” group. Is there anything else I need to do?
Hello!
I set hardware.wooting.enable to true, but Wootility still won’t detect my keyboard. I also made sure to add my user to the “inputs” group. Is there anything else I need to do?
You probably need to log out and log back in for your user to “be” in the inputs group.
I’ve already restarted a few times
Does the keyboard work on different systems?
Does the journal show anything when they keyboard is plugged in?
The keyboard works fine, but Wootility won’t detect it. Inputs work normally, RGB turns on, etc. I don’t know if Wootility works on other systems as I only have one computer
Journalctl shows these logs when plugging it in: https:pastebin.com/Gp89N4ry
I don’t see anything from wootility there…
I’m also on nixos (with sway) and have just set hardware.wooting.enable to true, for my new 80HE
I can see it has written the udev rules into /etc/udev/rules.d/70-wooting.rules
I run “groups” and see that I am a member of “input”
But my wootility doesn’t seem to detect my device either
I enclose my journalctl and output from launching wootility in terminal…
I see wootility state “Giving permissions for device” but no further outputs.
Unfortunately (or fortunately imo ) my main PC and laptop are both on nixos, so don’t have anything “else” to test on.
Although, this is my second wooting (60HE before) and the 60HE keyboard also doesn’t recognise. So I’m most certain it’s not the keyboard(s)
I think I set up the 60HE initially when I was running fedora, hence not noticing wootility not detecting until now
I seem to be unable to launch wootility application as sudo (perhaps due to my limited knowledge)
But… I am able to launch chromium elevated as sudo, with “sudo -E chromium --no-sandbox”
Then, after doing so, the Web version of wootility does immediately detect my keyboard and works fine
So it seems related to the udev rules being effective, or my user permissions.
I’m unsure if this is nixos wooting option issue worthy, and I would not be sure where to raise that anyway.
But if anyone else has nixos, a wooting, and the same issue, I can at least suggest that workaround