replacing NNN with the number after kCGSSessionSecureInputPID= from the first command. The output of that command will have a bunch of stuff in it, but the important bit is kCGSSessionSecureInputPID=NNN where NNN is the ID of the process(es) that are using Secure Input.
LOGINWINDOW HAS DISABLED TEXTEXPANDER FULL
Here's the jsavin's full answer from the forum thread above (the fragment above is not enough to find the offending login process): After running into this issue many times and not finding good solutions short of logging out and back in again, I finally found a () that can help figure out what process is using Secure Input: But in fact it was Google Chrome, and Textexpander was just fooled for some reason. I once tried sudo killing the process and my computer just sort of paniced and logged out or something. Textexpander upon login, complained that the culprit was the loginwindow process. I was able to notice because I use an application that informs me of this (namely Textexpander stops working and shows in status bar icon that it is disabled and my Logitech mouse and keyboard settings don't work, and other weird things happen, also running ioreg -l -w 0 | grep SecureInput gives out some output if it's enabled, and nothing if it's disabled). I tried closing Chrome entirely, and it worked, then I reopened it and secure input was enabled again, then I specifically closed the tab with the login input page, and secure input was finally disabled. For me the problem was Google Chrome browser, and specifically that I had a tab with a login input page that I left open without really doing anything.
0 kommentar(er)
