Skip to content
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

karabiner 14.13.0 fails to start manager on MacOS Sonoma 14.4.1 #3781

Open
tbee opened this issue Apr 15, 2024 · 4 comments
Open

karabiner 14.13.0 fails to start manager on MacOS Sonoma 14.4.1 #3781

tbee opened this issue Apr 15, 2024 · 4 comments

Comments

@tbee
Copy link

tbee commented Apr 15, 2024

Opening the settings show the "please allow" overlay. I've tried many solutions, from Karabiner reinstall, to startup in safe mode. Manually starting from a terminal shows a different error. What else is there to try?

Screenshot 2024-04-15 at 10 24 27 Screenshot 2024-04-15 at 10 25 21
@aspauldingcode
Copy link

Same here

@TheRealMXDDXM
Copy link

@tbee , @aspauldingcode , are you computers managed by corporate IT at all?

I have the issue with Karabiner V14.13.24 on Ventura 13.6.6 (22G630). I believe it might be to do with my IT department not allowing the installation of software that is not from 'App store or identified developers'. When I (re)install Karabiner or reactivate the driver, I do not get the prompt to allow it.

It's a hunch but the best idea I have at present.

@tbee
Copy link
Author

tbee commented May 16, 2024

@TheRealMXDDXM my computer is in a grey zone. We have Microsoft Defender installed, there are entries in the settings (you can find that elsewhere on the interwebs) to show that it is managing, but it is not set blocking anything. I can turn it off if I want, but that does not seem to help.

@aspauldingcode
Copy link

@TheRealMXDDXM No, but My issue has been fixed as of V 14.13.14 and I've turned off SIP, AMFI, Library Validation, and it is currently working for me on Sonoma 14.4.1.

I don't know how, or why, but I woke up one day and it was fixed. Probably adding AMFI disable flag to nvram.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants