Currently Being ModeratedAug 6, 2012 11:22 AM (in response to AlexBrown)
Great discovery, Alex,
thanks for posting this.
I have similar problems and tried your fix, but for me the debugger only turns up the name of my previous camera for some reason, no iPhoto albums.
06.08.12 20:04:25,979 Aperture: [<RKAlbum 0x1171c6bd0> valueForUndefinedKey:]: this class is not key value coding-compliant for the key minImageDate.
<RKAlbum: 0x1171c6bd0 > modelId = 576, uuid = 'KTxJyhwER8yx48TrV824IA' name='FZ 50', displayName='FZ 50'
Any idea, why Aperture might be complaining about my old Lumix FZ 50 r.i.p.?
Currently Being ModeratedAug 6, 2012 11:28 AM (in response to léonie)
You have an album called "FZ 50" - use the aperture search box to find it.
Currently Being ModeratedAug 6, 2012 11:39 AM (in response to AlexBrown)
You are correct! There it was - a smart album, long forgotten!
Removing it really stopped the error message, only now I have to find the next album.
Currently Being ModeratedAug 6, 2012 8:32 PM (in response to AlexBrown)
When I try this:
In the Terminal Application, run the following.
I get this:
No such file or directory
Currently Being ModeratedAug 6, 2012 8:39 PM (in response to AlexBrown)
I just had an additional idea.
I migrated from iPhoto to Aperture a year ago or more, and haven't used iPhoto since. I just noticed my iPhoto was back on 8.x and now there is 9.3 something.
I'm going to try upgrading iPhoto, and opening the iPhoto library in the latest iPhoto, and see if that improves anything. Probably a shot in the dark, but been meaning to check out iPhoto anyway now that everything is supposedly "unified" maybe my wife will still use iPhoto.
Currently Being ModeratedAug 6, 2012 9:39 PM (in response to giordajl)
No luck. Upgraded iPhoto to latest. That upgraded my iPhoto library rather quickly. But opening Aperture, still pinwheels and hangs on my primary library.
I have to use Switch to: and open a new, empty library to get Aperture to actually Launch.
Currently Being ModeratedAug 6, 2012 11:30 PM (in response to giordajl)
For my example to work, you need Xcode installed.
You can get it for free from the mac app store.
Currently Being ModeratedAug 6, 2012 11:32 PM (in response to AlexBrown)
Note that I have raised a bug with apple for this, and sent them a library containing just one photo that seems to show the problem. (bug 12034892).
Currently Being ModeratedAug 12, 2012 1:39 PM (in response to AlexBrown)
Aperture won't even let me select Keep Projects & Albums Arragned by Date!?
Currently Being ModeratedAug 20, 2012 10:14 AM (in response to AlexBrown)
My library has gone bad again-the albums I cloned To avoid the issue now cause the same problems as the originals.
Also my library frequently crashes an has to rebuild itself.
Next step may be to use AppleScript to see if particular types have a problem.
Currently Being ModeratedAug 20, 2012 10:15 AM (in response to giordajl)
If you mean sort by date doesn't seem to stick-that's precisely the signature of this problem.
Currently Being ModeratedAug 22, 2012 11:19 PM (in response to AlexBrown)
You sir are a certifiable genius!
One thing that may help in the debugging process where multiple albums are needed to be erradicated.
While in terminal, after typing "c" to continue:
^c (that is hold down the control key and the c key)
detach <PID of Aperture>
That allowed aperture to keep going without having to quit and restart it.
Once Aperture is running, keep repeating the "Keep Projects & Albums arranged by : Date" process and note the object number that appears in the console and then kill that album from within Aperture. Eventually, you'l get them all. You'll know you've got it when console messages stop appearing and when keeping albums arranged by date actually does just that in your library.
For me, the issues were all related to Smart Albums I had created. Made it somewhat easier as they were easy to just delete. I can recreate them later if I need to.
Currently Being ModeratedAug 22, 2012 11:30 PM (in response to AlexBrown)
Alex: In the library just repaired using your method, I still have one issue. If I go to add a new vault, the dialog box pops up that says:
"1 managed file will be included in this vault.
16628 referenced files will not be included. These need to be backed up separately.
Vaults provide automated backup of all original files stored inside your Aperture library. Original files for referenced images are stored elsewhere, and are not backed up in vaults.
Adjustments, ratings, and other metadata are included for all images, regardless of file location."
Thing is, all the master files related to this library are (supposed to be) referenced only. I create a Smart Album to catch only Managed Files and it comes up empty.
Any thoughts on how to locate, so I can then relocate, the 1 managed file hiding in the library?
Currently Being ModeratedAug 30, 2012 3:22 PM (in response to AlexBrown)
Hi, was hoping to have found the solution as to why Aperture keeps crashing on me when doing basic stuff like clicking on "New Smart Album" but unfortunately I seem to be less lucky.
Console gives me
*** Terminating app due to uncaught exception 'NSUnknownKeyException', reason: '[<RKAlbum 0x11fdc99e0> valueForUndefinedKey:]: this class is not key value coding-compliant for the key minImageDate.'
So it does look very similar to what is described here and I did import iPhoto libraries with albums and smart albums (multiple iPhoto libraries even and some of them twice at that... don't ask )
Unfortunately gdb gives me
(gdb) print-object 0x11fdc99e0
0x11fdc99e0 does not appear to point to a valid object.
I might be doing something wrong or I might have another issue altogether perhaps... any input is appreciated, thanks!