pqrs-org/Karabiner-Elements

Caps Lock LED no more working since 0.90.67 (still on 0.90.68)

ZeeArts opened this issue ยท 23 comments

Since version 0.90.67 the caps lock led is no more workin.
Keybindings also no more workin. Only un- and reinstall help. Till restart of the system.
The event_manipulator issue still on 0.90.68.
I'm back again to 0.90.66
screenshot

I do agree!

Same problem here. After upgrading to 0.9.68 the Caps Lock key and LED are not working anymore.

Bump! Same here.
KarabinerEventViewer sees caps-lock being pressed, Apple's Show keyboard viewer shows caps-lock being clicked but caps lock does not work.
Caps lock fails both on internal keyboard or external.

Weird, this worked for several days and now does not, once again force quit of karabiner_grabber resolves the issue

same issue here.
since last update capslock not working until quit kaeabiner-elements app

Edit: Thanks thymara... worked for me

Yep, same here. I can make capslock work again by for the time being, unticking 'Apple Internal Keyboard' in Devices pane in Karabiner-Elements settings. Appreciate your amazing development, dev!!!

Tried unticking 'Apple Internal Keyboard' in Devices pane in Karabiner-Elements settings. While it worked as far as the caps lock light goes several of my modifications no longer worked

RESTARTING KARABINER GRABBER HELPS! as you see! :)

@thymara @bcubic @RicoSky Are you suggesting to kill a karabiner_grabber process? I don't have such a process running while Karabiner-Elements is running. Can you be more specific? Would be much appreciated.

if you use Activity Monitor and then search for "kar" it will show about 4 processes, one of which is grabber. Quick way to start Activity Monitor is to use Spotlight

Thanks for the quick response @thymara. I have 3 such processes: Karabiner-Elements, karabiner_console_user_server, and karabiner_event_dispatcher.

Everything is working as expected, except for the Caps Lock bug described here.

not sure why you don't have grabber, it will take someone much more knowledgeable than I am on this subject. The fact that you don't have grabber suggests a possible installation error. I was very fortunate when I discovered the installation instructions which made things quite simple

I followed those instructions to reinstall and am now experiencing #448. By downgrading to 0.90.66 I can resolve that issue (#448) as well as this one (Caps Lock works again).

I've been hitting this as well with all my external keyboards. Pretty annoying. Looking forward to a fix. :)

Same issue for me as well. Quitting karabiner grabber helped, but I still look forward to a fix.

Same issue. As soon as it's loaded by system, it stops working.

Restarting Karabiner grabber helped! It restarts itself, just force quit it.

I have both of the issues mentioned above. Karabiner-Elements is preventing the Caps Lock key from working on the internal laptop keyboard. If Karabiner is running, Caps Lock doesn't work and the LED does not turn on, although Karabiner Event Viewer detects the key press. Also, I do not have a "grabber" process running so I cannot kill it as suggested by someone above. I am running 0.90.68 on a MacBook Pro (15-inch, Late 2016) with Sierra 10.12.2.

In my case, I cannot find any process without Karabiner-Elements. So I tried re-installing. Now all works fine.

Restart the karabiner grabber, that seems to work for me in version 0.9.68.

qmmr commented

Same issue here. Works after updating to latest version and restarting ๐Ÿ‘

stale commented

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.

I'm having problems with Capslock key I think. It only works when I map right_option to it, but only turns it on, then it stays on and I can not turn capslock off. Trying to_if_alone mapped back to caps_lock doesn't help either. Note, I've mapped caps_lock to left_control, which is why I'm trying to find a way to make Capslock functionality work. I thought I was doing something wrong, but maybe I'm not if there's actually this problem here that is interfering.

My config looks like this.