Apple Event: May 7th at 7 am PT
I have generated many different libraries using the
Switch to Library-->Other/New-->Create New
I have been using Aperture 3.4.3 for a long time
I just upgraded to 1.8.3 from 10.7.5
and now Switch to Library-->Other/New-->Create New does not work. The button darkens but NO dialogue comes up.
Also, holding down the option key when launching Aperture results in the same thing.
27 inch Mid 2011 iMac
Suggestions?
Thanks
Are thee any diferencs with the iCloud settings between the accounts that work and the one that doesn;'t?
I have used Font Book to remove all questionable fonts (triangle with exclamation mark) and disabled all user specific fonts. It did not help.
One account does not have iCloud set up as I never use it on that account
Redid the Console look: The bolded text below is what pops into the console window as soon as I click on the 'Create New' Button
3/18/13 9:30:51.853 AM com.apple.launchd.peruser.501[193]: (com.apple.ubd[334]) Exited with code: 254
3/18/13 9:30:57.695 AM com.apple.XType.FontHelper[343]: FontHelper: message received. (<dictionary: 0x7f9dab200060> { count = 2, contents =
"query" => <string: 0x7f9dab200000> { length = 110, contents = "com_apple_ats_name_postscript == "HelveticaNeueUI" && kMDItemContentTypeTree != com.adobe.postscript-lwfn-font" }
"restricted" => <bool: 0x7fff75f09320>: true
})
3/18/13 9:30:57.696 AM com.apple.XType.FontHelper[343]: AutoActivation: scopes (
"/Library/Application Support/Apple/Fonts"
)
3/18/13 9:31:05.378 AM com.apple.launchd.peruser.501[193]: (com.apple.ubd[340]) Exited with code: 254
3/18/13 9:31:10.422 AM sandboxd[347]: ([341]) Aperture(341) deny mach-lookup com.apple.KernelExtensionServer
3/18/13 9:31:10.000 AM kernel[0]: Sandbox: sandboxd(347) deny mach-lookup com.apple.coresymbolicationd
3/18/13 9:31:19.218 AM com.apple.launchd.peruser.501[193]: (com.apple.ubd[345]) Exited with code: 254
3/18/13 9:31:30.001 AM com.apple.security.pboxd[350]: CGSGetWindowTags: Invalid window 0x87
3/18/13 9:31:30.001 AM com.apple.security.pboxd[350]: kCGErrorFailure: CGSSetHideOnDeact: error getting window tags
3/18/13 9:31:32.585 AM com.apple.launchd.peruser.501[193]: (com.apple.ubd[348]) Exited with code: 254
3/18/13 9:31:39.920 AM Aperture[341]: RVS:__54-[NSRemoteSavePanel _runOrderingOperationWithContext:]_block_invoke_0319 : Timeout occured while waiting for the window
3/18/13 9:31:46.504 AM com.apple.launchd.peruser.501[193]: (com.apple.ubd[351]) Exited with code: 254
3/18/13 9:31:59.981 AM com.apple.launchd.peruser.501[193]: (com.apple.ubd[354]) Exited with code: 254
3/18/13 9:32:03.156 AM com.apple.security.pboxd[350]: CGSGetWindowTags: Invalid window 0x88
3/18/13 9:32:03.156 AM com.apple.security.pboxd[350]: kCGErrorFailure: CGSSetHideOnDeact: error getting window tags
3/18/13 9:32:12.769 AM tccd[272]: Unable to talk to lsboxd
3/18/13 9:32:12.822 AM sandboxd[361]: ([272]) tccd(272) deny mach-lookup com.apple.ls.boxd
3/18/13 9:32:12.000 AM kernel[0]: Sandbox: sandboxd(361) deny mach-lookup com.apple.coresymbolicationd
3/18/13 9:32:13.150 AM Aperture[341]: RVS:__54-[NSRemoteSavePanel _runOrderingOperationWithContext:]_block_invoke_0319 : Timeout occured while waiting for the window
3/18/13 9:32:13.621 AM com.apple.launchd.peruser.501[193]: (com.apple.ubd[355]) Exited with code: 254
3/18/13 9:32:27.139 AM com.apple.launchd.peruser.501[193]: (com.apple.ubd[366]) Exited with code: 254
One account does not have iCloud set up as I never use it on that account
That's on the working account? If so as a test disable ALL iCloud settings for the non-working account and try it.
Trying to sign out of iCloud with the signing out display going for about 5 minutes now....
I have unchecked all iCloud items...Had no effect on Aperture problem
I think you're going to have to conatct Apple on this.
The NSRemoteSavePanel error was a reported bug, it has to do with the new sandboxing policies.It manifested itself by not allowing some users to save files in some apps and was strongly correlated with iCloud which is why I asked you to try turning off iCloud on the non-working account.
Two last things I can think of to try:
One turn off networking before starting Aperture and give it a shot. See if there is any change.
Second is to run Disk Utilities Repair Permissions. As a rule I never recommend this especially in the case where only one account is not working but there were some reports that doing this also cleared up the problem.
good luck
OK one real last thing.😉
There is another plist file associated woth Aperture it is in
While there is no mention of this directly fixing your situation this plist file does deal with security and sandboxingso it is reasonable to think it might have something to do with this.
I would quit Aperture, move that Container.plist file to the desktop, reboot the machine and try Aperture. If it still fails you can move the plist file back.
I really appreciate all the help from Frank and Leonie. I finally called Apple Support and I will try to replicate what they told me. This is not for the faint of heart and I am not 100% sure I have all the steps, but I think so.
1. Select Option-->Go (in file menu) to open user specific library
2. Go to Application Support folder--->Aperture folder (delete the whole thing)
3. Go to Caches folder-->look for folder com.apple.aperture [I did not have one]. I assume he would have had me delete it if I had found it
4. Go to Preference folder-->delete com.apple.aperture.plist
5. Repair permission with Disk Utility and restart computer.
That worked as best as I can tell.
When I upgraded to 10.8.3 I had repaired permission right before I upgraded so who know.
Special thanks to Ben at Apple Support!!
Glad it's finally fixed.
regards
Me too. I was developing some pretty significant anxiety as Aperture is a critical program for my business as well as personal stuff! And I really appreciate Frank's and Leonie's efforts.
🙂
Create New Library
