Bug: IOHIDDeviceOpen error: (iokit/common) not permitted

[aljustiet]

Requirements

• I've searched platform-specific issues, issues and discussions to see if this has been reported before.

Describe the bug

Can't run the kanata. having permission related issue
When I run:

sudo kanata --nodelay --cfg ~/Documents/mac-arch/kanata.lsp

I get:

2024-08-27T22:38:02.385497+05:00 [INFO] kanata v1.6.1 starting
2024-08-27T22:38:02.386648+05:00 [INFO] process unmapped keys: true
2024-08-27T22:38:02.387009+05:00 [INFO] NOTE: kanata was compiled to never allow cmd
2024-08-27T22:38:02.389551+05:00 [INFO] config file is valid
2024-08-27T22:38:02.389593+05:00 [INFO] entering the processing loop
2024-08-27T22:38:02.389608+05:00 [INFO] entering the event loop
2024-08-27T22:38:02.389615+05:00 [INFO] Starting kanata proper
2024-08-27T22:38:02.389618+05:00 [INFO] You may forcefully exit kanata by pressing lctl+spc+esc at any time. These keys refer to defsrc input, meaning BEFORE kanata remaps keys.
IOHIDDeviceOpen error: (iokit/common) not permitted
IOHIDDeviceOpen error: (iokit/common) not permitted
IOHIDDeviceOpen error: (iokit/common) not permitted
2024-08-27T22:38:02.404165+05:00 [ERROR] failed to open keyboard device(s): Couldn't register any device


Press enter to exit
2024-08-27T22:38:02.404174+05:00 [ERROR] channel disconnected

Relevant kanata config

https://rentry.co/4qvbsknp/raw

To Reproduce

1. Open terminal
2. Run kanata --cfg config.kbd
3. Get an error

Expected behavior

Shouldn't have error

Kanata version

kanata 1.6.1

Debug logs

2024-08-27T22:48:30.251437+05:00 [INFO] kanata v1.6.1 starting
2024-08-27T22:48:30.252508+05:00 [INFO] process unmapped keys: false
2024-08-27T22:48:30.252827+05:00 [INFO] NOTE: kanata was compiled to never allow cmd
2024-08-27T22:48:30.252833+05:00 [DEBUG] (1) kanata_parser::cfg::alloc: freeing allocations of length 0
2024-08-27T22:48:30.255348+05:00 [INFO] config file is valid
2024-08-27T22:48:30.255394+05:00 [INFO] entering the processing loop
2024-08-27T22:48:30.255407+05:00 [INFO] entering the event loop
2024-08-27T22:48:30.25542+05:00 [INFO] Starting kanata proper
2024-08-27T22:48:30.255424+05:00 [INFO] You may forcefully exit kanata by pressing lctl+spc+esc at any time. These keys refer to defsrc input, meaning BEFORE kanata remaps keys.
IOHIDDeviceOpen error: (iokit/common) not permitted
IOHIDDeviceOpen error: (iokit/common) not permitted
IOHIDDeviceOpen error: (iokit/common) not permitted
2024-08-27T22:48:30.27162+05:00 [ERROR] failed to open keyboard device(s): Couldn't register any device


Press enter to exit
2024-08-27T22:48:30.271629+05:00 [ERROR] channel disconnected
2024-08-27T22:48:30.271657+05:00 [DEBUG] (2) kanata_parser::cfg::alloc: freeing allocations of length 2983

Operating system

MacOS Sonoma 14.6.1

Additional context

Installed using cargo.

[rsomani95]

I'm facing the same error (I'm also on macOS Sonoma 14.6.1). I installed via the binary in the Releases. I've cycled through some other issues that discuss this but none of the suggestions worked there either.

I verified that the dext part of the installation happened correctly as I can see the virtual keyboard in system settings:

Additionally, I verified the version like so:

> defaults read /Applications/.Karabiner-VirtualHIDDevice-Manager.app/Contents/Info.plist CFBundleVersion
3.1.0

[Reucherian]

This error is likely due to macOS's TCC (Transparency, Consent and Control).
Under Settings > Privacy and Security > Input Monitoring
Check if Kanata (and/or the terminal of your choice is present along with karabiner)

Adding the Kanata binary ( from ~/.cargo/bin/kanata especially if you're using it as a launch daemon) and adding your terminal to this list should solve the issue.

[rsomani95]

@Reucherian i believe i've set that up correctly. Here's what my input monitoring window looks like:

Still doesn't resolve the issue for me

[rsomani95]

I noticed you have a karabiner_observer, which I'm missing.
Is that something you added explicitly? If so, how does one go about doing it?

[Reucherian]

That is not something I added explicitly. Are you certain that kanata or the terminal application you use is on this list?
I don't see either in the screenshot.

To add a new application you can click the + button on the bottom and either drag the application to the new finder window or navigate to it using that window.

[Z233]

I faced the same problem and resolved it by:

1. Adding the terminal app (in my case, iTerm) to the "Input Monitoring" list.
2. Completely quitting Karabiner-Elements.

[sergei1152]

Ill add that it worked for me after adding kanata to the "Input Monitoring" list on macOS security settings. Frustrating all the hops you have to go through on macOS.

I'm now able to run kanata through launchctl with this.

My kanata is installed via homebrew so i added the /opt/homebrew/bin/kanata symlink.

[LeonardoMor]

Ill add that it worked for me after adding kanata to the "Input Monitoring" list on macOS security settings. Frustrating all the hops you have to go through on macOS.

I'm now able to run kanata through launchctl with this.

My kanata is installed via homebrew so i added the /opt/homebrew/bin/kanata symlink.

How did you do it? I have no way to browse /opt from the picker I'm presented with.

[LeonardoMor]

Nevermind. On the picker, just press ⇧⌘G

Then type the path manually.

[nivzelber]

This happens to me as long as karabiner is open. I couldn't find a way to make both of them to work.
I guess it's related to the way they create virtual keyboards.

[makkonen]

I banged my head against this for an embarrassingly long time. I tried different versions, different paths, whitelisting everything in the Input Monitoring permissions pane... but would always get the (iokit/common) not permitted error.

Turns out that the issue was my terminal of choice (alacritty). Even when enabled on the Input Monitoring page, it doesn't have access. Running in the native terminal resolved all the issues.

I don't expect this is a common sticking point, but I thought I ought to mention it anyway, in case I save someone else a few minutes (or hours) of frustration.

[aberezin-fti]

Cant use Karabiner proper with Katana because, it seems from Karabiner logs, that Karabiner already sees the socket create by katana to talk to the Karabiner-DriverKit-VirtualHIDDevice and so gives up. Im not sure I anyone has hacked the karabiner code to try to just create another socket and see if that works. I might do that or I might just pull the plug on Karabiner proper and remap all my karabiner mappings to katana.