Q: Aperture 3.24 crashes after update
-
Jun 1, 2012 5:29 PMby William Lloyd,If you bought it on the Mac App Store and somehow something went wrong (it sorta looks like this is the case), you don't need to use Time Machine at all.
Just delete Aperture from your Mac (select it in Finder, press command-Delete, and then enter your password. Or on Lion you can just click and hold in Launchpad and press the X in the upper left when it starts wiggling).
Anyway, then go to the Mac App Store, click the purchases tab, and re-install Aperture.
-
Jun 1, 2012 7:24 PMby léonie,That crash log is very typical: The PluginManager.framework is missing from your System Library. For this particular framework this happens in most cases by installing Final Cut. Have you Final Cut installed?
The recommended, safest solution to fix the library is to reinstall the operating system, using the latest combo update from the support downloads page , see this Support article:
Aperture 3.x: Aperture unexpectedly quits if Final Cut Express 4 is installed:
http://support.apple.com/kb/TS3528
It might be less trouble, to replace just the /Library/Frameworks/PluginManager.framework from the latest Time Machine backup, before the trouble started (if you indeed did install Final Cut), but the recommended procedure is to reinstall the OS.
Regards
Léonie
-
Jun 1, 2012 7:35 PMby bit-mover,Hmmm. "Reinstall the app." I did think of that of course, but two things stopped me: The original install worked fine for a couple of weeks right up until this software update today. The Aperture installation does not write the file:
/Library/Frameworks/PluginManager.framework/Versions/B/PluginManager
I proved this with an installation on another machine. So, if the update broke that file, then an app reinstall won't fix it. The second thing that stopped me is I'm temporarily on a very slow internet connection and I'm looking at a 6 hour download to reinstall.
Seems pointless to reinstall under those conditions, no?
That's why I was going for restoring (at least that library file) from a TM backup.
Need a solution that's a bit more astute this time, but thanks.
-
Jun 1, 2012 9:38 PMby léonie,So, if the update broke that file, then an app reinstall won't fix it.
No, the MacOS update does not corrupt the Plugin Manager Framework. Installing other Applications may do it. See my post above - did you install any other multi media Applications?
If you are on a very slow network, reinstall the Framework from the Time Machine Backup. That has been proven to work previously. To find the Library quickly when diving back in time on your Time Machine add it to the Finder Sidebar before opening Time Machine.
-
Jun 2, 2012 2:32 AMby bit-mover,No other applications were installed between having Aperture working and not. In fact, it was working the hour before the update, then the update, then not working...nothing else installed or changed. I do have Final Cut Studio 5 (not Express), but that was installed before Aperture, and Aperture has worked since. At this point my only real choice involves Time Machine, as I don't have my OS install disc with me.
I'd sure like to know what corrupted the library framework file, though. I'm trying to commit to using Aperture to manage a library of almost 50,000 images, but so far there have been quite a few bumps in that road, this one being the most recent. Just building the library took a couple of days, and if this is a simple fix, great, but Aperture has cost me a ton of time so far. Hope this works, and stays that way!
Thanks for your help.
-
Jun 3, 2012 8:35 AMby bit-mover,No. I don't have a list of the updates, there were a bunch. No Final Cut, though. Probably since I have FCP Studio v5, which is quite old. I also understood the final cut issue to be Final Cut Express releated.
This might help though. The date on the corrupted PluginManager file was 2006. The date on the one in the backup was 2010. Not sure how that could be.
-
Jun 3, 2012 9:06 AMby léonie,The date on the corrupted PluginManager file was 2006.
The date on the one in the backup was 2010.
The date on the corrupted PluginManager file matches my Final Cut Pro installation (early 2007); The date on the one in the backup matches all three of my current installations (iMac, MBP).
Do you have Aperture plug-ins installed? Some have relatively old code.
But as you do not remember exactly which applications are newly updated, it is hard to guess, what reinstalled the outdated framework.
-
Jun 3, 2012 6:37 PMby bit-mover,...And here's the answer: The update that replaced the PluginManager file is the current Compressor update for FCP 5. I just ran Software Update, it wanted to update Compressor. I did the update, launched Aperture and it again crashed, same problem. So the update re-wrote the PluginManager file, and killed Aperture, contrary to popular mythology which says this isn't possible.
Interestingly, the update also found the clean PluginManager file copy I had on my desktop and trashed it too, causing me to have to go back to the TM backup again for a working copy of the file to restore Aperture.
Sweet. So Software Update for Apple's own products kills their own app, and it's the most recent Apple product I have.
So, Apple, if you're listening, here are the conditions where this is a problem:
OS 10.6.8 (have to run this because of the version of FCP I have)
Final Cut Pro Studio HD v5.x
Aperture 3 - current version
Software Update wants to update Compressor, which is part of the FCP suite, and in doing so installs an incompatible version of the PluginManager file.
My solution is to not accept FCP updates any more, and keep a working copy of PluginManager somewhere, probably renamed so it won't be deleted by SU again.
For reference, I'm running FCP 5 because I cannot afford to upgrade to V9, which is the last full version that opens legacy projects, and includes DVD Studio. The current FCP won't open any projects that it hasn't created (dumb!), and no longer includes any disc authoring (again, dumb!), which still is my main releast format, yes, even in these days of streaming and downloads.
Long term, I'll probably have to move to an Adobe product for video...again, and for the last time, DUMB!
-
Sep 20, 2012 2:54 PMby Frozenfire1,Last night I installed the OS 10.8.2 on both my iMac Quad Core and MacBook Pro without incident, then the Aperture 3.4 update. Upon the first launch on my MacBook Pro, I got a warning that I must run Photo Library First Aid (Repair Database was the preselected choice). Now it seems to run OK there. On the iMac, the library seems to remain corrupted even though I performed the repair, ran the Mac disc utility, and Onyx.
My question is: did the library itself get corrupted, or is it a glitch in the app upgrade?
-
Sep 20, 2012 3:36 PMby Frozenfire1,At launch, Aperture shows the usual "Opening Aperture Libraries". Then an error message pops up which says, "Aperture Quit Unexpectedly" along with a lengthy report. It states that the message will be sent to Apple automatically. If I keep re-launching, a pane opens which invites me to repair the Aperture Library. When I activate that, it goes to completion and then Unexpectedly Quits again.
I'm not that well versed with Time Machine, but following the instructions in my two Mountain Lion handbooks I was able to find a time yesterday prior to downloading the Aperture update. I restore from that time and it makes an "original" version of the Aperture icon. When I try to launch that, a pane opens which says "Aperture Library can't be loaded because it is from a newer version of Aperture." These error messages keep alluding to the library, not the app itself, that's why I'm confused.
The good news is that when I run iPhoto and click Show Aperture Libraries, I can see all the RAW images I have stored in Aperture, so I know they're still there.
With all these error messages that are automatically being sent to Apple by me and others, I hope they publish a fix for this glitch. My work depends on these images!
