search

espanso / espanso

Cross-platform Text Expander written in Rust
https://espanso.org
GNU General Public License v3.0
10.07k stars 277 forks source link

loginwindow always blocking espanso #469

Closed maxandersen closed 4 years ago

maxandersen commented 4 years ago

not sure what changed but recently I can no longer get espanso to work I constantly get this:


WARNING: An application is currently using SecureInput and might prevent espanso from working correctly.

APP: loginwindow
PROC: /System/Library/CoreServices/loginwindow.app/Contents/MacOS/loginwindow

Please close it or disable SecureInput for that application (most apps that use it have a
setting to disable it).
Until then, espanso might not work as expected.
Daemon started correctly!
``

i tried killed loginwindow but it keeps respawning instantly.

any idea on how to fix it ?
federico-terzi commented 4 years ago

Hey, Thanks for reporting this issue! That's unfortunate but doesn't seem to be limited to espanso: https://smilesoftware.com/textexpander/secureinput/#loginwindow

I'm wondering whether analyzing the process tree with pstree (which could be installed via homebrew) could give us some more insights.

What version of macOS are you running?

federico-terzi commented 4 years ago

Also, are you using 1Password? https://blog.twonegatives.com/post/48609305893/textexpander-disabled-because-of-loginwindow

maxandersen commented 4 years ago

Catalina and yes 1Password user. I'll try see if ptree can reveal something

federico-terzi commented 4 years ago

All right, thank you. I bet this is due to 1Password keeping SecureInput active then...

federico-terzi commented 4 years ago

Hey, Closing the issue as it doesn't seem to be related to espanso. Cheers :)

SantoshSrinivas79 commented 3 years ago

I am having the same issue ... is there a way to identify which app is using loginwindow? ... I don't have 1Password. When I start my OS (Catalina), espanso works perfectly ... but later it stops working

federico-terzi commented 3 years ago

@SantoshSrinivas79 I'm sorry you experienced this problem! Could you please try quitting the apps one by one when this happens until espanso is enabled again? Hopefully, that way we can identify the culprit...

tclancy commented 3 years ago

Just to add to this, I never saw this issue with 1Password until this week; I notice there was a new update this week that may be relevant..

EDIT: so much for that. In my case it was Microsoft Teams which is poison on OSX.

ioreg -l -w 0 | grep SecureInput is . . . kind of helpful for finding the culprit. So is closing things one by one as suggested above.

federico-terzi commented 3 years ago

@tclancy Thank you for the investigation! I never considered Teams as a possible culprit, very helpful

ioreg -l -w 0 | grep SecureInput is . . . kind of helpful for finding the culprit. So is closing things one by one as suggested above.

Espanso already uses this mechanism for detecting a possible culprit for SecureInput, but unfortunately, as far as my testing goes, it's not reliable if SecureInput is enabled in the background. In that case, the previous command will indicate the app that was in the foreground as the culprit instead of the actual one...

camilovietnam commented 1 year ago

Just my experience: I had to close Microsoft Teams and Calendar, one of these two did the trick.