2BUA8C4S2C.com.agilebits.onepassword4-helper unexpectedly quitting after 4.2 update [fixed in 4.2.1]

RichBT

I have a family license for 1Password 4. After updating to 4.2, I'm getting crash reports (which I'm sending on to AgileBits) about 2BUA8C4S2C.com.agilebits.onepassword4-helper unexpectedly quitting.

To replicate:
Log into a user account on our computer that has 1Password in use by a family member.
Run 1Password
Log out of that user account.
Log back into that user account.
I get a crash report about 2BUA8C4S2C.com.agilebits.onepassword4-helper/

Jasper

Hi @RichBT,

Thanks for submitting the crash reports. They will be most helpful for finding the issue.

If you'd like, you could also send us a diagnostic report, which we could take a look at and see if there is anything wrong with your instance of 1Password. Please follow these instructions to send a Diagnostics Report, along with a link to this topic to: support+forum@agilebits.com

Thanks! :)

RichBT

Hi @JasperP‌

Done. I sent an email with a link to this discussion, a summary of the problem & attached a diagnostics report.

Additional details: there are three user accounts on our Mac that use 1Password (out of the five allowed under the family license). Two of these accounts (that includes mine) sync 1Password to Dropbox. These two accounts are where I had to reenable syncing after updating to 4.2 and where we're having this problem. In the third user account, 1Password does not sync to anything and the problem is not occurring.

We are running OS X 10.8.5; we're not quite ready to update to Mavericks for reasons unrelated to 1Password.

Jasper

We've received the report and will follow up through email. :)

ThomasV

Hello after upgrading to version 4.2 last evening I now get a crash error on restart or login every time. Saying "2BUA8C4S2C.com.agilebits.onepassword4-helper unexpectedly quit the last time it was run. Would you like to send a crash report to AgileBits?

This only happens however if I am syncing to a folder. If I disable syncing the issue does not occur. I had to reenable syncing after the update and then I noticed the error. I even ruled out the current vault being the issue because I had it sync to a new folder and create a new vault and the issue still occurs.

I am leaving syncing off for now. How does this affect me? I do not want to lose my data. I am backing up so I hope that means the data will be ok? I have submitted crash reports and will also email support+forum@agilebits.com with my diagnostics report and a screenshot of the error.

On a side note if I want to backup my 1Password data vault and move it to a new Mac, can one of the backup files or the keychain vault files that the application creates just be reimported into a new install of 1Password 4 and will that include all of the same data?

Thank You for your prompt response and assistance.

RichBT

Hi @ThomasV‌

I reported this earlier and started a discussion here:

http://discussions.agilebits.com/discussion/21877/2bua8c4s2c-com-agilebits-onepassword4-helper-unexpectedly-quit-problem-after-updating-to-4-2

RichBT

I have had a good exchange via email with one of the AgileBits Tech Ninjas.

After analyzing the diagnostics and crash reports, they have determined that this is a problem with running 1Password4 for Mac on OS X 10.8.5. A fix will be devised soon. I should keep an eye on the beta change logs and update to the beta that takes care of this issue or alternately wait for the stable 4.3 release.

In the meantime, it's not something to be worried about. When the helper crashes, 1Password4 will just start it up again automatically. An irritant but not something that affects the functionality of 1Password.

sjk

Hi @ThomasV,

I've merged your report of this issue with the similar one from @RichBT that he'd helpfully referred to. I see that Chris has similarly helped you with it in email and answered your question about moving your data to your new Mac. And we now all know it's expected this bug will be resolved in an upcoming 4.3 beta. :)

If there's anything else we can you with please let us know. Thanks!

bahob

I upgraded to 4.2 yesterday morning and used my Mac throughout the day and evening; 1P/Wd worked fine throughout.

Shut down last night, all "ok". Opened-up this morning, to be met by a screen wanting to send a crash report. No matter how many times i clicked on "Send" the screen did not actually send and would close down, reopening a few seconds later with a "ting" alarm !

Tried Force Quit 1 P/Wd - nothing changed. Shut down Mac and rebooted - nothing changed. Still have the Problem Report screen appearing, it won't go away, sits over anything else opened. 1 P/Wd does't work either, The Safari extension also doesn't work.

Should I just Time Machine back to the previous version ????????

I have emailed some screenshots to Support by way of further information.

RichBT

That was fast. Version 4.2.1 already has a fix to the helper crash running 1Password 4 for Mac on OS X 10.8.5 so I updated. No more helper crashes.

In my user account, 1Password correctly showed the last sync to Dropbox as 14 hours ago and resynced when I unlocked 1Password.

In the other user account on our Mac where this problem occurred, 1Password incorrectly reported as 'never synced' but at least it was pointing to the correct keychain in Dropbox and synced without further intervention on my part when I unlocked 1Password.

Thanks for taking care of this issue so quickly.

bahob

Thanks RichBT for the update information.

I have now downloaded 4.2.1 and installed and I am back up-and-running on OSX 10.8.5.

Thanks also go to a very Agile (Bits) response with the release of 4.2.1 !!

Megan

Hi @RichBT‌ and @bahob,

Thanks so much for letting us know that 4.2.1 fixed things up for you! I do apologize that it was a bit of a process for you there, but I hope things go smoothly for you from now on.

Of course, we're here if you hit any snags. :)

ThomasV

Thanks @RichBT, @sjk, Chris from Support, and @Megan.

I had downloaded 4.3 Beta 1 so it would not show version 4.2.1 as an available update when I checked today. So I just downloaded version 4.2.1 from the website and replaced version 4.3 Beta 1 that was in my Applications folder. I did some testing and everything seems to be good. So I wanted to say Thank you to AgileBits for the quick resolution! :) Have a Good one!

sjk

You're most welcome, @ThomasV, on everyone's behalf. :)

It's great to hear you've successfully resolved this issue, too, by manually reverting from 4.3.BETA-1 to 4.2.1. The next 4.3 beta build should include all the 4.2.1 changes. I'm sorry for any inconvenience with 4.2.1 being temporarily newer than the current beta.

RichBT

Hi @Megan‌

Hey, no problem. That's life with software.

Dealing with big companies can be a hassle - tech support script kiddies who don't actually read one's emails. In comparison, working with the AgileBits Tech Ninjas is a pleasure.

Thanks again for the quick fix. May all of you at AgileBits live long and prosper.

sjk

It's our pleasure to help, @RichBT. And I've passed along your kind words to the rest of our team, who I'm sure will enjoy actually reading them. :)

If anything else comes up you know where to find us. Cheers!