danielisaacrodriguez
commented
3 years ago I am glad someone else also hit this issue. I reported it here: https://github.com/pqrs-org/Karabiner-Elements/issues/2513 I hope it can be fixed.
Closed xiao-zang closed 3 years ago
danielisaacrodriguez
commented
3 years ago I am glad someone else also hit this issue. I reported it here: https://github.com/pqrs-org/Karabiner-Elements/issues/2513 I hope it can be fixed.
Terubozu
commented
3 years ago I get the same problem on my M1 Mac Mini. I reported it in #2513, but it's closed over there, so I'll report it here as well.
My report is at the following link. https://github.com/pqrs-org/Karabiner-Elements/issues/2513#issuecomment-731616784
gmedori
commented
3 years ago +1. The computer I got my wife (M1 MBP) is having the same issue. 16GB RAM with 2TB SSD is the configuration.
owner203
commented
3 years ago +1. The same issue on my M1 MacBook Pro with 16GB RAM / 2TB SSD. Big Sur 11.0.1
xereeto
commented
3 years ago Yup MBP M1 8/256GB Big Sur 11.0.1. Same deal. Was about to RMA the MacBook before I realised this could be the cause, uninstalled it and boom no more errors.
profoundthinking
commented
3 years ago I can confirm I am also experiencing this, the system restarts itself after shutdown with an error.
MBP M1 16GB/512GB SSD. Big Sur 11.0.1
purge
commented
3 years ago Since karabiner is no longer a kernel extension a panic is probably an apple issue so if you are getting this raise an issue in feedback assistant (or radar if you have a developer account). I am experiencing this issue on brand new install on new hardware (M1 16Gb / 1Tb.) so i don't think it's an issue with other software.
schram
commented
3 years ago Just confirming the same results on an M1 MacBook Air, fresh install and the only other software yet installed is vlc, Lastpass, MS Edge Canary, and vscode. Uninstalling allows my MBA to reboot without a panic and gives me back my startup chime. Really don't want to uninstall, though.
fredericksee
commented
3 years ago Just reporting that I have the exact same issue as schram has described above.
taylornd
commented
3 years ago Same issue for me
mono96
commented
3 years ago I get the same issue on my M1 MacBookPro （8GB 512GB）
macOS Big Sur 11.0.1 (20B29) Karabiner-Elements 13.1.0 / 13.1.1 beta
l installed is Karabiner-Elements, only. After stopping the Karabiner-Elements, restarting macOS also crashes.
Uninstalling Karabiner-Elements will not cause this issue.
And, When updating Karabiner-Elements from 13.0.0 to 13.1.0, the reboot after disabling the drivers did not cause any problems. Therefore, l think that the issue is due to the drivers.
I hope this issue will be solved.
jeremysexton
commented
3 years ago Having same issue here, M1 MBP (16GB, 2TB), Big Sur 11.0.1
ikuina
commented
3 years ago My M1MBP(16G, 2T, BigSur11.0.1) has same issue. After installing Karabiner, everytime shutting down, I see pink screen.
sweeneybros
commented
3 years ago also having the same issue with M1 MBA 16GB/512GB
jacklaing
commented
3 years ago I have this issue with my M1 MBP too, running 11.1 Beta 2. Have uninstalled and periodically checking in here to see if it has been fixed yet.
atelierbram
commented
3 years ago Same problem her on M1 Mac Mini with almost no other apps installed. Had to uninstall to fix it. BTW no pop-pup to disable driver after trying the beta version.
gelpenaddict
commented
3 years ago I have this issue with my M1 MBP too, running 11.1 Beta 2. Have uninstalled and periodically checking in here to see if it has been fixed yet.
You can also click "Subscribe" on the right side of github issues to get updates for particular issues.
I also get this issue on M1 Macs. Please fix.
MarkLopresto
commented
3 years ago Also experiencing this issue. Issue persists in Safe Mode, and in a test user account with no other 3rd party apps installed. Uninstalled Karabiner Elements to resolve. Logs basically identical to original poster.
MBA M1 16GB | 512GB | macOS 11.0.1 (20B29)
rickybright
commented
3 years ago Same issue here. Can post logs if needed, but basically the same as OP.
g8rh8r
commented
3 years ago I had very similar and relentless kernel panics on a brand new M1 Mac mini. It happened shortly after installing the legacy X-Rite i1 display pro calibration software/driver to try to calibrate my monitor. I went to the X-Rite website and followed their complete uninstall directions.
No more kernel panics.
Big Sur is a nightmare when installing any legacy drivers on Apple m1 ARM machines.
tam315
commented
3 years ago I'm using M1 Mac in the following combination, removing either i1Profiler or Karabiner solved the problem. Thanks a lot @g8rh8r ! (i1Profiler isn't working anyway so removing that is OK in my case)
UPDATE: kernel crashes came back now 🤢
xiao-zang
commented
3 years ago I'm using M1 Mac in the following combination, removing either i1Profiler or Karabiner solved the problem. Thanks a lot @g8rh8r ! (i1Profiler isn't working anyway so removing that is OK in my case)
- Mac OS 11.1 (released today)
- Karabiner-Elements 13.1.0
- i1Profiler 3.3.0
Glad that uninstalling i1Profiler works for you, but I don't have any X-Rite product on my M1 Mac. I have just installed the macOS 11.1 update and reinstalled Karabiner-Elements 13.1.0, but it still crashes...
g8rh8r
commented
3 years ago I'm using M1 Mac in the following combination, removing either i1Profiler or Karabiner solved the problem. Thanks a lot @g8rh8r ! (i1Profiler isn't working anyway so removing that is OK in my case)
- Mac OS 11.1 (released today)
- Karabiner-Elements 13.1.0
- i1Profiler 3.3.0
Glad that uninstalling i1Profiler works for you, but I don't have any X-Rite product on my M1 Mac. I have just installed the macOS 11.1 update and reinstalled Karabiner-Elements 13.1.0, but it still crashes...
Well the kernel crashes came back. Since it's a brand new M1 Mac mini, I have very few programs installed.
So I started analyzing the crash reports and realized they had sleep time in common. The only device I had connected other than my keyboard, was my 4k monitor. I had my monitor connected via an AKiTiO Thunder Dock, via a thunderbolt to DisplayPort cable. So I unplugged the AKiTiO thunder dock and connected my 4k monitor directly to the Mac mini Thunderbolt 3 port with a thunderbolt 3/usb-c to DisplayPort adapter.
The crashes have stopped for the last 24 hours or so. I spoke to an Apple senior tech, and she had me send my log files to engineering. So if I had to guess, the kernel panics may have to do with legacy thunderbolt devices and sleep commands...
xiao-zang
commented
3 years ago I'm using M1 Mac in the following combination, removing either i1Profiler or Karabiner solved the problem. Thanks a lot @g8rh8r ! (i1Profiler isn't working anyway so removing that is OK in my case)
- Mac OS 11.1 (released today)
- Karabiner-Elements 13.1.0
- i1Profiler 3.3.0
Glad that uninstalling i1Profiler works for you, but I don't have any X-Rite product on my M1 Mac. I have just installed the macOS 11.1 update and reinstalled Karabiner-Elements 13.1.0, but it still crashes...
Well the kernel crashes came back. Since it's a brand new M1 Mac mini, I have very few programs installed.
So I started analyzing the crash reports and realized they had sleep time in common. The only device I had connected other than my keyboard, was my 4k monitor. I had my monitor connected via an AKiTiO Thunder Dock, via a thunderbolt to DisplayPort cable. So I unplugged the AKiTiO thunder dock and connected my 4k monitor directly to the Mac mini Thunderbolt 3 port with a thunderbolt 3/usb-c to DisplayPort adapter.
The crashes have stopped for the last 24 hours or so. I spoke to an Apple senior tech, and she had me send my log files to engineering. So if I had to guess, the kernel panics may have to do with legacy thunderbolt devices and sleep commands...
But my M1 MBA with Karabiner-Elements crashes without any external device plugged in (not even the power cable)...
crcoppin
commented
3 years ago I am having this issue as well since using migration assistant. My M1 Mac Mini running 11.1 and KE 13.1 will flash a pink screen and panic every time I try to restart or shutdown when Karabiner is running. All worked well in safe mode, as did uninstalling Karabiner.
TimNedvyga
commented
3 years ago Same here(Mac mini M1 base model), it appeared after updating to 11.1. It was fine on 11.0.1 for me.
sasagar
commented
3 years ago Same here, but I encountered with 11.1 and 11.0.1 too.
wookiist
commented
3 years ago same here.. using mac mini (apple silicon). cannot shutdown or reboot with karabiner. pink screen situation also occured.
ssmooncoder
commented
3 years ago i'm not even on big sur, but kernel panics and sleep-wake failure came back after a recent security update to Catalina.
It'll happen once the machine goes into deep sleep (i.e., keep the lid closed for like an hour).
macOS is just awful to use now. I don't care if the M1 outperforms this or that chip if the operating system is less reliable than Windows 95 with a corrupt ram stick
benjaminpottier
commented
3 years ago I'm on Big Sur 11.1 with an M1 Mac mini and had to uninstall karabiner in order to get rid to the kernel panics at shutdown.
ghost
commented
3 years ago I'm also on Big Sur 11.1, using an M1 MacBook Pro 16GB/1TB. System hangs for a second on shut down and restart, screen flashes pink, then restarts (even if Shut Down was chosen). On logging back in I get a similar kernel panic report as posted by @xiao-zang.
I did a full wipe of my laptop (not a big deal because I only got it a few days ago), and checked that shut down and restart work with no kernel panics. Then installed Karabiner, allowed the driver in System Prefs but didn't do anything else with the app (Karabiner was the only programme installed other than the default apps) and the kernel panics came back on every shut down and restart. I uninstall the app (using the button in the Misc Tab) and the kernel panics go away, my machine shuts down properly again.
I also did some testing on the install process - it seems to be that allowing the driver in System Prefs causes the panics to start happening (unsurprisingly). When I install Karabiner, open the app, and get the pop-up to allow the driver in System Prefs (".Karabiner-VirtualHIDDevice-Manager") if I ignore this and shut down, the system doesn't kernel panic. If I then allow this driver in System Prefs, the kernel panics come back.
Hope this info can help with fixing the issue.
Markologne
commented
3 years ago Same here (M1 Mac mini, 16GB/1TB) Big Sur 11.1, Karabiner-Elements 13.1.0
windless0530
commented
3 years ago I believe this should be a solution for this issue, which I also encountered on my M1 Mac Mini with Karabiner 13.1.0.
In brief, use HammerSpoon instead.
First, download and install HammerSpoon: http://www.hammerspoon.org/
Then, edit the configuration file 'init.lua' following this thread to meet your need: https://stackoverflow.com/questions/43383348/remap-apostrophe-to-other-keys-using-hammerspoon/
This works for me perfectly :)
BTW, below is my configuration:
local function keyCode(key, modifiers)
modifiers = modifiers or {}
return function()
hs.eventtap.keyStroke(modifiers, key)
end
end
local function remapKey(modifiers, key, keyCode)
hs.hotkey.bind(modifiers, key, keyCode, nil, keyCode)
end
remapKey({"cmd"}, "escape", keyCode("`", {"cmd"}))
remapKey({"option"}, "escape", keyCode("`", {"fn"}))
hassan987
commented
3 years ago I'm having the same problem! Is this going to be fixed or should I go the HammerSpoon route? I tried Hammerspoon but could not get it to toggle 'fn' key on my windows keyboard, to use the media functions as default.
MuhammedZakir
commented
3 years ago I'm having the same problem! Is this going to be fixed or should I go the HammerSpoon route? I tried Hammerspoon but could not get it to toggle 'fn' key on my windows keyboard, to use the media functions as default.
IIRC, you can do that in System Preferences > Keyboard.
hassan987
commented
3 years ago That option only exists for built-in keyboards or other apple keyboards
eddyg
commented
3 years ago In brief, use HammerSpoon instead.
Has something changed with Hammerspoon? Previously, one of its primary developers specifically recommended the use of Karabiner Elements...
hassan987
commented
3 years ago Nothing has changed except Karabiner elements seems to cause system panics on Apple silicon macs, causing people to search for alternatives
MuhammedZakir
commented
3 years ago Try Kmonad - https://github.com/david-janssen/kmonad.
P.S. see https://github.com/Hammerspoon/hammerspoon/issues/1732 if you want modal layout in Hamerspoon.
eddyg
commented
3 years ago In my opinion, the power (and responsiveness and reliability) of Karabiner Elements is the fact that it is a low-level HID driver implementation. As agentk suggested here, I’m just ignoring the panic until 1) it gets fixed, or 2) we’re told it can’t be fixed and there’s a need to find alternatives. I reboot infrequently enough that I barely notice.
hairarrow
commented
3 years ago I'm running into the same issue on the m1 mini.
My one weird trick to actually shut down the computer is to disable automatic login and click "Shut Down" on the login screen.
I'm definitely not going to uninstall any time soon.
crcoppin
commented
3 years ago I'm running into the same issue on the m1 mini.
My one weird trick to actually shut down the computer is to disable automatic login and click "Shut Down" on the login screen.
I'm definitely not going to uninstall any time soon.
Another user reported a workaround that I think is the same as what you are doing. Essentially log out before shut down.
Edit: I have tried this workaround and it makes no difference for me. Logging out before shut down still results in a pink screen and panic. Since I have isolated the issue and don't shut down all that often, I am living with it for now.
ATG1209
commented
3 years ago Any update/workaround on this issue? Is it the same on the newest Big Sur beta?
TimNedvyga
commented
3 years ago Any update/workaround on this issue? Is it the same on the newest Big Sur beta?
it's fixed for me on M1 Mac mini with macOS 11.2 RC
gelpenaddict
commented
3 years ago it's fixed for me on M1 Mac mini with macOS 11.2 RC
Awesome to hear; from similar issues here, karabiner maintainers were not going to look into it themselves.
TimNedvyga
commented
3 years ago Well, I began to encounter this problem on RC2 again. But it's not consistent, most of the time machine turn off and restart just fine.
crcoppin
commented
3 years ago Great news, BetterTouchTool has been updated to allow for a hyper key - issue solved without giving up my functionality. https://community.folivora.ai/t/thank-you-for-capslock-hyper-a-small-request/20907/4
TimNedvyga
commented
3 years ago Great news, BetterTouchTool has been updated to allow for a hyper key - issue solved without giving up my functionality. https://community.folivora.ai/t/thank-you-for-capslock-hyper-a-small-request/20907/4
It also can recognise Fn now! Well, that's actually a game changer, I do not need karabiner anymore! Awesome!
gelpenaddict
commented
3 years ago Looks like they also have some crashes but limited to the app and not as bad as the kernel panic with Karabiner: https://community.folivora.ai/t/apple-m1-night-shift-clash/20877
And they're actually getting an M1 box to test and make progress!
matsuda0707
commented
3 years ago Today version 13.3.0 has been released, but it still cause Kernel Panic after installation. But it does not repeat restart, only show Kernel panic message after login. A little bit progress, but not fully fixed!
After I installed Karabiner Elements on the new Apple silicon MacBook Air, the system crashes during the shutdown process. The system restarts due to the crash no matter whether I choose to shut down or restart. In the latter situation, at first glance I cannot tell whether the restart is due to a crash or it is a "successful" restart. However, I know there is a crash because the system shows the crash report every time after the restart. Uninstalling Karabiner Elements solves the problem, and reinstalling Karabiner Elements makes it crash again, so it is highly likely that Karabiner Elements is the cause. I will uninstall Karabiner Elements for now and wait for the developer to fix the issue.
The following is the crash report: