-
-
Notifications
You must be signed in to change notification settings - Fork 830
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 elements breaks the TouchBar on the new MacBook pros #435
Comments
+1 |
@DJCool1 check out this one. Decent fix, makes sense since I guess macs think that it's another keyboard. |
Ah thanks, that fixed it. For some reason, in my case there was not just one but two "No product name" keyboards listed, so I unchecked both. |
I had issues too - strangely enough the only FN keys affected were Mission Control's F11 and F12 for show desktop and dashboard respectively. They were "stuck" at volume down and volume up instead. I uninstalled Karabiner Elements and I got my keys back. Incidentally this was with the latest version (as of this writing). |
Yup. I'm experiencing this too. The unchecking "No Product Name" solved the Mission Control/KB/iTunes issue, but as noted the holding down Fn is still broken. Thanks! |
Just ran into the same issues as others here. To be specific, though, the Touch Bar buttons that fail seem to be the ones formerly mapped to the Fn keys: mute, volume up/down (but not the volume button that goes into the slider), play/pause (but not when in iTunes), Mission Control, keyboard lighting, etc. It's probably just incorrectly intercepting those events. |
Another important one that no longer works when Elements is installed is Option-Command-Esc to Force Quit. |
Good point @allenmhc ! I think you're right. Interesting that it is registered as a keyboard. @broberts01 that's weird, so holding down the fn key doesn't show up the function buttons? For me it does, and f11 works as "show desktop" |
@kyleholzinger: Correct w/o Elements holding Fn shows F1 through F12 in any app. With Elements Fn has no effect on the Touch Bar (though if you hit Fn twice dictation will start as expected). |
Hm interesting. @broberts01 and that's even after you turned off the "No Product Name" input in the devices preferences? |
@kyleholzinger: Correct. The "No Product Name" is unchecked. |
i can attest to the observations @broberts01 is describing. I have the same exact issue. |
I wonder if you uninstall karabiner if it work @noestreich @broberts01 |
@kyleholzinger funny, I just read your reply on my phone opened up the MacBook and wanted to reply:"Yes it works when Karabiner is uninstalled but not as described above", but then i realized, that the FN key worked again. This was the first time my MacBook went to sleep since my last reinstall of Karabiner maybe there is a connection. |
Hm interesting @noestreich. No idea! I've never used karabiner with sierra so no idea. Glad it works now though! Maybe that's the answer |
I have the same problem, with Karabiner Elements installed and "No product name" disabled the Interestingly, if I add an external Apple keyboard (0x024f) and disable modifying events from it, then the Perhaps we can repurpose http://kupdates.com/tech-news/hashkey-1-button-for-all-your-hashtagging-needs/ 😛 |
@vincent99 I suspect something else is going on, seems like the touchbar is definitely another input device. I'd check your installed programs for seil or karabiner or something, but for everyone else it seems like for the most part disabling the "no product name" device solved this issue |
Just so we're clear -- disabling the "no product name" device solves the Mission Control/KB/iTunes issue, but as noted the holding down Fn to get the function keys is still broken as is any KB combination that includes the Fn keys or Esc. e.g Cmd-Optn-Esc, Cmd-F9, etc. |
When Karabiner-Elements 0.90.67 is running, holding down the fn key doesn't cause the function keys to appear on the Touch Bar. When I quit Karabiner-Elements, the problem goes away. Under "Devices", "No Product Name" shows up twice, both of which are unselected (and were unselected by default after installation). Under "Function Keys", "Use all F1..." can either be selected or deselected, the problem occurs either way. |
I have noticed EventViewer registers the keystrokes for mute, next track, previous track, play/pause, volume up, volume down as "SysKeyUp" eventTypes, but never a "SysKeyDown" on the TouchBar. Esc, keyboard brightness, and screen brightness all register as "SysKeyDown." I don't know enough to fix the issue but it seemed important. |
+1 |
I would also like to notice that for all applications you force the function keys to appear (System Preferences -> Keyboard -> Shortcuts -> Function Keys menu), those keys do not work with any kind of modifier key: Shift, Ctrl, Alt or Cmd + any function key is treated as function key only. |
Any update on a "proper" resolution to these issues for MacBook Pro TouchBar users?
|
I am experiencing the same problem with karabinier elements and the Fn key. I would love to see a fix or feedback |
I'm having the same problem as others; if I disable the 'no product name' device, then the fn key works to bring up the extended touchbar (with it enabled, this doesn't work), but disabling this device stops the escape key from functioning properly, this effects force-quit as well as other shortcuts involving escape. With the device disabled, escape does work as a stand-alone key, just not with modifier keys. |
Same problem here ,FN dont display the FN keys on touchbar |
Any progress here? |
I've had good luck disabling the "No product name" device from Karabiner Elements as a workaround. |
+1 for FN doesn't do anything when karabiner running |
@makslevental you've tried the above suggestions of disabling the "no product name" as a device? |
@kyleholzinger correct |
@makslevental what others have suggested above regarding letting the computer sleep worked for me. Put it to sleep or go into screensaver then log back in. Fn keys work again... Although this is not ideal, it might partially solve the issue. |
I have had similar issues (the first few keys of my control stripe stopped working after installing karabiner elements) but I can see no way to fix it, even after uninstalling karabiner and rebooting the system. And there are people with the same issue on Apple's forum. |
Any progress on the issue that prevents Option-Command-Esc from opening Force Quit when Elements running? Whenever I want to use Option-Command-Esc to open Force Quit, I have to first quit Elements. |
Here's a link to my screen recording on YouTube showing the Option-Command-Esc bug: https://youtu.be/XxQ745Zhz6k |
I have the same issue |
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. |
Yaah, me too. Is there anything we (users) could help with? |
Running into the Shift + fn + fn key not registering the shift issue. Anyone have a fix? |
I'm experiencing the same thing. I can't open the Force Quit dialog window (Option-Command-Esc) when "No Product Name" is unchecked. However, if I check it, my display brightness, keyboard backlighting controls don't work. It sounds like with some rewiring this can be fixed where it's no longer mutually exclusive. Has anyone found a workaround other than checking/unchecking the boxes? |
Hey guys, please check the solution at #535, works for me. |
I swapped fn and left_control on 2017 touchbar mbp running high sierra. MacOS configured to show F1, F2 on touchbar. But even with fn and left_control swapped, pressing either key causes touchbar to show expand control strip (as far as touchbar is concerned, now I have 2 fn keys) |
There is a good solution here. |
Karabiner-Elements
MacOS
Still Touchbar Expand Control Strip when I press either physical fn or left_control key, in my case making it impossible to perform left_command (physical Fn key) + F1 |
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. |
To save folks having to dig through the entire other thread, the workaround on Karabiner side is this post (enable keybaord 1452/34304) #535 (comment) plus possibly this post #535 (comment). |
I also filed #1700 as a feature request to have that keyboard enabled by default. |
None of my touchbar buttons worked after installing Karabiner elements. After uninstalling it, they all immediately started working again.
The text was updated successfully, but these errors were encountered: