Safari Extension stuck in "Initializing..."
Jens
Hello!
Since I updated to Version 3.9.2, the Safari Extension is stuck in "Initializing.." when I try to unlock it.
I have read the older posts about this problem, but non of the
workarounds work for me.
I have not changed my master password.
I uninstalled the extension and reinstalled it, no success.
I reseted safari, no success.
Is there anything else I can do?
Thx
Jens
Comments are currently closed for this discussion. You can start a new one.
2 Posted by Walter on 25 Nov, 2011 10:44 AM
Same here: I upgraded yesterday to Tiger / Safari 5.1.1 and now I'm stuck.
Can't believe we are the only ones …… AgileBits are you listening?
Walter
3 Posted by Mark on 25 Nov, 2011 01:08 PM
Every few weeks since Lion came out I give Safari another chance, but every time there is some problem with 1Password. This time I'm getting the initializing thing. Is 1Password ever going to work with Safari again, or will it be vaporware forever?
4 Posted by Walter on 25 Nov, 2011 02:15 PM
«Same here: I upgraded yesterday to Tiger / Safari 5.1.1……»
oops, I meant Lion NOT Tiger ……
Walter
5 Posted by Jamie Phelps on 26 Nov, 2011 09:32 PM
Hi, Jens, Mark, and Walter. I'm sorry for the trouble you're having. If you've already tried deleting the Safari extension and reinstalling it, it sounds like this might be a permissions issue. Using your browser, please download a standalone tool to run from the following link:
http://i.agilebits.com/ms/tools/reset_folder_permissions.zip
After the download is complete, use the Finder to locate it in your browser's download folder. If the browser has not already expanded the ZIP archive file then please double-click it to force it to be expanded.
The result will be a Unix Executable File script named reset_folder_permissions. Double-clicking that script file will cause a Terminal utility window to appear, and the tool will run it for you. You will be prompted to enter your OS X Admin password (what you would use to login to your Mac's account, or to install system-level software).
Any output seen in the Terminal window may help to determine additional problems with permissions on your system that could impact 1Password. Please copy the entire output (easy way: Command-A, followed by Command-C) and paste it into a response for us to look at.
It may be that running this script will allow the extension to get its components into place and start properly.
I hope that helps. Please let us know if we can be of further assistance.
6 Posted by walter rohrbach on 27 Nov, 2011 02:04 PM
Hi Jamie
thanks for your help, but no luck at all. Could it be that my OS and Safari are in German ?
regards Walter
here is the copy of the terminal output:
> Last login: Sun Nov 27 14:28:44 on console
> MacBook:~ wr$ /Users/wr/Desktop/reset_folder_permissions ; exit;
>
> Please report all output you see here!
>
> /Users/wr/Desktop/reset_folder_permissions standalone release 1.1.2
>
> Folder permissions will be reset to support 1Password
>
> Please ignore any messages like the following:
>
> chmod: No ACL present ...
>
> If prompted for a password, please enter your Mac OS X Admin password
> (it will not echo as you type, so just type it and press return at the end).
>
> Password:
>
> The folder permissions have been reset.
> Please restart 1Password and any open browsers.
>
> Please copy the entire contents of this window (use Command-A, then Command-C)
> and paste that into a reply to [email blocked] so we can see it.
>
> Once you have done that you can press RETURN in this Terminal window to
> end the script.
>
> Press the RETURN key after copying the output:
7 Posted by Tagaloa on 27 Nov, 2011 05:33 PM
Same Here. German version of Mac OS Lion. The Error showed after installing Lion (no problems with Snow Leopard)
No changing of the Master Password.
The reset_folder_permissions script did not help at all.
Still waiting for an update or work around.
8 Posted by Tagaloa on 28 Nov, 2011 06:10 AM
Some additional information, which might be helpful:
The Firefox Add-on still (Version 3.8.7) works perfectly. So it's probably not a problem of folder permissions.
9 Posted by Jens Reimann on 28 Nov, 2011 09:25 AM
Hello!
Running the folder permissions script did not work for me. sorry.
Here is the output:
Last login: Mon Nov 28 09:23:40 on console
/Users/reimannje/Downloads/reset_folder_permissions ; exit;
Mac:~ reimannje$ /Users/reimannje/Downloads/reset_folder_permissions ; exit;
Please report all output you see here!
/Users/reimannje/Downloads/reset_folder_permissions standalone release 1.1.2
Folder permissions will be reset to support 1Password
Please ignore any messages like the following:
chmod: No ACL present ...
If prompted for a password, please enter your Mac OS X Admin password
(it will not echo as you type, so just type it and press return at the end).
Password:
The folder permissions have been reset.
Please restart 1Password and any open browsers.
Please copy the entire contents of this window (use Command-A, then Command-C)
and paste that into a reply to [email blocked] so we can see it.
Once you have done that you can press RETURN in this Terminal window to
end the script.
Press the RETURN key after copying the output:
10 Posted by Mike Tselikman on 29 Nov, 2011 09:19 PM
Wait, is there anybody here that isn't running a German locale on OS X?
Jens, are you also using OS X with German locale?
@Tagalloa, the extensions and its 1Password database are stored in the separate folders for each browsers, so having it work in Firefox doesn't exclude the possibility of a folder permission.
In order to help us narrow this down, we need you guys to send us your diagnostic reports, so that we can look at it. Since this discussion is public, I'd like to ask you all to send us your report at support @ agilebits.com with a link to this discussion.
Thanks!
11 Posted by Jens Reimann on 30 Nov, 2011 08:56 AM
Hello!
My OS X (Lion btw.) is in english with german keyboard and date and number settings and so on.
I also send the requested report to [email blocked]. I hope this helps.
Thx
Jens
12 Posted by Mike Tselikman on 01 Dec, 2011 08:46 PM
Hi Jens,
Thanks for sending in your report.
According to Jen's report, an older 1Password Agent (from the older 1Password 3.8) is running next to 1Password Helper that's in 1Password 3.9. This can definitely block 1Password from working correctly in Safari.
This can happen if 1Password 3.8 was not updated first before upgrading to 1Password 3.9 as we made 1Password 3.8 smarter in the later updates to kill itself when it detects 1Password 3.9 is running.
To fix this, please open Terminal.app in your Applications > Utilities folder and then enter the following command in one line;
launchctl unload -w ~/Library/LaunchAgents/ws.agile.1PasswordAgent.plistAfter this, I'd recommend restarting your Mac. This should then let 1Password work in Safari.
I hope this helps, please let me know.
Thanks!
13 Posted by Jens Reimann on 02 Dec, 2011 09:21 AM
Hi!
Woohoo!! This did it for me.
And not only that, but the universal unlock feature now works as expected.
I had some problems with that too, but never payed much attention.
Thanks a lot for your support. That was awesome work.
Thx
Jens
14 Posted by Brandt Swindell on 02 Dec, 2011 12:44 PM
Hallo Jens,
On Mike's behalf, you are very welcome! I'm very glad his suggestion did the trick. :)
Also, thank you for the kind words. We are here to help, and I hope you will let us know if we may be of assistance in the future.
Vielen Dank!
Brandt
15 Posted by Tagaloa on 06 Dec, 2011 08:11 AM
Well, it does the trick for me too, finally. :-)
Thanks for the great support and keep up the good job!
16 Posted by Brandt Swindell on 06 Dec, 2011 01:57 PM
Hi Tagaloa,
Excellent news! Thanks for updating the conversation with your success. :)
I hope others having the same issue will try Mike's suggestion.
Cheers!
Brandt
17 Posted by Lawrence on 12 Dec, 2011 10:34 PM
I was having the exact the same problem in the last two weeks or so. I am glad I have checked this web page. Mike's suggestion also worked for me. Thanks!
18 Posted by Mike Tselikman on 12 Dec, 2011 10:43 PM
Hi Lawrence,
Thanks for the update, I'm glad this works.
I'll close this discussion for now. If anybody has the same issue and my suggestion doesn't work, please create a separate discussion, so that we can help you further.
Thanks everybody for their help in this.
Mike Tselikman closed this discussion on 12 Dec, 2011 10:43 PM.