-
-
Notifications
You must be signed in to change notification settings - Fork 829
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 completely broken on macOS Big Sur #2331
Comments
Looks like the kext isn't loading, but this is all probably expected. @tekezo has been working on a DriverKit version for a while already, so we likely just need to be patient while that develops over the summer :) |
Well, actually: $ kextstat | grep Karabiner
159 0 0xffffff7f9f095000 0x2000 0x2000 org.pqrs.driver.Karabiner.VirtualHIDDevice.v061000 (6.10.0) 4D004D1A-ED2F-3780-AD53-A10F286EC759 <51 6 5 3 1> (I guess I should clarify at this point that this is with SIP off, which lets the kext load, but it still does nothing useful except steal all keyboard input and make it really annoying to make the computer usable again.) |
Yep, I'll be waiting on a workaround. It's all that works with my spacebar broken. |
I have a similar problem!!! |
Workaround pls |
Just want to add my log to this issue - the kext isn't loading either for me. For the affected who map ESC to Caps Lock, you can remap this in Keyboard Prefs -> Modifier Keys... -> Select Keyboard -> toggle from Caps Lock to Escape. |
BetterTouchTool also allows for creating keyboard hotkeys, which can be used as a replacement for some cases. For example I created hotkeys for option + hjkl as arrow keys, which I did through karabiner before. Hopefully that makes it less painful for some of you :) |
Any alt for disabling internal keyboard? |
For me, upon upgrading to Big Sur I could not whitelist kexts — the option is there, and it asked me to do so and reboot afterwards, but it seems kind of broken (upon boot the kexts would remain disabled). However, I tried disabling SIP (reboot into recovery, open terminal, I had to remove Karabiner to regain use of my keyboard (which itself was also a hassle, as upgrading somehow made |
I hit this same issue.. you can also pull up the onscreen keyboard if you have a trackpad or a mouse that is still working via thats how I was able to uninstall and get my keyboard to work again. looks like disabling SIP does allowed kernel extensions to work for the beta period though. that said, currently karabiner-elements will effectively disable your keyboard from what I can see |
With SIP off the extension does load (as it should) but Karabiner doesn't like the that |
dang. looks like that maps to |
Oh, huh, interesting. I wonder if that is coming from the kernel or in userspace from IOKit/KernelManagement.framework? |
Anyone know another way to map space to right command? That was my workaround for a badly broken space bar. |
If you are doing only simple remapping, you can use Apple's built-in This was good enough for me (I only have 2 simple remaps - |
Wow, TIL! Thanks for sharing, it works great :) |
@chuyeow Thanks for sharing! But I can't figure out how to map "fn" key since it doesn't seem to have a code. |
@hiroshihorie Hmm I won’t be at a Mac for awhile so I can’t test it, but I did find this: https://opensource.apple.com/source/IOHIDFamily/IOHIDFamily-308/IOHIDFamily/AppleHIDUsageTables.h. Don’t know if |
@chuyeow the command keys are called "GUI" in the table. The function key may also have a counter-intuitive name 🤷♀️ |
yeah I'm also curious. was looking backwards in the commit history to see if another method for the kext load might work |
Wanted to point out other issues I’ve encountered: I’m not super familiar with the code as I’m a measly web dev. but hope this helps. |
Hm. I don't actually think this is the case. I built and ran the current build and got the following output
It should be noted that if I do not have Karabiner 'grabbing' any input devices (all the devices in the Devices tab are unchecked) it does not break key input.
that is the last line of karabiner's log. Also worth noting, despite the
*please ignore the |
Is there a way to map |
@chuyeow thank you so much for this info! Now I can set it and forget it 😃 (at least for the foreseeable future!) |
this one didn't work for me. I've been looking but haven't found anything. Does you know if karabiner-eventViewer is having issues as well? Could possibly test the fn key there? |
There is a note on https://karabiner-elements.pqrs.org since yesterday Is it related? Are we going through what happened from Karabiner to Karabiner-Elements again? 😭 |
I don't think it is quite the same. The legacy kext should actually still work with Big Sur, I'm wondering if maybe its a macOS beta bug or if something is hanging after the That said, it looks like quite a bit of progress has been made on the DriverKit version of the I downloaded and ran the client app and the macOS 11 beta was already recognizing the virtual device so I wouldn't be too worried. |
Will it be possible to remap the function key with Karabiner Elements in the future on Big Sur? I'm hoping they didn't remove that functionality... |
for those who are looking for a short term solution. you can also try Keyboard Maestro, BetterTouchTool is good, but it doesn't follow the system key repeat and delay setting when you want to use ctrl+hjkl to navigate, it's still very slow after you set to the shortest repeat time. |
Ok, let's break at
If you go up a frame, there's a a test and a load from it (the
So I would guess a missing lock? |
@saagarjha Thank you for feedback! |
Guess who can't read? Yep, it's me. Thanks for finding the actual fix, @tekezo :P 12.93.0 is looking good from my side; I'm glad to have Karabiner back :) |
Confirming it works on Beta |
Do you mean beta 6, or… |
Beta 6 yeah, sorry, too excited! |
Thanks for the release, I can confirm this works on Big Sur beta 6 also 🏅 Initially I got a "something went wrong" error when trying to open the Security & Privacy prefpane to allow access. The hoops, for future travellers:
|
🎉🎉🎉🎉 aaahhh it's so nice to have karabiner back finally! |
Also working on Catalina and seems to have fixed this issue where the system would hang when shutting down or restarting |
@tekezo On the latest beta (7), Karabiner-Elements reloads without a problem on reboot. 🥳 |
Hi, should I clone this repo and build from source for now, or should I download v12.10.0? I'm on Big Sur beta 7. Thank y'all for the great work btw! |
Use version 12.93.0 posted above. Edit: there's a 12.94.0, use that |
Hi, you can get the link to the beta here above: #2331 (comment) |
Thank you! @saagarjha @bosr |
For me, @gondalez solution worked because I (1) uninstalled all traces of Karabiner, (2) THEN opened Security and Privacy AND LEFT IT OPEN, (3) installed Karabiner 12.95.0. Previously, if the Sec and Priv was not already open, the Karabiner installation would fail because opening Sec and Priv crashed. |
On Big Sur Beta 8, I needed to open Karabiner, check for beta updates, install, and that was it. Everything worked! Oh and not sure if it's related, but if your on board keyboard is unresponsive, reset the PRAM (Cmd + Opt + P + R) and you're good to go. Yay. Everything seems to work. Even after reboot. EDIT: Although after an update, you need to do the above steps from @gondalez again. |
This comment has been minimized.
This comment has been minimized.
This is useful except there is one simple remap that I cannot live with: fn to left mouse click. Any way to accomplish this? Thanks |
You're able to shutdown/restart just fine? I literally cant turn my macbook off or sleep it, even after removing KArabiner. Its basically always on. No idea how to fix this. I'm on a macbook air M1 with big sur and the latest karabiner. |
Thanks for your brilliant idea, it helps me. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
亲,您的邮件我收到了,感谢您的来信。
|
It seems the beta broke Karabiner completely. The program opens and runs, but doesn't actually modify any keys.
Re-entering configurations does not fix it, nor does messing around with permissions to my knowledge.
The text was updated successfully, but these errors were encountered: