Aperture 3.0.1 won't open in 64-bit mode; only opens in 32-bit
I downloaded the trial version and then purchased the serial for A3. I installed the plug-in Aperture2gmail and that seems to be where my trouble began. I realized I had to open A3 in 32-bit mode for A2gmail to work. When I un-selected 32-bit mode, I could not open A3. My error message is below:
Process: Aperture [1360]
Path: /Applications/Aperture.app/Contents/MacOS/Aperture
Identifier: com.apple.Aperture
Version: ??? (???)
Build Info: Aperture-1002221847~1
Code Type: X86-64 (Native)
Parent Process: launchd [130]
Date/Time: 2010-03-18 22:33:36.723 -0400
OS Version: Mac OS X 10.6.2 (10C540)
Report Version: 6
Interval Since Last Report: 583218 sec
Crashes Since Last Report: 17
Per-App Crashes Since Last Report: 17
Anonymous UUID: 6BD5A8CB-8295-46D2-BD3F-37C96FA48CF4
Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000
Crashed Thread: 0
Dyld Error Message:
Library not loaded: /Library/Frameworks/PluginManager.framework/Versions/B/PluginManager
Referenced from: /Applications/Aperture.app/Contents/MacOS/Aperture
Reason: no suitable image found. Did find:
/Library/Frameworks/PluginManager.framework/Versions/B/PluginManager: no matching architecture in universal wrapper
/Library/Frameworks/PluginManager.framework/Versions/B/PluginManager: no matching architecture in universal wrapper
Model: iMac5,1, BootROM IM51.0090.B09, 2 processors, Intel Core 2 Duo, 2.16 GHz, 4 GB, SMC 1.9f4
Graphics: ATI Radeon X1600, ATY,RadeonX1600, PCIe, 128 MB
What is the best way to resolve this? Reinstall A3? I have already removed the A2gmail plug-in. Suggestions?
Where does Logic Freeze? Can you see any text in the starup splash screen? Also, how long have you actually waited when Logic appeared 'frozen'?
A program becoming unresponsive isn't necessarily frozen, it may well come "unstuck" after a while - it may be looking for resources, or performing checks - allof hese processes can take some time sometimes.
You should perhaps start up Logic just before taking the dog for a walk or something. If it still hangs when you return, you can reasonably conclude that it is frozen.
Also, what is the Startup Action Logic is set to? Changing it to Do Nothing is a good first step.
Similar Messages
-
Aperture working on OS 10.6.8 then Library Update rqstd on Aperture 3.2; said yes;
now Aperture won't open, get msg "error opening data base for the library "~/Pictures/Aperture Library.aplibrary"
TIme machine won't load backup "error code -8003"
Tried reloading Aperture 3.2 but get same result.You’re running an outdated copy of Safari on your Desktop. That won’t work.
In the Finder, select
Go ▹ Applications
from the menu bar, or press the key combination shift-command-A to open the Applications folder. Check that the Safari application is in that folder. If it is, use it, and delete the copy on your Desktop. Never move or copy built-in applications.
If you've deleted Safari from the Applications folder, back up all data, then reinstall OS X. If your Mac was upgraded from an older version of OS X, you’ll need the Apple ID and password you used to upgrade, so make a note of those before you begin. -
I was editing photos and it was getting stuck or frozen and working very slowly. I attempted to restart the computer but it would not allow me to quit aperture. Now aperture appears in my toolbar but will not open up so I can work on any photos. Any ideas?
Did you try opening from the Applications folder?
Depending on how far that gets you, I would also take a look at the Troubleshooting Basics. -
Aperture 3.4.1 won't open after install
Aperture 3.4.1 wont open after install. it says my graphics card isn't supported. Here's my card ATI Radeon HD 2600 Pro 256 MB, but I can't find specs required for 3.4.1, so I got no idea
Here is the Error Message I get
"The installed graphics card does not meet the minimum requirements for Aperture."
Here is my hardware profile:
iMac
24-inch Mid 2007
Processor 2.4 GHz Intel Core 2 Duo
Memory 4 GB 667 MHz DDR2 SDRAM
Graphics ATI Radeon HD 2600 Pro 256 MB
Software Mac OS X Lion 10.7.5 (11G56)
Went by the Apple store and they didn't have anybody that had seen this one yet. Going by tomorrow for a deeper dive to see if they can find any issue with hardware. Seems like they should have found this before release. I suppose it could be an old card. My iMac is from 2007, so it could be that they have passed it by. I just want to knowwhat I need to get next. Ill reply to this tomorrow if it gets resolved -
Aperture 3.1.3 won't open after upgrade to Lion
Using latest Aperture 3.1.3 on Mac Mini, 2.53 Core Duo, 4GB. Worked fine before upgrade to Lion last week.
Repaired permissions, deleted com.apple.aperture preferences (in now hidden ~/Library), deleted program and reinstalled as new download from App store.
Error message upon startup says:
Dyld Error Message:
Library not loaded: /Library/Frameworks/PluginManager.framework/Versions/B/PluginManager
Referenced from: /Applications/Aperture.app/Contents/MacOS/Aperture
Reason: no suitable image found. Did find:
/Library/Frameworks/PluginManager.framework/Versions/B/PluginManager: no matching architecture in universal wrapper
BTW - "Option - Cmd" during startup won't get to Aperture repair option.
Maybe I am missing something simple. Anybody have any ideas? Thank you!Ok - found my own solution after a more thorough search of forums. Tried it and this solved the problem:
https://discussions.apple.com/message/15111356#15111356
(Thanks!!!)
In a nutshell,my guess is that my installing Motion 5 was the culptrit, as there seems to be something that installing Final Cut and /or Motion does to affect the Library structure of Aperture.
The suggested deleting and re-downloading of the plugin manager buried deep in /Library/Frameworks/PluginManager.frameworks/Versions/B/PluginManager did the trick.
Aperture works like it should. -
Aperture Locks Up and Won't Open Selected Library
I recently did some housekeeping on my system drive..... now Aperture does not connect to the managed library or vault. The library is on a separate drive and shows 40 gigs.
I have done the following:
1. Re-Installed Aperture and set the Library location in preferences.... all I get is the spinning wheel.
2. Started Aperture holding down the option key and pointed to the library or vault..... all I get is the spinning wheel.
I obviously messed up something when I did my housekeeping, but I thought re-installing the program would fix that issue. I've searched through the posts and forums and can't find a similar problem. Any ideas? I'm stuck!
Thanks!You should try to rebuild your library. There is a way to force Aperture to rebuild the library on startup through a key sequence which I do not remember. I know I had to do this once when I was in a similar situation as you.
Here is a link that talks about how to do it
http://aperturetricks.wordpress.com/2006/07/10/aperture-trick-54-library-rebuild / -
IPhoto asks for an upgrade of Aperture and otherwise won't open
After upgrade to Maverick, iPhoto asks for an upgrade of Aperture (which I don't have and never had), and otherwise won't open. If I click "ok", the Applications store opens and asks me to BUY Aperture (69,99 EUR).
There must be a bug in iPhoto 11 after the upgrade to Maverick..?I can only guess at a couple of solutions:
#1
1 - delete the iPhoto preference file, com.apple.iPhoto.plist, that resides in your
User/Home/Library/ Preferences folder.
2 - delete iPhoto's cache file, Cache.db, that is located in your
User/Home/Library/Caches/com.apple.iPhoto folder (Snow Leopard and Earlier).
or with Lion and Mt. Lion delete the contents the User/Library/Containers/com.apple.iPhoto/
Data/Library/Caches/com.apple.iPhoto folder.
3 - reboot, launch iPhoto and try again.
NOTE: In Lion and Mountain Lion the Home/Library folder is now invisible. To make it permanently visible enter the following in the Terminal application window: chflags nohidden ~/Library and press the Return key - 10.7: Un-hide the User Library folder.
If you're running Mavericks, 10.9, go to your Home folder and use the View ➙ Show View Options menu to bring the this window:
where you can check the Show Library Folder checkbox.
#2
1 - launch iPhoto with the Command+Option keys held down and rebuild the library.
2 - Run Option #4, Rebuild Database, followed by Option #1 if needed. -
Aperture won't open in OS 10.5.5
Hi people.
Ok. I'm using an Intel Mac, with 3gb RAM. I've just taken some photo's with my Canon EOS 400D in RAW format. I plugged my camera in and flicked it on just so i could drop the images in iPhoto for some simple adjustments. The camera screen showed that it was 'BUSY'. After a few seconds, it just went to normal shoot mode screen. The camera wasn't mounting or anything. So i opened the EOS Utility piece of software that came with the camera, and it wouldn't open (in force quit, i was presented with "Program not responding"). Ok i thought, i thought i'd give Aperture a go. Aperture (2.1) wouldn't even open.
I've done a bit of research, and found that there's an EOS Utility update which I'm currently downloading, which I'm hoping will solve the mounting issue, so iPhoto will recognise the camera. However, this shouldn't directly affect Aperture should it? Even with the camera disconnected, Aperture still won't open.
I've had Aperture open in the last month, but i've not used it since i done the most recent 10.5.5 update. Anybody any ideas as to why this might be happening?
All my software is up-to-date, the camera and leads are fine-and i've successfully used the camera and software to import RAW photo's previously. I'm a little stumped as to why this has happened. Is there an issue with the latest OS update that affect the compatibility with Aperture 2.1? I've re-downloaded Aperture, but no joy.
Answers on a postcard....The first thing to try (IMO important) is not to import directly from your camera. Get a Firewire-connected card reader (USB works also but is slow on Macs) and use the Mac's Finder to copy images from the card to a folder on the Mac hard drive. My description below describes a CF card, but the workflow is the same for an SD card or whatever.
I feel pretty strongly that camera-to-Aperture handling of original images puts originals at unnecessary risk. I suggest this workflow, first using the Finder (not Aperture) to copy images from CF card to computer hard drive:
• Remove the CF card from the camera and insert it into a CF card reader. Faster readers and faster cards are preferable, and Firewire is much preferable to USB2.
• Finder-copy images from CF to a labeled folder on the intended permanent Masters location hard drive.
• Eject CF.
• Burn DVD copies of the original images (optional backup step).
• Eject DVDs (optional backup step).
• From within Aperture, import images from the hard drive folder into Aperture selecting "Store files in their current location."
• Review pix for completeness (e.g. a 500-pic shoot has 500 valid images showing).
• Reformat CF in camera, and archive DVDs of originals off site.
Note that the "eject" steps above are important in order to avoid mistakenly working on removable media.
Good luck! The camera-to-Aperture workflow may or may not be the cause of your specific problem this time but in any event card-to-finder long term will provide a more solid workflow.
-Allen Wicks -
I just bought Aperture on the App Store, and it won't open. I get this error when I try to open it. Any suggestions? I've tried restarting my iMac.
Here is the crash report.
Process: Aperture [2090]
Path: /Applications/Aperture.app/Contents/MacOS/Aperture
Identifier: com.apple.Aperture
Version: 3.2.3 (3.2.3)
Build Info: Aperture-203040000000000~4
App Item ID: 408981426
App External ID: 6826406
Code Type: X86-64 (Native)
Parent Process: launchd [141]
Date/Time: 2012-04-30 11:41:57.575 -0400
OS Version: Mac OS X 10.7.3 (11D50)
Report Version: 9
Interval Since Last Report: 798638 sec
Crashes Since Last Report: 8
Per-App Crashes Since Last Report: 8
Anonymous UUID: 031A80F1-A655-4757-8E98-BC754EA50771
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: /Library/Frameworks/PluginManager.framework/Versions/B/PluginManager
Referenced from: /Applications/Aperture.app/Contents/MacOS/Aperture
Reason: no suitable image found. Did find:
/Library/Frameworks/PluginManager.framework/Versions/B/PluginManager: no matching architecture in universal wrapper
Binary Images:
0x100000000 - 0x100797fe7 com.apple.Aperture (3.2.3 - 3.2.3) <68B4FE50-2493-34CE-AA96-5082AEB612C8> /Applications/Aperture.app/Contents/MacOS/Aperture
0x100984000 - 0x100e3efe7 com.apple.RedRock (1.8.2 - 233.29) <C0877210-AC68-3632-843C-41EDD190D9EC> /Applications/Aperture.app/Contents/Frameworks/RedRock.framework/Versions/A/Red Rock
0x1010b7000 - 0x1010baff7 com.apple.iLifePhotoStreamConfiguration (2.2 - 2.2) <F3D00C75-7FC9-3E44-9C43-1CCF02A42244> /Applications/Aperture.app/Contents/Frameworks/iLifePhotoStreamConfiguration.fr amework/Versions/A/iLifePhotoStreamConfiguration
0x1010c0000 - 0x1010d0ff7 com.apple.iLifeAssetManagement (2.1 - 10.12) <53C0A173-E7C3-3978-A5F3-28E4E9C951CF> /Applications/Aperture.app/Contents/Frameworks/iLifeAssetManagement.framework/V ersions/A/iLifeAssetManagement
0x1010e3000 - 0x101191ff7 com.apple.MobileMe (13 - 1.0.4) <233AAB01-586D-33DF-89D8-1D5754615C1E> /Applications/Aperture.app/Contents/Frameworks/MobileMe.framework/Versions/A/Mo bileMe
0x200000000 - 0x20000aff7 com.apple.iphoto.AccountConfigurationPlugin (1.2 - 1.2) <B142A0DF-3C82-31B4-913D-558F618E739C> /Applications/Aperture.app/Contents/Frameworks/AccountConfigurationPlugin.frame work/Versions/A/AccountConfigurationPlugin
0x7fff6b85b000 - 0x7fff6b88fbaf dyld (195.6 - ???) <0CD1B35B-A28F-32DA-B72E-452EAD609613> /usr/lib/dyld
0x7fff8e044000 - 0x7fff8e044fff com.apple.Cocoa (6.6 - ???) <021D4214-9C23-3CD8-AFB2-F331697A4508> /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa
0x7fff8e43e000 - 0x7fff8e640fe7 com.apple.AOSKit (1.02 - 91) <78F90BCC-414B-38E0-908D-A17906CF31FF> /System/Library/PrivateFrameworks/AOSKit.framework/Versions/A/AOSKit
0x7fff90564000 - 0x7fff905b0ff7 com.apple.SystemConfiguration (1.11.2 - 1.11) <A14F3583-9CC0-397D-A50E-17217075953F> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfi guration
0x7fff905f6000 - 0x7fff905f6fff com.apple.CoreServices (53 - 53) <043C8026-8EDD-3241-B090-F589E24062EF> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
0x7fff90c4c000 - 0x7fff90dd6ff7 com.apple.WebKit (7534.53 - 7534.53.11) <2969964C-2759-3407-9EBB-C1304A556755> /System/Library/Frameworks/WebKit.framework/Versions/A/WebKit
0x7fff92d3a000 - 0x7fff92d4aff7 com.apple.opengl (1.7.6 - 1.7.6) <C168883D-9BC5-3C38-9937-42852D719718> /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL
0x7fff9317c000 - 0x7fff93350fff com.apple.CoreFoundation (6.7.1 - 635.19) <57B77925-9065-38C9-A05B-02F4F9ED007C> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x7fff9336c000 - 0x7fff9350bfff com.apple.QuartzCore (1.7 - 270.2) <F2CCDEFB-DE43-3E32-B242-A22C82617186> /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore
0x7fff935c4000 - 0x7fff9362eff7 com.apple.framework.IOKit (2.0 - ???) <EEEB42FD-E3E1-3A94-A771-B1993B694F17> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
0x7fff949b7000 - 0x7fff949bdfff com.apple.DiskArbitration (2.4.1 - 2.4.1) <CEA34337-63DE-302E-81AA-10D717E1F699> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration
0x7fff976c5000 - 0x7fff976c5fff com.apple.Accelerate (1.7 - Accelerate 1.7) <82DDF6F5-FBC3-323D-B71D-CF7ABC5CF568> /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate
0x7fff985fb000 - 0x7fff985fbfff com.apple.ApplicationServices (41 - 41) <03F3FA8F-8D2A-3AB6-A8E3-40B001116339> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Application Services
0x7fff9941e000 - 0x7fff99700fff com.apple.security (7.0 - 55110) <252F9E04-FF8A-3EA7-A38E-51DD0653663C> /System/Library/Frameworks/Security.framework/Versions/A/Security
0x7fff9a588000 - 0x7fff9a61afff com.apple.PDFKit (2.6.2 - 2.6.2) <4C8D80F6-09BB-3BD5-983B-A24FBEB5BCF3> /System/Library/Frameworks/Quartz.framework/Versions/A/Frameworks/PDFKit.framew ork/Versions/A/PDFKit
0x7fff9ab73000 - 0x7fff9ab73fff com.apple.Carbon (153 - 153) <895C2BF2-1666-3A59-A669-311B1F4F368B> /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon
Model: iMac12,1, BootROM IM121.0047.B1F, 4 processors, Intel Core i5, 2.5 GHz, 16 GB, SMC 1.71f22
Graphics: AMD Radeon HD 6750M, AMD Radeon HD 6750M, PCIe, 512 MB
Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1333 MHz, 0x029E, 0x434D5341344758334D314131333333433920
Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1333 MHz, 0x029E, 0x434D5341344758334D314131333333433920
Memory Module: BANK 0/DIMM1, 4 GB, DDR3, 1333 MHz, 0x029E, 0x434D5341344758334D314131333333433920
Memory Module: BANK 1/DIMM1, 4 GB, DDR3, 1333 MHz, 0x029E, 0x434D5341344758334D314131333333433920
AirPort: spairport_wireless_card_type_airport_extreme (0x168C, 0x9A), Atheros 9380: 4.0.61.5-P2P
Bluetooth: Version 4.0.3f12, 2 service, 11 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en1
Serial ATA Device: ST3500418AS, 500.11 GB
Serial ATA Device: HL-DT-STDVDRW GA32N
USB Device: FaceTime HD Camera (Built-in), apple_vendor_id, 0x850b, 0xfa200000 / 3
USB Device: hub_device, 0x0424 (SMSC), 0x2514, 0xfa100000 / 2
USB Device: Keyboard Hub, apple_vendor_id, 0x1006, 0xfa130000 / 5
USB Device: Apple Optical USB Mouse, apple_vendor_id, 0x0304, 0xfa131000 / 8
USB Device: Apple Keyboard, apple_vendor_id, 0x0220, 0xfa132000 / 7
USB Device: BRCM2046 Hub, 0x0a5c (Broadcom Corp.), 0x4500, 0xfa110000 / 4
USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x8215, 0xfa111000 / 6
USB Device: hub_device, 0x0424 (SMSC), 0x2514, 0xfd100000 / 2
USB Device: iPhone, apple_vendor_id, 0x1294, 0xfd140000 / 5
USB Device: IR Receiver, apple_vendor_id, 0x8242, 0xfd120000 / 4
USB Device: Internal Memory Card Reader, apple_vendor_id, 0x8403, 0xfd110000 / 3
FireWire Device: Hard Drive Quadra, LaCie, 800mbit_speedThe error message you are getting is telling you a shared library is missing. As shuttrtsp33d points out this is usually caused by an install of Final Cut.
The simplest solution is to download and install the OS X Lion Update 10.7.3 (Client Combo)
You can do that over your current system without causing a problem but of course whenever you're doing maintenance work like this is it always a good idea to have a current working backup of the system just in case. -
Aperture Won't Open (tethered shooting error?)
Aperture won't open, I was shooting tethered and it bogged down on importing images. After waiting a few minutes I forced quit the application. Since then I get this error. I have deleted the file from my Applications and reinstalled from the App store.
Process: Aperture [276]
Path: /Applications/Aperture.app/Contents/MacOS/Aperture
Identifier: com.apple.Aperture
Version: 3.2.2 (3.2.2)
Build Info: Aperture-201096000000000~2
App Item ID: 408981426
App External ID: 5333832
Code Type: X86-64 (Native)
Parent Process: launchd [121]
Date/Time: 2011-12-19 22:11:16.598 -0500
OS Version: Mac OS X 10.7.2 (11C74)
Report Version: 9
Interval Since Last Report: 406994 sec
Crashes Since Last Report: 49
Per-App Crashes Since Last Report: 37
Anonymous UUID: DB4F401E-4CC2-4F7A-9DAF-E8F1F045CAD1
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: /Library/Frameworks/PluginManager.framework/Versions/B/PluginManager
Referenced from: /Applications/Aperture.app/Contents/MacOS/Aperture
Reason: no suitable image found. Did find:
/Library/Frameworks/PluginManager.framework/Versions/B/PluginManager: no matching architecture in universal wrapper
Binary Images:
0x100000000 - 0x10078bfef com.apple.Aperture (3.2.2 - 3.2.2) <AD96E4EA-580B-3585-8783-6A2458AEA857> /Applications/Aperture.app/Contents/MacOS/Aperture
0x100975000 - 0x100e25fef com.apple.RedRock (1.8.2 - 231.95) <15582067-FB9A-3057-988F-85AB51721A33> /Applications/Aperture.app/Contents/Frameworks/RedRock.framework/Versions/A/Red Rock
0x101096000 - 0x101099ff7 com.apple.iLifePhotoStreamConfiguration (2.2 - 2.2) <FED42410-3DB7-3CF4-BF3B-AE1650576C9D> /Applications/Aperture.app/Contents/Frameworks/iLifePhotoStreamConfiguration.fr amework/Versions/A/iLifePhotoStreamConfiguration
0x10109f000 - 0x1010affff com.apple.iLifeAssetManagement (2.0 - 2.33) <B7102C48-4455-313B-9D2B-14A3DE14D5B8> /Applications/Aperture.app/Contents/Frameworks/iLifeAssetManagement.framework/V ersions/A/iLifeAssetManagement
0x1010c1000 - 0x10116fff7 com.apple.MobileMe (11 - 1.0.3) <50A10074-AB15-39EE-952B-30D6E5CEB395> /Applications/Aperture.app/Contents/Frameworks/MobileMe.framework/Versions/A/Mo bileMe
0x200000000 - 0x20000aff7 com.apple.iphoto.AccountConfigurationPlugin (1.2 - 1.2) <E8A0F472-C8AA-3F5F-9F85-BDC6F9E260CB> /Applications/Aperture.app/Contents/Frameworks/AccountConfigurationPlugin.frame work/Versions/A/AccountConfigurationPlugin
0x7fff6948b000 - 0x7fff694bfac7 dyld (195.5 - ???) <B372EB7D-DCD8-30CE-9342-E06CADD7CACA> /usr/lib/dyld
0x7fff82bfa000 - 0x7fff82bfafff com.apple.Cocoa (6.6 - ???) <7EC4D759-B2A6-3A99-AC75-809FED1500C6> /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa
0x7fff831d8000 - 0x7fff831d8fff com.apple.Accelerate (1.7 - Accelerate 1.7) <82DDF6F5-FBC3-323D-B71D-CF7ABC5CF568> /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate
0x7fff833f5000 - 0x7fff835f7fff com.apple.AOSKit (1.01 - 87) <E00ACA45-14A4-3894-9001-DDD39667B107> /System/Library/PrivateFrameworks/AOSKit.framework/Versions/A/AOSKit
0x7fff84b03000 - 0x7fff84b6dfff com.apple.framework.IOKit (2.0 - ???) <87D55F1D-CDB5-3D13-A5F9-98EA4E22F8EE> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
0x7fff84e8c000 - 0x7fff84e9bff7 com.apple.opengl (1.7.5 - 1.7.5) <2945F1A6-910C-3596-9988-5701B04BD821> /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL
0x7fff85943000 - 0x7fff8598eff7 com.apple.SystemConfiguration (1.11.1 - 1.11) <F832FE21-5509-37C6-B1F1-48928F31BE45> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfi guration
0x7fff86f7c000 - 0x7fff86f7cfff com.apple.CoreServices (53 - 53) <043C8026-8EDD-3241-B090-F589E24062EF> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
0x7fff87eb2000 - 0x7fff8803cff7 com.apple.WebKit (7534.52 - 7534.52.7) <D858B247-71C2-395A-9A44-A0B8B0713E3A> /System/Library/Frameworks/WebKit.framework/Versions/A/WebKit
0x7fff89d8a000 - 0x7fff89d8afff com.apple.Carbon (153 - 153) <C1A30E01-E113-38A0-95CA-99360F92A37A> /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon
0x7fff8a133000 - 0x7fff8a133fff com.apple.ApplicationServices (41 - 41) <89B6AD5B-5C75-3E83-8C2B-AA7F4C55E400> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Application Services
0x7fff8a42a000 - 0x7fff8a5c9fff com.apple.QuartzCore (1.7 - 270.0) <E8FC9AA4-A5CB-384B-AD29-7190A1387D3E> /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore
0x7fff8b3a9000 - 0x7fff8b57dfff com.apple.CoreFoundation (6.7.1 - 635.15) <FE4A86C2-3599-3CF8-AD1A-822F1FEA820F> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x7fff8b57e000 - 0x7fff8b856ff7 com.apple.security (7.0 - 55010) <93713FF4-FE86-3B4C-8150-5FCC7F3320C8> /System/Library/Frameworks/Security.framework/Versions/A/Security
0x7fff8c18b000 - 0x7fff8c191fff com.apple.DiskArbitration (2.4.1 - 2.4.1) <CEA34337-63DE-302E-81AA-10D717E1F699> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration
0x7fff8ce65000 - 0x7fff8cef7ff7 com.apple.PDFKit (2.6.1 - 2.6.1) <33A0A777-8CF4-3F36-BB1A-78F8A3D7E8C2> /System/Library/Frameworks/Quartz.framework/Versions/A/Frameworks/PDFKit.framew ork/Versions/A/PDFKitLooking at the crash dump you posted it appears as if one of the apllication libraries got messed up.
This entry from the dump:
Dyld Error Message:
Library not loaded: /Library/Frameworks/PluginManager.framework/Versions/B/PluginManager
Referenced from: /Applications/Aperture.app/Contents/MacOS/Aperture
Reason: no suitable image found. Did find:
If you have a TM backup of the OS volume you could get the PluginManager file out and just copy that but probably the easiest and quickest thing to do would be to reinstall Lion. -
Aperture library won't open after using new iphoto
My Aperture library won't open after accidently using iphoto to view it. It says Aperture is outdated but I run 3.4.5 version which is the last.
Now I CAN'T DO MY WORK thanks to this lunacy.
Anyone any suggestions how to fix this ****?Also one more thing
On the MacBook Air - Where aperture is working fine and loading the library, i tried to change the name of the library and then when I tried to open it it shouted with the error ""Error Opening Library--The library could not be imported because it is from an out of date version of Aperture 3. Please upgrade the library to the latest version of Aperture 3 and try again""
But when I changed the name back it was working fine again on the MacBook AIr
Should i be worried that when i look at the get info on my library it says it's an aperture library 3.5.1 ?
Pandava -
I've upgraded to Snow Leopard, Aperture 3 won't open.
I've finally upgraded to snow leopard (hoping the bugs would all be worked out!) Aperture 3 won't open. I did the "fix" found under aperture support. However, the advised, 3.1.1 update for aperture won't open either, saying it I need to install aperture 3 first (it is installed!) help please....
Please see this thread and do follow all the instructions.
Just upgrade to Snow. Now Aperture 3.1 will not start.
I know you have Aperture 3 installed and feel its silly to reinstall it but just try it. -
Aperture library suddenly won't open
OK, I've been putting off updating to the latest version of Aperture (3.4.3) because I had a sort of premonition about something bad happening to my library. But I finally got around to doing the upgrade, having felt this version had been around long enough to be stable. Big mistake. It worked OK initially, but suddenly today won't open my library, no matter what I do.
When I launch Aperture, it opens a little window with a spinning marker in it and the message "Opening Aperture Library". This is normal prior to the main window opening, but usually I see it for no more than a second or so. Now, it's all I see; the main window never appears.
Oddly, Apertur's menu structure seems to work OK while this 'loading' window is open. I can, for example, open the Activity window. However, it contains no useful information to say what's going on; the entries are just blank in this window. Also, I can quit Aperture normally (whereupon it says 'updating previews' as usual).
I've tried all three of the database-reparing options that Aperture offers if you hold down Option-Command when starting: repair permissions, repair database, rebuild database. In all three cases, it goes through the repair process and then just reverts to showing the little 'opening library' window and nothing has improved.
The upgrade to version 3.4.3 apparently went OK the other day, and I've opened and quit the software a few times since I upgraded it, and I thought everything was fine. The one thing that wasn't quite right (and I wonder if this has somethnig to do with my problem now) was Photo Stream. It didn't seem to be working properly. If I clicked the Photo Stream entry in the list at the left of the window, what I saw was just the 'welcome' message with buttons below it to sign in or turn off the service ("No, thanks" button). I didn't see any actual Photo Stream content. In this window, however, it *did* say that I was signed in with my usual Apple ID, so it wasn't very clear to me whether it was OK or not.
There's a photo I took on my iPhone which I was expecting Aperture 3.4.3 to download from Photo Stream, but it never did. I.e. just one shot that failed to download; all the previous ones had been downloaded by my previous version of Aperture. I couldn't see why the missing picture was failing to download, so I tried turning Photo Stream off and on again from within Aperture. I'm really not sure whether this worked or not; there didn't seem to be any meaningful feedback from the software.
Anyway, after having tried to launch Aperture today (and failed), I checked System Preferences and found that Photo Stream was turned off. So I turned it on again. Unfortunately it makes no difference: Aperture still won't load its library at all now.
I have tried all of following:
1. Rebooting my Mac
2. Verifying the disk contaning my Aperture library (it was fine)
3. All three of Aperture's database-repair options
4. Turning Photo Stream on in System Preferences
...and nothing makes any difference. Aperture simply will not open my library but just sits there, twiddling its spinner.
NB My library still appears to be OK, in that I can access its contents from other software successfully using the media browser.
What I haven't yet attempted is to create a blank new library and import my existing library into it. Failing any better ideas I'll try that next, but it's going to be a big operation that will take a lot of time and disk space, so I'd like to see if there are any better things to try first.
I must say I'm very disappointed that Aperture can apparently break so easily. I haven't lost any actual pictures because I'm paranoid and keep a separate copy of all my shots just in the Finder, external to any management software. But I've lost access to lots of photo books I've created over the years and various other resources, not to mention all the editing work I've done on thousands of shots within Aperture (which I haven't retained separately).
This is supposed to be professional level software. How can it seriously (a) break this easily and (b) not be able to retrieve itself via its database repair options?I'm very disappointed.Thanks for that very helpful reply. I've followed your instructions and done some further digging too.
To answer your three points, first of all:
1. No, I haven't imported any images since upgrading my Aperture library for version 4.3.4; I did move photos between projects a couple of times, but mostly I just checked that everything appeared OK after the upgrade and tried to work out why PhotoStream didn't seem to be working properly.
2. I've attempted to create a new Aperture library. This didn't work! A library gets created on disk, but attempting to open it produces the same endless spinner as the main library.
3. I switched to a spare user account (a blank one called 'test', just as the system created it) and tried to launch Aperture and create a new library there. Same result: library is created but won't load in.
This is very strange, because I'm not aware of having changed anything substantial on my system recently. No new software that installed anything as a login item, system service or background process etc. that I'm aware of. (I'm actually quite wary of such software, and don't have much of it on my system.) The only substantial thing that I know has changed since I last successfully launched Aperture is the year, to 2013! And I hardly think that's the cause...!
I'm wondering if Aperture itself has become corrupted somehow, and whether I should trash it and reinstall it. But that's rather a pain because I've got the DVD version, not the one from the Mac App Store. Besides, I'm not sure what remnants it leaves on the system (sandbox files etc.).
I've verified my startup disk, on which Aperture resides, and repaired permissions, and no error was reported (nor did many permissions need to be fixed).
Now, the only other possible explanation I can come up with is that startup is being prevented by a misbehaving PhotoStream process, as I've just discovered that I'm having endless crashes from PhotoStreamAgent, as reported in Console. I'm getting the same series of messages popping up every few seconds:
01/01/2013 21:58:51.649 xpcd[4676]: PhotoStreamAgent[5540]: registration request failed: (0x11, 0x0) The file “com.apple.iLifeAssetManagement.agent.plist” couldn’t be saved in the folder “Preferences” because a file with the same name already exists.
01/01/2013 21:58:52.431 com.apple.launchd.peruser.501[473]: (com.apple.photostream-agent[5540]) Job appears to have crashed: Illegal instruction: 4
01/01/2013 21:58:52.431 com.apple.launchd.peruser.501[473]: (com.apple.photostream-agent) Throttling respawn: Will start in 10 seconds
01/01/2013 21:58:52.615 ReportCrash[5531]: Saved crash report for PhotoStreamAgent[5540] version 2.7 (40.34) to /Users/rghallas/Library/Logs/DiagnosticReports/PhotoStreamAgent_2013-01-01-2158 52_Richard-Hallass-Mac-Pro.crash
01/01/2013 21:58:52.620 ReportCrash[5531]: Removing excessive log: file://localhost/Users/rghallas/Library/Logs/DiagnosticReports/PhotoStreamAgent _2013-01-01-215516_Richard-Hallass-Mac-Pro.crash
This is just repeating every 10 seconds, as suggested by the 'Will start in 10 seconds' message. Starts; crashes; loop.
Now, I've searched for a file called "com.apple.iLifeAssetManagement.agent.plist" and have found three instances: one each in the following places:
Aperture:
/Users/rghallas/Library/Containers/com.apple.Aperture/Data/Library/Preferences/c om.apple.iLifeAssetManagement.agent.plist
PhotoStream Agent:
/Users/rghallas/Library/Containers/com.apple.photostream-agent/Data/Library/Pref erences/com.apple.iLifeAssetManagement.agent.plist
iPhoto:
/Users/rghallas/Library/Containers/com.apple.iPhoto/Data/Library/Preferences/com .apple.iLifeAssetManagement.agent.plist
In all three cases, the file appears to be an alias that points to itself (i.e. original path is the same as the alias's path in each case). That seems weird but I hope it's right, given that it applies to all three (and the files alongside these plists in the folders in which they reside).
Anyway, the logs unfortunately don't make it clear exactly *which* Preferences folder is being referred to, and hence which com.apple.iLifeAssetManagement.agent.plist file is causing a problem. I imagine it's the one associated with PhotoStream Agent, since it's the Agent that's producing the ongoing crash reports. But either way I don't know what to do about it. I suppose I could try trashing this particular plist file, but I'm reluctant to do so as I don't want to break anything further.
NB Aperture itself doesn't appear to output any log messages to say what's happening while it's failing to load its library. -
afyer updating to yosemite aperture, pages, numbers and keynote won't open
i have tried updating them via app store only be told they aren't authorised on this account, they were bought and installed with this mac and there has never been a problem updating before so why now?
this is the fourth time i have had to type this question out. what a terrible lay out for a support section!this is the fourth time i have had to type this question out. what a terrible lay out for a support section!
You aren't likely to get an answer with that type of attitude. BTW, you are not contacting Apple on these forums. We are all volunteer end users just like you. If you want support, then call AppleCare and you can get one-on-one assistance. -
This is going to be a long one. I don't know what I did wrong.
I have a trial version of aperture. I don't know if that means that it will cease to work after a period of time or what. I'm not proud to say that I downloaded it from a torrent site. Okay, shoot me! Maybe it's okay because it was a trial version.
So here is what is going on. Yesterday the CF card from my camera wouldn't load into my computer, and I put it back into the camera and there was nothing on it. Very strange as when I was taking the shots I could see them on my LCD on the camera.
So for all intents and purposes it is empty. I downloaded Untrasher to try and recover the pics on the card. In the download process of the Untrasher, I had to put a copy of it onto an external hard drive. Which I did. And again I'm not sure of any of this because I don't know what I'm doing.
Untrasher recovered some pics on the CF card, but they were ones that had been purposely deleted when aperture asked if I wanted to delete and eject the card from previous download. So Untrasher works pretty good as it recorvered some old stuff. It didn't however recover the stuff I wanted.
So now it is taking up 16 gigs on my external drive. Maybe it is not taking up that space because it is a copy and there is nothing on there, but I JUST DON'T KNOW, AS I DON'T KNOW WHAT I'M DOING. I'm not yelling, just emphasizing.
Now I cannot put the "Digicam .dmg" which is what is on my external drive, in the trash. I get an error message saying an error occurred and I can't continue. Error # 1407. What ever that is.
And now Aperture won't open either. I just get the spinning beach ball. I found the original download folder for aperture and re-installed it and the new one won't open either. Have these expired? Does anyone have any idea what is going on?
And how can I put this Digicam .dmg in the trash and get rid of it. It just won't go.
Thank you for any help.There's a good chance that the version of Aperture you downloaded isn't legit. Same thing for the Digicam clone .dmg you downloaded. These could be filled with programs that could damage your HD and files.
Fist things first - since you're running Snow Leopard, the App Store version of Aperture won't work as it will only work on either Lion or Mountain Lion. You'll need to decide if you want to upgrade to ML first. You're alternative is to BUY the retail version of Aperture from someplace like Amazon.
My gut level feeling is that the software you downloaded may have damaged your OS. My personal recommendation would be to do a clean install of Snow Leopard (after you manually copy all of your data to an external drive that doesn't have any of the crap you downloaded on it).
If you need a good data rescue program, Data Rescue 3 is probably the best. Yes, it's expensive, but it's saved my butt multiple times (even recovering data from a WinDoze drive).
One more thing...quit downloading stuff from torrent sites! Buy it legit!
Maybe you are looking for
-
What is the Oracle VM for x86 internal product link?
As subject. Thanks in advance.
-
"Best practice" for accessing a class from a custom component?
My app utilizes a simple class to hold global properties such as username, session data, and similar data. The class is initialized at app startup via code similar to: appGlobals:myGlobals=new myGlobals. Many of the custom MXML components and AS clas
-
Change Settings in the exchange profile manual
Hi, can I change the parameter-values of the exchange profile manual. Can anybody say me in which directory the file is? Thanks. Regards Stefan
-
I have been a skype user in the UK since 2009 and have a subscription to call Canadian mobiles and landlines, where I have been calling the same numbers from my skype contacts with no problems until now. When I dial, it does not connect anymore and s
-
has anybody had the same ore simmilar problem or knows help for this...???