1Password 5 stopped working after security update

janine
janine
Community Member

Tonight I installed Security Update 2015-002 for Yosemite and Xcode 6.2, and immediately after doing so 1Password stopped working. When I try to launch the app, it immediately hangs without any app window appearing and has to be force quit. I have seen it do this before, after a botched update, so I downloaded a fresh copy of the app from your site and copied it to /Applications. No change, even after a restart.

I have the crash log from the "report" dialog, but it's much too large to paste here.

Is there anything else I can do to help you diagnose this? I've checked the console and there don't appear to be any messages being generated when 1Password tries to start.

Comments

  • Stephen_C
    Stephen_C
    Community Member

    Did you actually follow this procedure for the reinstall?

    1. Drag the 1P app to the trash (don't use any app cleaner tool, which is likely to try to delete files you need to keep).
    2. Empty the trash and reboot.
    3. Re-download and re-install 1P.

    Stephen

  • janine
    janine
    Community Member

    Sort of... I renamed the old version and installed the new one, so that I could compare the two (they seem to be identical). I have rebooted several times. I have started 1Password both by clicking on the Dock icon (which points to the newly installed version) and by double-clicking on it in Finder; it hangs either way.

  • janine
    janine
    Community Member

    A bit more info:

    I don't know what I was looking at last night, but there is output in the Console when 1Password is trying to launch:

    3/11/15 9:49:54.452 AM xpcproxy[1415]: CFPreferences could not connect to its daemon.
    Preferences using the connection 0x0 will be volatile and will not be persisted to disk.
    3/11/15 9:49:54.786 AM com.apple.xpc.launchd[1]: (2BUA8C4S2C.com.agilebits.onepassword4-helper[1415]) Service exited due to signal: Trace/BPT trap: 5
    3/11/15 9:49:54.786 AM com.apple.xpc.launchd[1]: (2BUA8C4S2C.com.agilebits.onepassword4-helper) Service only ran for 0 seconds. Pushing respawn out by 10 seconds.
    3/11/15 9:49:54.793 AM ReportCrash[1406]: Saved crash report for 2BUA8C4S2C.com.agilebits.onepassword4-helper[1415] version ??? to /Users/johmer/Library/Logs/DiagnosticReports/2BUA8C4S2C.com.agilebits.onepassword4-helper_2015-03-11-094954_Janines-MacBook-Pro.crash
    3/11/15 9:49:54.795 AM ReportCrash[1406]: Removing excessive log: file:///Users/johmer/Library/Logs/DiagnosticReports/2BUA8C4S2C.com.agilebits.onepassword4-helper_2015-03-11-094628_Janines-MacBook-Pro.crash

    At this point there is a pause, and then the above repeats. Eventually if you let it sit long enough it times out with an error dialog:

    1Password failed to connect to 1Password mini
    Please restart 1Password. If this does not help, please contact AgileBits support.

    I then tried clicking the 1Password button in Safari. This gave me a "Looking for the 1Password app" dialog and then a crash; I didn't save the crash log (sorry) but it was about CrashReport.framework not being launched because of a missing image. I could swear this was the same error I have seen before from a bad auto-update of 1Password, but that was solved by reinstalling from download, which I have already tried.

    I tried deleting and reinstalling the 1Password extension in Safari. This got rid of the crash when starting Safari, but not the "Looking for the 1Password app" dialog when I click the 1Password button.

  • AGAlumB
    AGAlumB
    1Password Alumni
    edited March 2015

    @janine: Sorry for the trouble! It looks like 1PasswordMini is having trouble running for some reason -- possibly some permissions were changed by the update.

    The best thing to do in this case is to send email to support+mac at agile bits dot com with the saved crash report from Users/johmer/Library/Logs/DiagnosticReports/. It will end in .crash, and the most recent should be fine, as they are most likely identical. Just attach it to your message and include a link to this forum post for context, and we'll get this sorted out for you! :)

This discussion has been closed.