Previous 1 2 3 4 Next 78 Replies Latest reply: Nov 28, 2012 4:09 PM by FarNorth_1 Go to original post
  • Pachacor92 Level 1 (0 points)

    i find the file with 'easy find' and remove it

    It works perfectly for me now

    many thanks from France

  • Dragon9 Level 1 (0 points)

    Thanks for a solution that works for this problem, I removed the file and all works well.

  • fof Level 1 (0 points)

    Deleting the plist file did NOT improve the situation for me. I can start Aperture from a different user account, but not from mine, neither after deleting the plist file, rebuilding the library, and even a re-install of Aperture.

    The problem is not associated with an error in the Aperture Library, because it also exists when no Aperture Library is present: Crash on start. No matter what I tried, there is no way to access my images with the updated Aperture.

  • léonie Level 10 (85,225 points)
    Deleting the plist file did NOT improve the situation for me. I can start Aperture from a different user account, but not from mine, neither after deleting the plist file, rebuilding the library, and even a re-install of Aperture.


    Then you better start a new thread - repeating this post and all fixes you tried sofar, and adding a crash log - the the first 50 lines + the crashed thread.


    The reason for your crashes might be something completely different.

  • David Gordon Level 1 (115 points)

    Are you sure you have deleted the correct plist in _your_ user account? There are two Libraries, make sure you are in /YourUserName/Library/Preferences and not Macintosh HD/Library. Your Library is hidden by default, access by holding down the alt key and look in Go menu in Finder.

  • fof Level 1 (0 points)

    yes of course I deleted the right plist...

  • David Gordon Level 1 (115 points)

    Can you open your Aperture Library while in the other user account?

  • léonie Level 10 (85,225 points)

    But since Aperture is running correctly from a different User account (did you try it with your Apperture Library?), something in your user library must be causing the problems.

    The usual suspects are:

    • Aperture's user preferences (you checked this)
    • The Caches
    • your Aperture presets
    • your startup items


    You could start by deleting the contents of Aperture's cache:



    Then move your presets to the Desktop and move them back, one by one

    ~/Library/Application Support/Aperture/



    Disable "Startup items" from "Users&Groups" in the System Preferences



  • fof Level 1 (0 points)

    Yes, I can open Aperture in a different user account. I also can open my Aperture Library from there, after I moved it to /Users/Shared and let Aperture repair the permissions opon start. In this way at least I can access my images.

  • fof Level 1 (0 points)


    I deleted everything you suggested, and more ;-) but the problem persists. Actually I deleted everything that had to do with Aperture and reinstalled from scratch. Did not help. I renamed the Aperture Library (file extension) so that it is no longer recognized by Aperture. Did not help. I created a new, empty Library. Did not help. I moved the Library to /Users/Shared, and opened it from another user account. After repairing the permissions, it worked with no problem at all. Thus, the problem is not with the Library.


    Also, I tried to start Aperture after Safe Boot, which does not work because the driver for the graphics card is not being loaded and Aperture consequently says that the graphic card does not meet Aperture's requirements.

    After normal restart, Aperture took longer to load, and then crashed again.

    Ich könnt kotzen...

  • léonie Level 10 (85,225 points)

    Ich könnt kotzen...

    better not - wan't help


    I tried to start Aperture after Safe Boot

    Safe boot at least will clear caches and reset parameters, no bad move.


    Post the crash log - the the first 50 lines + the crashed thread.

    Also look at the Console window, if there are disgnostics (at the time, Aperture launches).

  • fof Level 1 (0 points)



    There is nothing obvious in the Console, except that it says that a crash log has been written.


    These are the first 50 lines of the crash log:


    Process:         Aperture [329]

    Path:            /Applications/


    Version:         3.4 (3.4)

    Build Info:      Aperture-301036000000000~2

    App Item ID:     408981426

    App External ID: 10581304

    Code Type:       X86-64 (Native)

    Parent Process:  launchd [165]

    User ID:         502



    Date/Time:       2012-09-20 15:46:40.680 +0300

    OS Version:      Mac OS X 10.8.2 (12C54)

    Report Version:  10



    Crashed Thread:  0  Dispatch queue:



    Exception Type:  EXC_BAD_ACCESS (SIGSEGV)

    Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000



    VM Regions Near 0:


        __TEXT                 000000010cde9000-000000010d53b000 [ 7496K] r-x/rwx SM=COW  /Applications/



    Thread 0 Crashed:: Dispatch queue:

    0                0x000000010f02792b CFRelease + 379

    1                0x000000010f0bea12 CFURLCreateFileReferenceURL + 850

    2                0x000000010f0e66d6 -[NSURL fileReferenceURL] + 102

    3                    0x00000001111312dd -[NSFileManager componentsToDisplayForPath:] + 102

    4                       0x000000010dafc13e +[RKImageCaptureManager defaultImageCaptureApplicationPathAndAllCandidateApplications:] + 371

    5                      0x000000010ce448b5 0x10cde9000 + 374965

    6                0x000000010f06447a _CFXNotificationPost + 2554

    7                    0x000000011106d846 -[NSNotificationCenter postNotificationName:object:userInfo:] + 64

    8                        0x0000000111c5060d -[NSApplication _postDidFinishNotification] + 292

    9                        0x0000000111c50346 -[NSApplication _sendFinishLaunchingNotification] + 216

    10                        0x0000000111c4d532 -[NSApplication(NSAppleEventHandling) _handleAEOpenEvent:] + 566

    11                        0x0000000111c4d12c -[NSApplication(NSAppleEventHandling) _handleCoreEvent:withReplyEvent:] + 351

    12                    0x000000011108712b -[NSAppleEventManager dispatchRawAppleEvent:withRawReply:handlerRefCon:] + 308

    13                    0x0000000111086f8d _NSAppleEventManagerGenericHandler + 106

    14                            0x0000000114ee4b48 aeDispatchAppleEvent(AEDesc const*, AEDesc*, unsigned int, unsigned char*) + 307

    15                            0x0000000114ee49a9 dispatchEventAndSendReply(AEDesc const*, AEDesc*) + 37

    16                            0x0000000114ee4869 aeProcessAppleEvent + 318

    17                     0x000000011313a8e9 AEProcessAppleEvent + 100

    18                        0x0000000111c49916 _DPSNextEvent + 1456

    19                        0x0000000111c48ed2 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 128

    20                      0x000000010d25d00d 0x10cde9000 + 4669453

    21                        0x0000000111c40283 -[NSApplication run] + 517

    22                        0x000000010f95d324 NSProApplicationMain + 378

    23                      0x000000010cdf89c2 0x10cde9000 + 63938

    24                      0x000000010cdf8314 0x10cde9000 + 62228

  • léonie Level 10 (85,225 points)

    Do you have any third party Notification software installed - Growl or something similar?


    Aperture is crashing when it is trying to post the finish notification in the Notification center and reading your user information, that is probably why it is crashing only in your account.


    7                    0x000000011106d846 -[NSNotificationCenter postNotificationName:object:userInfo:] + 64


    Also it is trying to construct the path to your default image capture application: Which application have you set to open, when a camera is connected? Image Capture? iPhoto? Aperture? You might try to change this temporarily to "image Capture" by opening Image Capture and setting the preferences.


    [RKImageCaptureManager defaultImageCaptureApplicationPathAndAllCandidateApplications:] + 371




  • bomilcar Level 1 (0 points)

    Out **** Standing.  You guys are just great.  Messed with it for 3 hours yesterday before I found your information this morning and it worked just perfectly. Thanks from New Mexico.



  • léonie Level 10 (85,225 points)

    Added: If the notifications - or any other third party installations are the problem, inspect your start up items in the "System Preferences > Users & Groups" panel for your acconut. Disable anything you do not really need and log off and log in again.


    And I can't tell from your answers sofar, if you already tried to reinstallfrom your original installation media and to upgrade directly to the current version. That solved the problem for quite a few posters already.

Previous 1 2 3 4 Next