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
Media controls broken on Macbook Pro 2016 Touch Bar #431
Comments
Here's my log fwiw (karabiner.json parse error is from when I was experimenting with that file):
|
@dbryand that works for me too, thank you. |
I can confirm that @dbryand's post about unchecking the "No product name" fixes it for me as well, but one thing that is still broken for the touchbar mbp is holding the |
I had this problem, but restarting fixed the issue with the fn keys. Before, even though the fn-key switching was working, the actual function keys weren't working when I tapped them. After disabling the "No product name" device, everything works correctly on my end! My remaps are functional EDIT: upon further investigation, it doesn't work after a restart. Until you close and reopen the lid of the computer! I reproduced this a couple of times and karabiner-elements is working well for me |
Thank you for feedback! |
This seems to me a temporary fix.. What should I do if I want to map the esc (on the touch bar) to something else while keeping the media control keys to work? |
Hmm, I'm seeing the issue that ssameng reports on v0.90.86. After a fresh restart, the Fn key doesn't change the Touch Bar to the F1-F12 keys unless you close the lid and reopen it. Probably not the worst bug, but it threw me for a loop for a bit. |
There is not yet a fix for this right? |
There is a good solution here. |
While Karabiner-Elements is running, the media controls (volume up/down, play/pause, etc.) on the new Touch Bar don't respond.
I tried opening up the JSON file and removing all of the mappings defined by default in
"fn_function_keys"
. That didn't work.I'm running macOS Sierra 10.12.1. Here is my
karabiner.json
file:The text was updated successfully, but these errors were encountered: