Skip to content
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

skhd aborting because of false secure keyboard entry error #48

Closed
msuess opened this Issue Sep 4, 2018 · 16 comments

Comments

Projects
None yet
8 participants
@msuess
Copy link

msuess commented Sep 4, 2018

When I try and start skhd from the CLI it aborts with

skhd: secure keyboard entry is enabled! abort..

It randomly stopped working after a reboot yesterday and I couldn't get it to run since then. I've tried rebooting, reinstalling, reinstalling with --HEAD and turning accessibility access off and on, to no avail.

@crisidev

This comment has been minimized.

Copy link

crisidev commented Sep 4, 2018

You have enabled the secure keyboard entry without noticing (iTerm2).

Click on iterm2 menu, and then click on Secure Keyboard Entry to and untick it :)

@msuess

This comment has been minimized.

Copy link
Author

msuess commented Sep 4, 2018

Hey, thanks for the quick response. I'm using kitty as my terminal. Here's a screenshot of me trying to run it in Terminal.app:

screen shot 2018-09-04 at 14 05 13

It's also not working when started as a service, with the same error message in the log file.

@msuess

This comment has been minimized.

Copy link
Author

msuess commented Sep 4, 2018

I... just restarted my laptop without my screen connected, restarted chunkwm and skhd and plugged in my screen again. It's working now 🤔

@msuess msuess closed this Sep 4, 2018

@msuess

This comment has been minimized.

Copy link
Author

msuess commented Sep 4, 2018

Sorry for the false alarm, everyone!

@yurrriq

This comment has been minimized.

Copy link

yurrriq commented Sep 7, 2018

This keeps happening to me. skhd will stop working and if I try to restart it I get the "secure keyboard entry" error. I, too, am using kitty. Any advice? FWIW it works briefly if I log out and log back in. Maybe it's an issue with my company's AD.

@koekeishiya

This comment has been minimized.

Copy link
Owner

koekeishiya commented Sep 7, 2018

Some application on your system is likely turning it on without notifying you.

@yurrriq

This comment has been minimized.

Copy link

yurrriq commented Sep 7, 2018

Any tips on how to track that down?

@koekeishiya

This comment has been minimized.

Copy link
Owner

koekeishiya commented Sep 7, 2018

Not sure if this still works, but I came across this:


peternlewisElderDec '15
Thanks to info provided by the fine folks at Smile Software 24, you can use the Terminal command:

ioreg -l -w 0 | grep SecureInput
That will tell you the process ID (kCGSSessionSecureInputPID) of the application that has Secure Input enabled. You can then use:

ps auxww | grep NNN
to find the process with the specified pid.

I will endeavour to add some support for this within Keyboard Maestro’s alert in the future.

Thanks again to the Smile Software 24, makers of great Mac software!

Source: https://forum.keyboardmaestro.com/t/disable-secure-input/2410/3

@yurrriq

This comment has been minimized.

Copy link

yurrriq commented Sep 13, 2018

I'm just seeing your advice, thanks. By brute force, I think I've determined it was Keybase.app. After almost a week I finally have skhd back! 🎉

@msuess

This comment has been minimized.

Copy link
Author

msuess commented Sep 14, 2018

Hah, that was it for me as well!

@WhatisRT

This comment has been minimized.

Copy link

WhatisRT commented Sep 14, 2018

Maybe the info on how to troubleshoot this could be put somewhere in the readme? I'm having the same issue (though I cannot test if the troubleshooting will help me, as I just rebooted and it's working for now).

@koekeishiya

This comment has been minimized.

Copy link
Owner

koekeishiya commented Sep 14, 2018

I might implement support in skhd for figuring out the application keeping secure keyboard entry enabled, when it detects that it is in fact enabled, if I can be bothered looking into the IOReg API.

@dominiklohmann

This comment has been minimized.

Copy link

dominiklohmann commented Sep 14, 2018

This oneliner works. Broke it up into multiple lines to make it easier to read.

ioreg -l -w 0 \
    | perl -nle 'print $1 if /"kCGSSessionSecureInputPID"=(\d+)/' \
    | uniq \
    | xargs -I{} ps -p {} -o comm=

Edit: Updated to make it much easier to read and also work with multiple different sources of secure keyboard input.

@WhatisRT

This comment has been minimized.

Copy link

WhatisRT commented Sep 20, 2018

Well, in my case it was actually safari. Turns out in enables secure keyboard entry when you want to get a password from the settings dialogue, and just closing that window did the trick...

@L3rchal

This comment has been minimized.

Copy link

L3rchal commented Sep 26, 2018

In my case it was loginwindow console process
(So I killed it with my whole user session 😆 I do not recommend this).

@halvardlange

This comment has been minimized.

Copy link

halvardlange commented Mar 20, 2019

I had the same issue, and it was the loginwindow console process that caused it. I just locked my screen, and logged in again - that fixed the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.