Skip navigation

Aperture 3.4 will not open after 10.8.2 installed

13471 Views 78 Replies Latest reply: Nov 28, 2012 4:09 PM by FarNorth_1 RSS
  • mickcolips Calculating status...
    Currently Being Moderated
    Sep 22, 2012 4:10 AM (in response to léonie)

    Thanks very much,advice spot on.

  • RoarinPenguin Calculating status...
    Currently Being Moderated
    Sep 22, 2012 8:52 AM (in response to obo23)

    This fixed the issue I was having, THANK YOU!!!

  • nrq Calculating status...
    Currently Being Moderated
    Sep 24, 2012 12:39 PM (in response to fof)

    fof wrote:

     

    ...

     

    * narrowed the problem down to a file "com.apple.ImageCapture2.E72B46F8-A66A-573A-A8E3-41E03286B385.plist" - after deleting this file, Aperture started up with no problem

    * opened that file, and found that it referenced to a helper program (actually a prefpane) I had installed, "Cameras" from Flexibits. That program was still a 32bit prefpane. It used to very very useful to set up which program would launch upon connecting a camera on a per-device basis (so e.g. Aperture would not start upon connecting an iPod with image, but would open when connecting my camera).

     

    After hours of trying other suggested solutions (reinstalling Aperture, deleting Aperture's pref files, repairing permissions, etc.) I can confirm that this .plist file was the cause of Aperture crashing on my Mac.

     

    Followd fof's suggestion and everything works fine now.

  • rayfromlakewood Calculating status...
    Currently Being Moderated
    Sep 24, 2012 2:46 PM (in response to psychotic1)

    I am having issues similar to those described by folks concerning Aperture.  However; after performing the OS upgrade to 10.7.5, and 4 subsequent Apple updates (1 to aperture, and 1 to iphoto included)  All three of my apple image apps fail immediately upon start:  Aperture, iPhoto, and Preview.  I performed the actions recommended concerning the removal of the Aperture plist to no affect.  I have sent crash reports to apple for all of these.  I'm not sure what to do at this point...  Here is my aperture crash report (different than fof's)

     

    Process:     Aperture [591]
    Path:        /Applications/Aperture.app/Contents/MacOS/Aperture
    Identifier:  com.apple.Aperture
    Version:     3.4 (3.4)
    Build Info:  Aperture-301036000000000~1
    Code Type:   X86-64 (Native)

    Parent Process:  launchd [276]

     

    Date/Time:   2012-09-24 15:37:09.818 -0600
    OS Version:  Mac OS X 10.7.5 (11G56)

    Report Version:  9

     

    Interval Since Last Report:      9592 sec
    Crashes Since Last Report:       12

    Per-App Crashes Since Last Report:   4

    Anonymous UUID:                  2570661E-09AE-4496-B6AC-718A190B0538

     

    Crashed Thread:  0  Dispatch queue: com.apple.main-thread

     

    Exception Type:  EXC_BAD_INSTRUCTION (SIGILL)

    Exception Codes: 0x0000000000000001, 0x0000000000000000

     

    Application Specific Information:

    dyld: launch, running initializers

    /usr/lib/libSystem.B.dylib

    xpchelper reply message validation: sandbox creation failed: 1002

    failed to compile sandbox profile: line 778: unbound variable: fsctl-command

     

    Application Specific Signatures:

    sandbox creation failed: 1002

     

    Thread 0 Crashed:: Dispatch queue: com.apple.main-thread

    0   libxpc.dylib              0x00007fff8b657267 runtime_init + 823
    1   libdispatch.dylib         0x00007fff8ab733f2 dispatch_once_f + 53
    2   libxpc.dylib              0x00007fff8b657af5 _xpc_runtime_set_domain + 285
    3   libxpc.dylib              0x00007fff8b654f3d _libxpc_initializer + 452
    4   libSystem.B.dylib         0x00007fff8beeae7e libSystem_initializer + 222
    5   dyld                      0x00007fff60e53da6 ImageLoaderMachO::doModInitFunctions(ImageLoader::LinkContext const&) + 218
    6   dyld                      0x00007fff60e53af2 ImageLoaderMachO::doInitialization(ImageLoader::LinkContext const&) + 46
    7   dyld                      0x00007fff60e512e4 ImageLoader::recursiveInitialization(ImageLoader::LinkContext const&, unsigned int, ImageLoader::InitializerTimingList&) + 260
    8   dyld                      0x00007fff60e5127d ImageLoader::recursiveInitialization(ImageLoader::LinkContext const&, unsigned int, ImageLoader::InitializerTimingList&) + 157
    9   dyld                      0x00007fff60e5127d ImageLoader::recursiveInitialization(ImageLoader::LinkContext const&, unsigned int, ImageLoader::InitializerTimingList&) + 157
    10  dyld                      0x00007fff60e5127d ImageLoader::recursiveInitialization(ImageLoader::LinkContext const&, unsigned int, ImageLoader::InitializerTimingList&) + 157
    11  dyld                      0x00007fff60e5127d ImageLoader::recursiveInitialization(ImageLoader::LinkContext const&, unsigned int, ImageLoader::InitializerTimingList&) + 157
    12  dyld                      0x00007fff60e5127d ImageLoader::recursiveInitialization(ImageLoader::LinkContext const&, unsigned int, ImageLoader::InitializerTimingList&) + 157
    13  dyld                      0x00007fff60e5127d ImageLoader::recursiveInitialization(ImageLoader::LinkContext const&, unsigned int, ImageLoader::InitializerTimingList&) + 157
    14  dyld                      0x00007fff60e5127d ImageLoader::recursiveInitialization(ImageLoader::LinkContext const&, unsigned int, ImageLoader::InitializerTimingList&) + 157
    15  dyld                      0x00007fff60e520b7 ImageLoader::runInitializers(ImageLoader::LinkContext const&, ImageLoader::InitializerTimingList&) + 59
    16  dyld                      0x00007fff60e474dd dyld::initializeMainExecutable() + 206
    17  dyld                      0x00007fff60e4b60b dyld::_main(macho_header const*, unsigned long, int, char const**, char const**, char const**) + 1852
    18  dyld                      0x00007fff60e45059 _dyld_start + 49

     

    Thread 0 crashed with X86 Thread State (64-bit):

      rax: 0x000000000000008f  rbx: 0x00007fff60e40700  rcx: 0x00007fff60e4078f  rdx: 0x0000000000000000

      rdi: 0x0000000000000000  rsi: 0x00007fff60e3f998  rbp: 0x00007fff60e41750  rsp: 0x00007fff60e3fe60

       r8: 0x00007fff60e3fe20   r9: 0x00000000000000c6  r10: 0x0000000000000000  r11: 0x00007fff60e40724

      r12: 0x00007f9c2ac0c4f0  r13: 0x00007f9c2ac0bed0  r14: 0x00007f9c2ac0c140  r15: 0x000000000000000f

      rip: 0x00007fff8b657267  rfl: 0x0000000000010202  cr2: 0x0000000109105868

    Logical CPU: 4

  • léonie Level 8 Level 8 (46,510 points)

    Ray,

    that error is at system level.

    All three of my apple image apps fail immediately upon start:  Aperture, iPhoto, and Preview.


    /usr/lib/libSystem.B.dylib

    xpchelper reply message validation: sandbox creation failed: 1002

    failed to compile sandbox profile: line 778: unbound variable: fsctl-command


    Make a test, if you can launch Aperture and iPhoto, when you log into a different user account (create a new user account from "system Preferences > Users&Groups" if you don't have a test account; don't change any default settings in this account.)

     

    If lboth apps also crash in the new environment, reinstall the operating system and try again.

     

    To reinstall your system see: OS X. About OS X Recovery

     

    Regards

    Léonie

  • rayfromlakewood Level 1 Level 1 (0 points)
    Currently Being Moderated
    Sep 24, 2012 3:20 PM (in response to léonie)

    LeonieDF,

     

    Thanks for your quick reply, but I suspect you gave me some BAD news.  Yes the newly created account also crashes all the Apple image apps.  Do you suspect that the update failed in some way?  Before the update (performed this morning) all worked OK.   Now concerning the reinstall of the OS.  Are we talking a wipe-disk and start over from scratch type of affair?  Or are we talking about performing an upgrade kind of OS overwrite?  I, of course, understand that the full install is better in the long run... But the time, restoration of data, and re-install of certain items is daunting.  I haven't yet upgraded to 10.8, might this be an option?

     

    ray

  • léonie Level 8 Level 8 (46,510 points)

    Yes the newly created account also crashes all the Apple image apps.  Do you suspect that the update failed in some way?

     

    Either the update failed - bad internet connection, incomplete download - or you did install something recently, that corrupted your MacOS X. Look at your crash report. In the final section it lists all Frameworks and kernal extensions that are installled on your system. Are there any kernal extensions (names with the suffix .kext) that you remember installing and that have names that don't include "apple"? If you find something suspicious and have an deinstaler for that program, try if removing helps.

     

    Incomplete and installations and and incompatible kernel extensions are quite often solved by reinstalling the system. Try first, to install on top of your current system and see, if that helps.

     

    Regards

    Léonie

  • rayfromlakewood Level 1 Level 1 (0 points)
    Currently Being Moderated
    Sep 24, 2012 3:58 PM (in response to léonie)

    leonieDF,

     

    To the best of my recollection, I haven't installed anything new except perhaps an update to Java or an Adobe product.  There were no .kext listing within the crash report.  I pasted it into a text editor and scanned for the string after looking through that long list manually.

     

    I recognize that you are providing this advice "out of the goodness of your heart" and I THANK YOU for your help. 

     

    The timeframe of these apps breaking certainly sugests to me that the event causing these apps (that I use daily) to break is related to the some failure of the apple OS update.  Evidently they all share something related to the presentation of images.  Just FYI; my Adobe Bridge still works.

     

    I guess the next step will be to try and perform the OS restore as you suggested.  Thanks again... I've been wanting to install a faster harddrive in my kit anyway; maybe this will be the event that I use to justify all that effort.

     

    ray

  • léonie Level 8 Level 8 (46,510 points)

    You are welcome, ray.

    Good Luck to you!

    Léonie

  • BelaJapka Calculating status...
    Currently Being Moderated
    Sep 25, 2012 12:45 PM (in response to léonie)

    Tx...work perfect now...

  • SonnyV Calculating status...
    Currently Being Moderated
    Sep 26, 2012 12:10 PM (in response to obo23)

    Help!? Following this thread and still can't seem to fix. Any suggestions? Please be detailed in procedures. Much thanks ahead of time. Here is my first 50 lines in error report. Aperture 3.4 failed to load after installing OS X 10.8.2.

     

    Process:         Aperture [1180]

    Path:            /Applications/Aperture.app/Contents/MacOS/Aperture

    Identifier:      Aperture

    Version:         3.4 (3.4)

    App Item ID:     408981426

    App External ID: 10581304

    Code Type:       X86-64 (Native)

    Parent Process:  bash [1175]

    User ID:         501

     

    Date/Time:       2012-09-26 11:03:59.252 -0800

    OS Version:      Mac OS X 10.8.2 (12C54)

    Report Version:  10

     

    Interval Since Last Report:          23339 sec

    Crashes Since Last Report:           17

    Per-App Crashes Since Last Report:   13

    Anonymous UUID:                      DBA3ED28-E908-CCB9-FD83-6B69906E4EF1

     

    Crashed Thread:  0

     

    Exception Type:  EXC_BREAKPOINT (SIGTRAP)

    Exception Codes: 0x0000000000000002, 0x0000000000000000

     

    Application Specific Information:

    dyld: launch, loading dependent libraries

     

    Dyld Error Message:

      Library not loaded: @executable_path/../Frameworks/PrintServices.framework/Versions/A/PrintServices

      Referenced from: /Applications/Aperture.app/Contents/MacOS/Aperture

      Reason: image not found

     

    Binary Images:

           0x109cd4000 -        0x10a425fff  com.apple.Aperture (3.4 - 3.4) <F66E6C13-82C8-3C10-91D2-6A749047429F> /Applications/Aperture.app/Contents/MacOS/Aperture

           0x10a642000 -        0x10a64aff7  com.apple.PhotoFoundation (1.0 - 1.14) <A1F27E41-CD9E-31F0-8F21-887555E1D576> /Applications/Aperture.app/Contents/Frameworks/PhotoFoundation.framework/Versio ns/A/PhotoFoundation

           0x10a6c0000 -        0x10abdcfff  com.apple.RedRock (1.9.4 - 301.35) <6425F20F-6955-3997-9AEC-4E7198FC6111> /Applications/Aperture.app/Contents/Frameworks/RedRock.framework/Versions/A/Red Rock

           0x10aee1000 -        0x10af63fff  com.apple.iLifePageLayoutCore (1.0 - 176.10) <654893D7-EFC0-3E3F-A766-8C64227FF301> /Applications/Aperture.app/Contents/Frameworks/iLifePageLayoutCore.framework/Ve rsions/A/iLifePageLayoutCore

           0x10afc6000 -        0x10afcbfff  com.apple.iLifePhotoStreamConfiguration (3.4 - 2.5) <906317D7-09FF-3B77-8F35-01BB74C0109C> /Applications/Aperture.app/Contents/Frameworks/iLifePhotoStreamConfiguration.fr amework/Versions/A/iLifePhotoStreamConfiguration

           0x10afd9000 -        0x10b008ff7  com.apple.iLifeAssetManagement (2.7 - 31.34) <C39032ED-C0EA-3204-A272-C0C5318AC8C2> /Applications/Aperture.app/Contents/Frameworks/iLifeAssetManagement.framework/V ersions/A/iLifeAssetManagement

           0x10b03a000 -        0x10b047ff7  com.apple.iphoto.AccountConfigurationPlugin (1.2 - 1.2) <DB1DA508-491A-3B79-B3EC-CFE31C9C9497> /Applications/Aperture.app/Contents/Frameworks/AccountConfigurationPlugin.frame work/Versions/A/AccountConfigurationPlugin

           0x10b05b000 -        0x10b0feff7  com.apple.MobileMe (13 - 1.0.4) <9A7FCC99-67CE-3F5E-98BB-9079B305087F> /Applications/Aperture.app/Contents/Frameworks/MobileMe.framework/Versions/A/Mo bileMe

  • léonie Level 8 Level 8 (46,510 points)
    Currently Being Moderated
    Sep 26, 2012 12:21 PM (in response to SonnyV)

    Sonny, that is the typical - you need to remove and reinstall Aperture - crash log.

    Dyld Error Message:

      Library not loaded: @executable_path/../Frameworks/PrintServices.framework/Versions/A/PrintServices

      Referenced from: /Applications/Aperture.app/Contents/MacOS/Aperture

      Reason: image not found

     

    A framework is missing in your Aperture library package. To reinstall, follow this support document by Apple: Aperture 3.4: May quit unexpectedly on launch after updating

     

    Ask back if certain steps are not clear.

     

    Good luck

    Léonie

  • SonnyV Level 1 Level 1 (0 points)
    Currently Being Moderated
    Sep 26, 2012 2:02 PM (in response to léonie)

    Worked! Thanks so much, Léonie!

  • FarNorth_1 Level 1 Level 1 (0 points)
    Currently Being Moderated
    Sep 26, 2012 5:25 PM (in response to eadesr)

    I had the exact same problem!  Not only will the current library not update and work but new libraries can not be started either.  Always results in crash loop. 

     

    To fix the problem:

    Click on desktop

    Under the top menu item GO (on grey top menu bar)

    Click on: Go to folder

    Type in:

    ~/Library/Preferences

    Once the finder opens you will need to scroll down to find "com/apple.Aperture.plist"

    NOTE: if this is not visible you must enable hidden files.  Im sorry I forgot how to enable hidden files but you can google how to do it. Once you have enabled them they will always be visible from here on out.

     

    Delete this plist file.

    restart aperture and it will open your library and all will be well.

     

    Sidenote:  these plist files have become a total pain in my A**  It has become common place on my computer for these types of problems.  Usually deleting this plist file will reset and allow the program to work normally.

  • Aye Es Oh Calculating status...
    Currently Being Moderated
    Sep 27, 2012 8:57 AM (in response to FarNorth_1)

    FarNorth, deleting the plist is not a permanent fix. See Leonie's most recent post above.

Actions

More Like This

  • Retrieving data ...

Bookmarked By (1)

Legend

  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.