“Now is the time to do anything” - someone
I finally reserved some time to fix the annoyance that 1Password has been bugging me with since the past few months. yes months!
Starting from first, I was one of the users who contributed to the usage of Safari on a Mac. Better late than never, I fell in <3 with the Chrome Browser. 1Password was the best combination with it. I upgraded 1Password with the AppStore version. I think its since late Nov/December 2011.
The annoyance - 1Password was not able to connect to the helper and does not allow me to navigate via keyboard shortcuts. The user guides were useless. I did want to run the troubleshooter and pass on information to Agile. Today was the day my frustration about this reached its peak and I decided to debug the issue for myself. Running the 1PasswordTroubleShooting.app , looking at the helpers that are running.
Something struck me because one of the help menu says that it will fix login/startup items. Looking at the process which is an app running from Application Support instead of the new awesome Appstore’d , /Applications/1Password . That little prick !
~/Library/Application\ Support/1Password/Agent/1PasswordAgent.app
moved it out of there and put a shot in the head to running application (kill -9 pid). Tada !
Technical Details: If you are using the AppStore version of 1Password and see that this agent is running. Move the application to some other place safe (/tmp) and kill the pid. Now you could see another 1PasswordAgent running from /Applications/1Password.app/ .
Update: Information on permanently unloading the file. Thanks 1Password@ !
@macmini_in launchctl unload -w ~/Library/LaunchAgents/ws.agile.1PasswordAgent.plist
— 1Password (@1Password) March 9, 2012