The system launched an incorrect version of 1Password mini.
The system launched an incorrect version of 1Password mini.
Instead of '/Applications/1Password.app/Contents/LoginItems' it started '/Volumes/Clone iMac/Applications/1Password.localized/1Password.app/Contents/Library/LoginItems'.
1Password Version: Not Provided
Extension Version: Not Provided
OS Version: OSX 10.11
Sync Type: Dropbox
Referrer: forum-search:The system launched an incorrect version of 1Password mini. Instead of '/Applications/1Password.app/Contents/LoginItems' it started '/Volumes/Clone iMac/Applications/1Password.localized/1Password.app/Contents/Library/LoginItems'.
Comments
-
I suspect you have a backup drive permanently connected to your Mac. This knowledge base article covers the situation:
How to remove multiple, conflicting copies of 1Password from your system
Note the last section about backup drives. The solution (if you wish to have the backup drive permanently connected) is to:
- delete any copy of the 1Password app file (only) from the backup drive; and
- exclude the 1Password app file from any further backups (because, of course, you can always re-download it if you need to).
Provided you don't use any app cleaner tool when deleting the app file none of this will interfere with your 1Password data.
Stephen
0 -
One user has reported that excluding the backup drive from Spotlight searches eliminates this OS X problem. You do that in the Spotlight part of OS X settings. I'm testing that possibility myself now. I don't think it used to work. But perhaps it does in more recent versions of OS X.
0 -
It looks like Stephen and Hawkmoth have already given you some good information about the error message your getting. I just wanted to add that this problem is actually due to a strange issue in Yosemite and El Capitan which causes it to open the wrong copy of 1Password mini when it finds multiple copies of the 1Password app. In this case, it's finding the other copy on your backup drive. Unfortunately there's not much we can do because OS X determines which instance of 1Password mini to run, despite us telling it the right one. This must be fixed by Apple on the OS level. It doesn't affect many apps because not many apps are running two separate components at the same time.
To avoid this issue, you can delete the 1Password app from your backup volume (and if possible, exclude the 1Password app file from future backups). Your actual 1Password data is stored elsewhere on your Mac, so that will still be backed up. If necessary, you can always download a new copy of the app from our website.
I hope that helps, but if you need anything else, please let us know. We're here for you! :)
0 -
Getting the error to the effect - the version of the mini app doesn't match the 1Password app that was launched. This is due to 1Password finding the mini app out on a mirror backup drive.
I am unwilling to disconnect my mirror backup drives just because agilebits is unwilling to put a few lines of code into their app to check that 1Password and its mini app only launch from the boot drive (or at least give us the option to tell it not to).
I consider this a bug.
Any other opinions on this matter?1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided
Sync Type: Not Provided
Referrer: kb:remove-multiple-apps0 -
If it's a bug, it belongs to Apple, not AgileBits. It's a defect in how the latest versions on OS X go about finding things like mini, which is contained in the application bundle. OS X goes too far afield in looking for mini, even though 1Password tells it where mini resides.
At least one user has reported that excluding the attached backup drive from Spotlight searches cures the problem. I'm testing that myself now, but it's probably going to require a 1Password update before I can tell if it works. The backed up version of the app is the same as the current release for now.
Until I began to test to see if excluding the backup drive from Spotlight searches works, I've just excluded the 1Password application file (and only that file, not any of the supporting files like the ones containing my local backups) from my daily backups with Carbon Copy Cloner. Excluding the application isn't a really issue, since users can download a fresh copy whenever they wish.
0 -
How about agilebits adding code to look for mini in the same place if launched the main app in - as in /Applications ?
Any chance of getting this in an update sometime?
I have a 2nd HD which is a mirrored copy of my boot drive (I use ChronoSync) which is also internal and mounts at the same time as the boot drive. I also have 1Password auto launch. I am not too interested in messing with my bootup sequence just for 1Password to behave.
One thought I have (since this just started happening after I updated my 1Password to 5.4(.1 ?) build 540047) is that the update actually goofed on where to point to the mini.
Seems to make more sense to me that 1Password be a little smarter as to where it updates and launches stuff from. /Applications seems like the most convenient default.
Thoughts? Possibilities?0 -
As you're using Chronosync it should be easy to exclude 1PW from being copied. After all, you don't actually NEED copies of the application.
The problem is that 1PW uses Apple's launchd to get its Mini. And the bug is in launchd which certainly ought to look in Applications first but does not.
0 -
Hey @persojm,
First off, this is not a bug but rather a feature built in to OS X that allows it to find things anywhere (a very useful feature, at that). The version of the feature most people see is Spotlight, but there are others, in this case
launchd. As hawkmoth noted, excluding the backup of 1Password from Spotlight tends to fix this issue. This post goes into a bit of detail on that particular task. You shouldn't have to disconnect your drive or do any other fancy stuff in order for the app to continue working properly.Let us know if you have any questions about this. :)
0 -
Hi @persojm,
How about agilebits adding code to look for mini in the same place if launched the main app in - as in /Applications ?
That's actually the way OS X worked prior to 10.10 (Yosemite), but there was a change to the OS and now it tries connecting to any copy of 1Password mini it finds, instead of limiting the search to the same 1Password app bundle you opened, or the Applications folder. Danco is correct that this has to do with launchd - there's really nothing we can do to convince that to launch the correct copy of mini.
There's a more in-depth explanation from one of our developers about how it all works in this post, if you're interested.
I am not too interested in messing with my bootup sequence just for 1Password to behave.
You shouldn't need to do that. You just need to make sure there's only 1 copy of the 1Password app (which means deleting any other copies from other drives) and exclude the 1Password app from being copied to the other drives. Your 1Password data is stored separately from the app, so that data will still be copied via ChronoSync. As Danco said, you don't need extra copies of the app bundle - you can always redownload that.
One thought I have (since this just started happening after I updated my 1Password to 5.4(.1 ?) build 540047) is that the update actually goofed on where to point to the mini.
This problem has been happening for well over a year now, ever since Yosemite betas were first released. It's not specific to 5.4 or 5.4.1, although it's possible you haven't experienced the issue until now (the OS could have been choosing the correct copy of mini out of coincidence).
Seems to make more sense to me that 1Password be a little smarter as to where it updates and launches stuff from.
It's not up to the 1Password app. If it was, we would have solved this problem a long time ago! ;) We don’t actually launch 1Password mini: We trigger an event that causes OS X (launchd) to open 1Password mini, and launchd launches the wrong one. The post from our developer that I linked to above should help to explain this a little better than I can. But if you have more questions about that, please let us know! :)
0 -
I've owned both 1Password and SuperDuper for a very long time (at least 5 years), but I'm only experiencing this now, with this version.
I'm unwilling to "unplug my backup drive", potentially forgetting to plug it back in and screw up my backups, or mess with the volume table on my Mac when I plug it back in.
I'd prefer a better idea.
Please advise1Password Version: 5.4.1
Extension Version: 4.4.3.90
OS Version: 10.10.5
Sync Type: Dropbox
Referrer: kb:remove-multiple-apps, kb:error-connect-to-mini, kb:remove-multiple-apps0 -
Thanks to all for the informative background.
However, deleting a file from my Chronosync mirror defeats the purpose for which I even have a mirror bu - that is, to have an instant replacement of my boot drive should it ever fail (which it has for two other machines in the last couple of years).
Therefore, it looks like I'll have to live with it until Apple decides to fix the bug :(
Thanks again.0 -
I don't mind the feature - its the priority of where it seeks first.
I'll look into the post you mention.
I will be keeping my mirror copy as is because its there to provide an instant bootable image should my main boot image fail (which it has on a couple of other machines in the last couple of years).
Thanks for the link0 -
To circumvent this OS X problem there is no need to detach your backup drive. The solution (if you wish to have the backup drive permanently connected) is to:
- delete any copy of the 1Password app file (only) from the backup drive; and
- exclude the 1Password app file from any further backups (because, of course, you can always re-download it if you need to).
Provided you don't use any app cleaner tool when deleting the app file none of this will interfere with your 1Password data.
If you don't wish to do that—or have some difficulty excluding the app file from backups—others have reported that disabling Spotlight search on the backup drive may also work.
Stephen
0 -
Hi @persojm,
I just noticed we've been having this conversation with you in two different threads, so I've merged them into the same discussion to avoid confusion.
Hopefully we've answered your questions about all this and have given some good suggestions for how to avoid the problem! If you don't want to delete the 1Password app from your ChronoSync mirror, then hopefully the suggestion of excluding the backup of 1Password from Spotlight will help.
We're here for you if you need anything else! :)
0 -
Hi @trotsky,
I'm sorry you're getting that message when trying to launch 1Password! I hope you don't mind, but I've merged your discussion with an existing thread for the same issue.
Stephen's reply should explain other ways to avoid this problem. Some other posts in this thread also have details about that, as well as information about why this happens in the first place.
I hope that helps, but please let us know if you have more questions about that. We're always happy to help! :)
0
