Oder prints causes Aperture to hang

Hi all
Whenever I select the "Order prints" menu item Aperture immediately brings up a sheet with the text "Connecting ..." and a spinner icon and then hangs forever. I assume that this is the time when Aperture should update the list of available print products and pricing information, but nothing ever happens.
I'm currently running Aperture 3.3.1 but the error was present in previous versions of Aperture 3.x.
I have tried deleting the preferences (~/Library/Preferences/com.apple.Aperture.plist) but this didn't help.
Interestingly ordering prints from iPhoto works. Since Aperture and iPhoto now share the same library format, ordering prints from iPhoto is a workaround, but I would prefer printing from Aperture directly.
Does anybody have an idea what is going wrong?
Kind regards,
Christian

My recent upgrade of the OS to version 10.8 (Mountain Lion) and the Aperture update to version 3.2.2 have solved this problem for me.

Similar Messages

Sharpener Pro 3 has problems in Aperture as the Pre sharpener continually asks one to buy or activate and the Output Sharpener causes Aperture to hang. Have removed all duplicate fonts and tried using a new user account. Any ideas?

I am experiencing problems with Sharpener Pro 3 as an Aperture 3 plug-in. These are: the Pre sharpener continually asks one to buy or activate and the Output Sharpener causes Aperture to hang. Following discussions with Nik Software I have removed all duplicate fonts and tried using a new user account. Neither of the courses of action worked. Have other users experienced these difficulties? Can you suggest an alternative remedy?

I am experiencing problems with Sharpener Pro 3 as an Aperture 3 plug-in. These are: the Pre sharpener continually asks one to buy or activate and the Output Sharpener causes Aperture to hang. Following discussions with Nik Software I have removed all duplicate fonts and tried using a new user account. Neither of the courses of action worked. Have other users experienced these difficulties? Can you suggest an alternative remedy?

Switch to RAW decode 2.0 causes Aperture to hang

My apologies if this has already been posted. I didn't see this question anywhere else in the forums.
I converted to Aperture 2.0 and have a library of about 25k images. I have shot with a Nikon D100, D200 and D300 and have images from each in my library. I am pleased with the appearance of many of my images with RAW decode 1.0 and 1.1 so don't want to migrate my entire library to 2.0. I am able to convert some of my images to 2.0 with no problem. Several images, though, refuse to convert. When switching the decode from 1.0 to 1.1 or 2.0 or from 1.1 to 2.0, I get the spinning beach ball of death and have to force quit Aperture. Sometimes the image will convert when I restart Aperture and sometimes it won't. One image in particular was shot with my D100 and consistently causes Aperture to hang when changing the decode from 1.0 to 2.0.
Any ideas on how to fix this problem and get that image to decode 2.0?
Any help is much appreciated.
Rick Holliday

My apologies if this has already been posted. I didn't see this question anywhere else in the forums.
I converted to Aperture 2.0 and have a library of about 25k images. I have shot with a Nikon D100, D200 and D300 and have images from each in my library. I am pleased with the appearance of many of my images with RAW decode 1.0 and 1.1 so don't want to migrate my entire library to 2.0. I am able to convert some of my images to 2.0 with no problem. Several images, though, refuse to convert. When switching the decode from 1.0 to 1.1 or 2.0 or from 1.1 to 2.0, I get the spinning beach ball of death and have to force quit Aperture. Sometimes the image will convert when I restart Aperture and sometimes it won't. One image in particular was shot with my D100 and consistently causes Aperture to hang when changing the decode from 1.0 to 2.0.
Any ideas on how to fix this problem and get that image to decode 2.0?
Any help is much appreciated.
Rick Holliday

2.1.3 causes Aperture to hang

I asked about difficulty with the Vaults pane in this thread:
http://discussions.apple.com/thread.jspa?threadID=1969957&tstart=0
I do not have a solution, but after deleting all Aperture related files and re-installing from disc (Aperture 2.0) the problem was gone. (I also deleted the user account from the computer).
After using Software Update to bring Aperture 2.0 up to Aperture 2.1.3, the problem is back.
Is there a way for me to go back to Aperture 2.1?

All I have been able to do is re-install 2.0.
I don't see any updates available from apple.com except the one that takes you all the way to 2.1.3

Aperture 3 Hanging after upgrade and possible solution

In advance, sorry for the long post:
As many have reported already, I was also a user of Aperture staring at the beachball and finding my computer hanging completely up to the point I was ready to give it flight lessons for free. I might have done this to my MacBook Pro if I was not leaving for an overland trip to Capetown from the Netherlands in a Toyota Land Cruiser in 2 days. If you want to read about the trip: www.africaminded.com.
How did I solve the issue in my case? I hope it helps some of you.
*My aperture setup*
Before you go through all the steps below let me explain how my Aperture workflow was set up:
1. Projects in Aperture correspond to folders on my harddrives. The project folders in Aperture contain reference files to the fils on my harddrives. The folders on my harddrives have the same name as the projects in Aperture. Using the same name does not really matter much, except I find it easier to find images from aperture back on my harddrive without having to use aperture to find the images.
2. I do not have the images imported into an Aperture library because this alllows me to access the images with other applications than Aperture (Photoshop etc).
Preparations:
*Actions I took before I started with a clean Aperture:*
1. Launch Aperture with holding the shift key. This defers Aperture from processing images in the library. Tip from Apple website: http://support.apple.com/kb/HT3805
2. Show Keywords HUD and export the keyword list in a separate file onto the desktop
3. Create folder on desktop called "Exported Projects"
4. Drag project by project to the just created folder. Yes this is a painstaking long process and one I would have liked avoided but I did not find any other solution and needed one. Luckily I only had 44 projects to go through.
5. Close Aperture
6. Delete the user preferences
1. Quit Aperture if still running.
2. In the Finder go to ~/Library/Preferences. (The tilde "~" represents your Home folder).
3. Remove the "com.apple.Aperture.plist" file from the Preferences folder.
7. Move the user created presets, keyword lists, and so on...
1. Quit Aperture.
2. In the Finder, go to ~/Library/Application Support/Aperture.
3. Move the contents of this folder to your Desktop
8. Delete your old Aperture Library or move it to another harddrive. If possible do not empty the bin of your computer (just in case you need the library again - I did not after following all steps below).
9. Reinstall Aperture; Note: Make sure that you have your installation discs nearby before starting this.
1. Open the Applications folder.
2. Drag the Aperture application to the Trash.
3. Insert your Aperture installation disc and install Aperture.
4. When finished, choose Software Update from the Apple () menu to update your software to the latest version.
*Now your computer has a clean install of Aperture*
1. Launch Aperture
2. Show Keywords HUD and import the keyword list that you saved in a separate file on the desktop
3. Move the following files back into ~/Library/Application Support/Aperture:
1. Adjustment Chain Presets.plist
2. FileNamingPresets.plist
3. Metadata Presets.plist
4. MetadataSets.plist
4. Close Aperture and go to
Following the steps below allows you to keep all you metadata and rating as well. It is possible in Aperture 3 to read and import sidecar files containing metadata but this will not include the rating! So if you want to keep your metadata and your ratings, follow the steps below:
(*A) Importing Project*s
1. Launch aperture
2. File > Import >Library / Project
3. After selecting the exported project you want to import, confirm you want to merge the project
4. Which library should be used when a conflict is detected? Choose current library (and not the library/project you are importing).
5. Let Aperture take its time to merge the projects (depending on the size of the project you import this can take longer and you might see the famous beach ball for a few seconds). In the beginning it will look like Aperture does nothing or hangs again.
6. After merging the libraries are completed Close Aperture.
7. Launch Aperture and immediately select Window > Show Activity from the menu. Let Aperture process new previews (this should start automatically after opening Aperture). Show activity will give you an idea how far Aperture is when processing the images so you don't have to stress and stare at the spinning wheel in the bottom left corner.
8. After the processing has finished Close Aperture again to save the new previews and share them with iLife and iWork.
9. Repeat the above until you have imported all your projects. Remember to keep repeating step 6 to 9. This allows you to find out which project contains corrupted images or is corrupt and to deal with it separately. Importing all projects at the same time and then processing all pictures at the same time does not give you the opportunity to figure out how to get rid of the beachball!
*(B) What to do when images are corrupted in a project?*
In case you imported a project that was corrupted or contains corrupted images that causes Aperture to hang completely and slow down your computer to a complete halt:
1. Force quit aperture
2. Reopen aperture and immediately press the shift key after launching the program. Pressing the shift key stops Aperture from rendering/processing the images you imported from the "corrupted project".
3. Select the last imported projected (the one that contains 1 or several corrupted images and gave you the beachball again).
4. Delete the project and empty the trash in Aperture as well. Do not delete the master files associated with you referenced images.
5. Move the corrupted project into a folder called "Corrupted projects". Do not throw the corrupted project away - we will deal with this one later. Just make sure they are not part of the main library you are building.
6. Quit and launch aperture. Aperture should not be processing any images anymore as you already completed that with step 8 above.
7. Complete the importing of your projects following the exact steps above, skipping the corrupted project.
Ps. In my case I found 1 project with corrupted images.
*(C) What do you do with the corrupted projects?*
1. Make sure that Aperture is not yet running.
2. Double click the corrupted project and press the shift key to defer the processing of images. This will launch aperture and treat the project as an individual library.
3. Select all thumbnails and export masters to a new folder and select "Create IPTC4XMP Sidecar File" in the pulldown list where it says "Metadata" in the export window. You should now have all master images of this corrupted project and the sidecar files containing the metadata of these images in the same folder.
4. Quit Aperture
5. Press the Alt-Key/Option-Key and Launch Aperture. Aperture should now ask you which library you want to open. Select your Main Library that contains all the projects you imported following step 1-9 above.
6. Create a new project for the images you are going to import from step 3 of section C.
7. Import the images and move them to where you want them to have. Aperture should import the non-corrupted images including their metadata (as the sidecar file of these images is in the same folder as the images). All you have lost in this case is the rating and possibly the adjustment of these images. The IPTC data will be imported by Aperture in step 9 Section C. You could survive having to redo the rating manually. Redoing the adjustments is a bit of more work, sorry.
8. Quit Aperture.
9. Launch Aperture with pressing the alt-key or option-key and select your main library as in step 5 and select "Show Activity" from the menu. You are now back into step 7 of section A. Complete step7, step 8 and 9 of section A.
*D. Congrats*
1. When all projects have imported correctly delete the projects from your harddrive to gain space.
2. Delete the temporary Aperture library created in section C step 2.
3. Re-install plug ins that you might have moved in the preparation phase (if possible 64-bit versions if available)
Congrats. You now have a completely new and well functioning new Aperture 3 library that offers you all the new features and is very fast I should say. My machine: MacBook Pro 2.93GHz with 4GB Ram.
After you think you can trust Aperture again empty your bin to gain space on your computer.
How long did this take me? All in all about 3 days but not full time luckily. How many real corrupted images? None - something else in the project data was messing everything up.

WOW!
I'm REALLY impressed by your exhaustive and detailled description!
How long did it take to write? Sure longer than the import itself...
Thank you so much. I got a working import of Ap2 lib before but your description have me various hints for handling problematic or faulty projects.
Matt

The action file print causes PS CS5 to hang, stop responding

The action file print causes PS CS5 to hang, stop responding
Its installed on a Win 7 64 bit PC i7 with 6G ram
PS is version 12.0.4 64 bit
The print dialouge box does come up eventualy around 10 mins later (some times). While waiting PS is totaly dead and the task manager shows it as not responding
Anyone got any ideas?

I might suggest seeking out an updated printer driver to see if that will help.
Is it possible you have a network path configured in there somewhere that's pointing to something no longer available on your network?
-Noel

IPhoto, iCloud Photos, QTKitServer-iPhoto and QTKitServer-Aperture all hanging

iMac mid-2011, 8 GB RAM, 1TB Internal Hard Drive, Mac OS X Mavericks 10.9, iPhoto 5, Aperture 3.5
My iPhoto library, iCloud photos and some Mac OS X Mavericks file called QTKitServer-iPhoto and QTKitServer-Aperture keep hanging and not responding. Tried repairing permissions and repairing iPhoto library multiple times. Tried re-downloading Mavericks and that did not fix it. Called Apple Support. They said they could not help me beyond what I had already tried (Apple Online Support has really gone downhill since the last time I called) and to go to my local Apple retail store to see a Genius.
After running hardware tests, the Genius told me that my iPhoto library was too large and that was what was causing iPhoto and iCloud photos to hang. Even though he acknowledged that the QTKitServer operating system file is not supposed to hang. The Genius put in an additional 8 Mb memory to see if adding more memory would help (apparantly iPhoto is supposed to give back some memory when you close it and it does not). So Apple is not flushing memory when an App is closed. Apple's apparent solution is to add more memory that you have to purchase. However, the same three files kept not responding even with the additional memory. So I passed on the additional memory until I get the iPhoto problem solved. He also said my external hard drive, a WD 2TB hard drive that I bought from the same Apple retail store two or three years ago, looked like it was failing because there were lots of disk I/O errors in the system log, even though the drive appears to work fine and disk utility reported no problems when I ran Verify Disk on the external WD drive two days ago. I do not use this drive hardly at all (I backup my iMac to my Time Capsule), exept to keep a backup copy of my iPhoto library and Documents folder, and it has lots of original pictures that are not in my existing iPhoto library. I copied my iPhoto library and Documents folder to it last night and they seemed to copy fine.
So if my iPhoto library is really too big, and that is what the issue is, my problem is that there is no apparent way to break up my existing iPhoto Library into multiple small iPhoto libraries, without losing all of my keywords, titles, photo edits, event names, album names, folders and projects etc. The last time I tried breaking up my iPhoto library into smaller iPhoto libraries, even though I told iPhoto to export keywords and titles, it did not. And the Genius did not know if it would work now or not.
My question is to those of you who have large iPhoto libraries and are using Mac OS X Mavericks and iCloud Photos - how big are your iPhoto libraries? What is too big? Does anyone have an iPhoto library the size of mine that is working fine (who is also using Mac OS X Mavericks and iCloud)? When I talked to Apple online support, they said big iPhoto libraries are 100,000 photos and up. The Genius said anything over 1,000 is big. That's quite a spread. Currently I have 24,000 photos, most of which have been edited in some way or another, and about 1/2 of which have new titles, mulitple keywords assigned, faces and places assigned, etc., since I imported the original master photos. The Genius told me to duplicate my existing iPhoto library, create a new iPhoto library, import all of the folders in the iPhoto database except the Masters folder, and see if iPhoto still hung. If it did, he said it was all the data attached to the photos that is the problem, in which case I would need to create another new iPhoto library and import only the Masters file (images only). I think if I import only the Masters from my existing library, I will lose not only all of my keywords and titles, but also all of my photo edits, event names, album names, folder names, projects etc.
So I wasted an entire afternoon at the Apple retail store, only to buy a new external hard drive (that I may not even need), was told to buy more memory (that did not solve the problem - I passed on that), and I am no further ahead than I was when I went in. I need to know if there is any way that I can break up my iPhoto library into smaller libraries and retain all of the metadata and photo edits?
Finally, when I got home, I discovered that my husband with whom I had shared some of my photo streams, still had photos showing in shared photo streams that I had removed from iCloud two days ago. It removed them on my iMac - the place where those streams originated, but apparently left the thumbnails in the shared photo streams of everyone that I had shared the photos with. As soon as I clicked on an actual photo on my husband's iMac, the photo suddenly vanished and all the photo thumbnails in the stream did too. But the empty shared photo stream still remained on my husband's iMac and he had to physically say "Unsubscribe" to get it to go away. So something is not working right with iCloud photos, which is no doubt why iCloud photos is one of the files that keeps not responding.
Then, when I set up my iMac again this evening, and looked at iCloud on my iMac, all of my photo streams (not just the four that I had removed two days ago) were gone! And when I went into Aperture, the photo streams were all there, but with zero photos in them. Now last night when I boxed up my iMac to take to Apple, those photo streams were all there and they all had photos in them. So where did they go? And why, when you are the originator of a photo stream, and you tell iCloud to remove the photo stream, it says that it does but it leaves remnants of it with the other people you have shared it with? It seems to me that iPhoto, iCloud, and the fact that Apple is not flushing memory when an app closes is the problem with my iMac, not the size of my iPhoto library, or my external hard drive, or the fact that 8Gb of memory is apparently no longer enough memory for decent response with Mavericks (which I thought was designed to help solve some of the memory issues that OS X has).
I need help and help is apparently nowhere to be found at Apple.
Is there anyone out there who can help me?

If you're using iPhoto 5 as you say then, yes, 24k photos is heading close to the Limit of 25k. iPhoto 6 is good for 250,000 images, iPhoto 11 is good for 1,000,000.
I'm going to guess that's a typo and that you have iPhoto 9.5.
I've simply never heard of "too many photos" causing the problem you describe. You don't need more memory. You don't need to break up the Library. "Flushing Memory" is a non-isssue. One of the big improvements in 10.9 is in memory management.
There are a couple of ways to break up a Library while preserving everything. It's dead easy with Aperture - export projects as Library - you can do it with iPhoto simply by duplicating the Library and deleting from the two libraries or use iPhoto Library Manager.
But, as I say, 24k is a small Library. My main library is more than twice the size of that.
Are Aperture and iPhoto using the same Library?
As a Test:
Hold down the option (or alt) key and launch iPhoto. From the resulting menu select 'Create Library'
Import a few pics into this new, blank library. Is the Problem repeated there?
Post back with the result.

Aperture 3 hanging when working with 120,000 image library

I love Aperture. Have used Aperture since v1, now on 3, Snow Leopard 10.6.6. MacPro 3.0 with 20GB RAM and four 7200 3TB HDrives. Shoot a Nikon D3 and others.
I have a big referenced library running internally on Drive 2, images are internally on drive 4. About 120,000 in total, mostly RAW (NEF).
For some time I have had hangs, spinning ball. Some will clear, but most will not, requiring force quit.
I have repaired permissions, on hard drives as well as in Aperture.
Hangs happen when I click on a Folder, or sometimes when selecting image.
I moved everything to a Referenced system to correct this problem, but seemed to not solve things.
I do also use Aperture to catalog Photoshop files, so dont know whether this creates an increased RAM or CPU issue.
Have sent crash reports to Apple, but not heard back yet.
I shoot professionally, sometimes 2,000 per day, so need this to become more reliable.
Any suggestions.
Many thanks!

Leighton wrote:
Thanks so much for your time.
You're welcome. I appreciate your mentioning it.
I have found leaving the Activity Monitor on, where I watch the RAM / MEM usage, is a clue as to whether its still thinking.
I do the same. In addition to AM, I use +iStat Menus 3+, a nifty system-reporting menulet. Recommended (just a satisfied user).
I also need to tell you I do allow my assistant, using a 27"iMac, to access my MASTER LIBRARY from her computer. (Different Aperture 3 version, and mine is shut down).
Supposedly this is ok (acording to Apple) but I am v suspicious. Sometimes it takes forever to load, and I have seen "strange" things like keywords go missing.
Until you have everything working well ... can you refrain from opening your Library using different program installations? I think you are right to be suspicious. (And trouble-shooting strategy would favor limiting problems and then bringing things back as a way of isolating the cause.)
Please check out my response to the others - I stated library size/capacities.
I don't think Library size is the problem.
I wish I could limit my Projects to 500 Masters, but most of the shoots I do are sports, where I will shoot 1,000 to 3,000 images in a day or two.
However, it can be done if this is the issue.
It could be voodoo, but it has become part of the more-or-less generally accepted best practices. You do know that in addition to selecting multiple Projects in order to see all of their images in the Viewer, you can also put Projects in a Folder and just select the Folder. Selecting a Folder in the Library Inspector will show the contents of all Projects and Albums "held" by that Folder. You might -- as an example -- make a Folder for a game, and then put each quarters' shots in its own Project.
I run dual monitors. HOWEVER, I am suspicious of my NVIDIA GeForce 8800GT card. 512 VRAM, 1920x1200 dual outputs. Not sure if this is my problem.
However, I can run Photoshop 5, DW5, InDesign, etc, along with the normal appls, with no problem. Sometimes I have 15-20 PSD files open, and I never use all my RAM.
I run huge Library on a machine w. 4 GB RAM. I don't think your RAM is the source of your problems.
I can't with any expertise address the issue of the video card. My hunch is that this is one of the rough edges of heavy Aperture use, but it's just a hunch.
Rejected/Trash. I find it takes forever to empty Aperture Trash. Have you found that> Did you know you have to empty twice, from Ap AND from OS10.6?
IME, it gets better if you do it often (all the way to system Trash). I have in past had to wait hours for the Aperture Trash to empty. Haven't seen that is a while, though.
Im going to try and move the MAIN LIBRARY to another, newer, drive. See if this works.
One of the biggest advantages will be the defragmentation of the hundreds of thousands of Library files.
I have wondered whether I should invest in a Solid State Internal drive.
Thoughts on that?
Go for it. I will buy one the day I can afford one. I am sure it is the very best performance investment you can make for Aperture.
Cheers. Post when you've found something out.

Printing via Aperture

First, here is my configuration:
Aperture 2.1.4
Printer: Canon Pixma Pro9500 Mark II
Using Canon and Red River Paper
24" iMac running OSX 10.6.2
Although I have been using Aperture since version 2.0 was released, it has only been recently that I have purchased a photo printer. Until now, I have been sending my pictures out to online stores to have them developed.
Since purchasing the printer I have been printing pictures to understand how it works. I have been using Canon papers, and recently I tried Red River Papers. With the Canon papers under "Colorsync profiles" I have been selecting the "System managed" option. Red River recommends I use the profiles they have developed specifically for their paper/my printer combo (they are icc files). If I do this, I get very, very red pigmented skin tones (a stranger looking at the pictures might think the person is suffering from 3rd degree burns). I am told by Red River, as well as Printer forums, and Mac photography forums that I am double profiling the pictures. Yet I have looked everywhere in the settings for my printer within Aperture (and the printer supplied software) and other than using the System Managed Option under Colorsync, I don't see where I am double profiling or how to change it.
Even though folks have been telling me I am double profiling, nobody has been able to show or indicate how to change it.
Admittedly, if I leave the Color Sync Profile setting as "System Managed" using the Canon and Red River papers, the pictures come out pretty good as long as I use glossy. If I use matte, the pictures still come out a bit red.
Thanks in advance for your help.

Thanks for your response. I have updated my sig, but at the moment I am using SL 10.6.2. I apologize for the confusion it might have caused.
Nonetheless, I went ahead and tried to follow your instructions. I attempted to access the printer's settings by going to system preferences/printer. I looked at all my options there and did not find any setting allowing me to turn off color management.
As an aside, I opened PSE 8.0 and looked at the printer settings there. In the program there is a location where I can select color management. I have three options. They are PSE makes the decisions, Printer makes the decision, or no management. Only selecting PSE gives me access to use a separate profile (BTW, none of the Canon or Red River profiles show up here, as they would in Aperture. Might be the subject for a different thread.), but even then, the list of available profiles does not show the profiles for Canon papers or Red River papers. I am digressing...
So, if I go back to Aperture and look at printer settings there is a choice for "Color Options". Within this choice you can manage some of the colors in terms of their intensity. You can also adjust brightness and contrast, but you can't turn off color management. BTW, the "Color Options" is grayed out unless you select "System Management" in another window.
Again thanks for your response.

Safari causing full-system hang

For a while now I've been getting the SBOD irregularly in Safari, since 3.x if I remember right. I've got some time off work at the minute so I'm finally looking into this properly, and here's what I've found:
There seems to be two separate conditions. The first happens on loading some, but not all web pages, causes a lengthy hang in which the entire system (even invoking Dashboard or Spaces) becomes unresponsive. In the console this accompanied by an entry similar to the following:
05/10/2010 08:15:47 /Applications/Safari.app/Contents/MacOS/Safari[242] ATS AutoActivation: Query timed out. (elapsed 5.0 seconds. params: queryString = {comapple_ats_namepostscript == "Helvetica-Neue" && kMDItemContentTypeTree != com.adobe.postscript-lwfn-font}, valueListAttrs = {<CFArray 0x6f5710 [0xa008dee0]>{type = immutable, count = 1, values = (
0 : <CFString 0xa01602c8 [0xa008dee0]>{contents = "kMDItemContentType"}
)}}, sortingAttrs = {<CFArray 0x6f5730 [0xa008dee0]>{type = immutable, count = 1, values = (
0 : <CFString 0xa01603a8 [0xa008dee0]>{contents = "kMDItemContentModificationDate"}
)}}, scopeList = {<CFArray 0x6f5750 [0xa008dee0]>{type = immutable, count = 1, values = (
0 : <CFString 0xa0161a98 [0xa008dee0]>{contents = "kMDQueryScopeComputer"}
(sometimes it names a font, sometimes the font name is "_")
I suspect this means some vestigial adobe product has messed my system right up. I used to use CS4 but have long since removed it. I also have Air and Flash (the current gala beta) installed. I have had fontbook validate Helvetica Neue and check all fonts for duplicates - if external disks are plugged in at this time they all spin up.
The other case is when downloading a file through clicking a link or alt-clicking a link (right-clicking a picture and saving it to the downloads folder does not cause this behaviour), and is accompanied by this much sparser line in the console:
05/10/2010 08:25:06 kernel disk0s2: I/O error.
The files themselves can be opened, moved and copied without incident and at regular speeds, so I doubt disk corruption. I've also performed a few full clone/restores on my boot disk with no effect. My initial thoughts were to blame a long-forgotten folder action that sorted downloads into different places (including a network share, if present), but disabling folder actions has not helped.
So, any ideas? I'm fresh out.

A workaround for the font-problem seems to be to turn off ATS - it's in FontBook.
The second issue still eludes me.
Things I have tried:
Trashing ~/Library/Safari/
Trashing ~/Library/Preferences/com.apple.Safari*
Cleaning out every vestigial trace of anything suspect I had on my system (google keystone, logitech control centre, SIMBL, The Spark, iStat Menus, folder actions)
Interestingly, the issue is not present for the guest user, so it IS something wrong with my user account. I just can't figure out what.
Yes, making a brand new account would fix all this, providing I'm meticulous about testing the issue as I move /Users/Old/ into /Users/New/, but I'm kind of loathe to give up. It's surely something really simple!

Cannot print from Aperture v.2.1.2 to an Epson Artisan 800 printer

I recently purchased an Epson Artisan 800 printer and I would like to be able to print from Aperture. Unfortunately, I have been unable to do so, in spite of multiple conversations with the Epson support group. I am able to print from other applications, such as TextEdit, Safari, and iPhoto. However, when I try to print from Aperture, I never get any output from the printer. Depending on the image that I try to print from Aperture, I will see an error message flash on the printer's display screen.
I captured the following error message from the "system.log" file:
Jan 20 20:11:24 new-host Aperture[12196]: An instance 0xce644a0 of class RKPrintPreviewView is being deallocated while key value observers are still registered with it. Observation info is being leaked, and may even become mistakenly attached to some other object. Set a breakpoint on NSKVODeallocateBreak to stop here in the debugger. Here's the current observation info:\n<NSKeyValueObservationInfo 0xf86da40> (\n<NSKeyValueObservance 0x1c6597e0: Observer: 0xb8c7d10, Key path: selection.isModified, Options: <New: YES, Old: NO, Prior: NO> Context: 0x0, Property: 0x1c641630>\n<NSKeyValueObservance 0xce9b170: Observer: 0xb8c7d10, Key path: selection.gamma, Options: <New: YES, Old: NO, Prior: NO> Context: 0x0, Property: 0xce7e7d0>\n<NSKeyValueObservance 0x1c659830: Observer: 0xb8c7d10, Key path: selection.blackPointCompensation, Options: <New: YES, Old: NO, Prior: NO> Context: 0x0, Property: 0x1c640340>\n<NSKeyValueObservance 0x1c65ef80: Observer: 0xb8c7d10, Key path: selection.colorSyncProfile, Options: <New: YES, Old: NO, Prior: NO> Context: 0x0, Property: 0x1c65d8e0>\n<NSKeyValueObservance 0x1c65d890: Observer: 0xb8c7d10, Key path: selection.dpi, Options: <New: YES, Old: NO, Prior: NO> Context: 0x0, Property: 0x1c6715c0>\n<NSKeyValueObservance 0x1c65eba0: Observer: 0xb8c7d10, Key path: selection.sharpenAmount, Options: <New: YES, Old: NO, Prior: NO> Context: 0x0, Property: 0x1c645070>\n<NSKeyValueObservance 0x1c65ebe0: Observer: 0xb8c7d10, Key path: selection.sharpenRadius, Options: <New: YES, Old: NO, Prior: NO> Context: 0x0, Property: 0x1c645630>\n)
----------END of ERROR MESSAGE------------
I am having this problem on both my iMac G5 and my wife's MacBook. Both are running the latest versions of Mac OS X (10.5.6) and the latest version of Aperture.
If anyone has been able to print from Aperture to an Epson Artisan 800 printer, please let me know how you did it. Thanks.
Bruce

I run 10.4.11 and am unfamiliar with that specific Epson. However step one with Epson troubleshooting is to do any OS updates then download and install the latest Epson driver, even if what you are using is current. The new install will simply install over the old installation. Repair Permissions via Disk Utility immediately before and again immediately after both the OS updates and the printer driver installation.
Once good Epson paper and a new driver installation are done the final step is to carefully follow Gary Ballard's excellent color management tutorials:
<http://www.gballard.net/psd.html>
Good luck!
-Allen Wicks
P.S. Epson tech support for consumer printers has always been worse than useless. Specialized support for the pro printers is pretty good.

HP B8850 Page Size Error Printing from Aperture 2 (or iPhoto)

I am trying to print on 13x19 (B+) size paper to an HP Photosmart Pro B8850 printer. I get this error when printing from Aperture --> "Page Size Error: Paper size selected in the print driver does not match the paper loaded in the printer IN tray."
Aperture 2.1.2
Mac OS X 10.5.6
HP Photosmart Pro B8800 Series Print Driver 2.3.1
I can set the paper size to 13x19 (B+) in the Aperture print dialog, but under the Print Settings button there is no option for paper size, only paper type. So apparently the size that the printer is expecting in the driver does not match the 13x19 that is loaded in the printer. I was able to verify this by leaving all print settings for 13x19 and loading an 8.5 x 11 sheet in the printer. It pulled the paper through and started printing, but the print was scaled to fit onto the 8.5 x 11!
So in other words, the way I'm seeing it, even though I am setting the paper size for 13x19 in Aperture's print dialog, the printer thinks it's suppose to print on 8.5 x 11.
To make matters worse, there is no Page Setup menu item in Aperture to set the paper size in the print driver directly. I would have assumed that the Aperture print dialog was "smart enough" to pass the page size parameter to the HP printer driver, but that is apparently not happening.
I spoke with HP tech support and they were surprisingly helpful. With their help I was able to print on 13x19 paper with HP's bundled software package, but I had to export my file from Aperture and import it into HP's software. Now that's a good first step which assured me there is nothing wrong with the printer itself, but obviously I purchased Aperture to use it's more elegant and supposedly streamlined interface to make my prints.
Has anyone had a similar problem? Any solutions? Suggestions? I have searched this forum, HP's support forum, DP Review, Google and not finding much. I can't believe I'm the only guy trying to print on 13 x 19 from Aperture using this printer. I suspect it's not printer specific though. Could be my system I guess. I plan on calling Apple Care depending on what type of response I get here.

I don't know if this may help, but recently we had a discussion about problems with Aperture's custom paper size not working correctly:
The solution was to define a paper size outside Aperture:
In any application, for example Preview, try to print something and the print dialog comes up. At this point click on Paper size and choose Manage Custom Sizes. You can define a new paper size here. This new custom size will then appear when you go to Aperture print dialog under paper size. It solved my problems with custom paper sizes here, for some reason (a bug?) defining a custom paper size within Aperture itself did not work correctly for me.

Is there a reason I can't print wirelessly in Aperture? I am able to from other programs. When I try to print in Aperture, the printer tells me it's offline.

Aperture won't print a photo wirelessly. My other programs print fine wirelessly. Anybody know why? I'm using OS X 10.6.8, Aperture 3.2.4 on an iMac with an Epson Artisan printer. When I try to print in Aperture, the printer utility tells me the printer is offline. But it isn't. I am shooting in RAW, by the way.

I don't have much, but ... make sure you are selecting the entry for the _wireless printer_. It's been some time since I did this — and a few OS's and Aperture versions ago — but I remember that there were multiple entries for my printer: USB, Ethernet, Wireless, and mounted to other computers on the network.

Printing causes Office 2013 applications to crash

We’ve a fresh installed Windows 8 Pro and Office 2013. Printing works correctly in every application but Office 2013.
Word, Excel, Outlook … printing causes the application to crash.
Any idea if this is a known issue?
Regards.
Peter
Peter Van Keymeulen, IT Infrastructure Solution Architect, www.edeconsulting.be

This is the answer that fixes the problem every time, based on my experience and that of others. It works for both the 32 & 64-bit versions of Windows (I'm one of those odd ducks who runs 32-bit Windows 8.1 Professional and it worked perfectly for me).
The problem is not Windows, either 7 or 8, it's Office 2013 and a variety of unique HP LaserJet printers. By the way, the glitch occurs whether you use networked printing or a USB cable; I discovered that early-on when I
was trying to troubleshoot the issue. Also (and it should go without saying), always reboot the computer after you make the change to the driver. Thanks to Shane, who apparently was the first one to discover the solution over a year ago, right
after Office 2013 came out and the problem manifested itself.
After lots of testing I have found a setting that has fixed all my HP CP5520 and HP M4555 printers that were crashing when printing from Office 365's 2013 pro plus.
It's the driver setting in Device settings -> Installable options -> Printer Status notification, this needs to be disabled.
I hope this also fixes other peoples problems.
Shane

Non-Apple browsers cause cascading system hang with clean install of Lion

It started with Google Chrome. After a few hours of use, Chrome would randomly lock up one renderer at a time until it was completely unresponsive. Console showed nothing conclusive in the logs, and would soon lock up itself. Logged-in Terminal windows could sometimes get as far as a "ps auxc", but would lock up during the command output, and new Terminal windows or tabs would never get past login. The SSH daemon would be dead in the water, preventing me from logging in remotely. Any existing SSH connections would hang on the first command. Activity Monitor would lock up the moment I tried to sample a process or interact with anything. Interacting with SystemUIServer (pulling down the menu for the clock or trying to do a Spotlight search) would cause SystemUIServer to hang. Same with the Dock. My mouse was like the Midas of software failure: everything I touched turned to hang. Eventually I'd be staring at a spinning beachball. After a few (five to ten) minutes, it might perform a couple queued events (opening a window, switching to another application) but would usually become wedged again immediately, forcing me to hard restart.
I then tried installing Firefox 5, and discovered that it causes the hang fairly reliably within the first ten seconds. Since I knew when it was about to happen, I managed to capture a few stack traces in Activity Monitor, but it was always different, and always somewhere in the kernel (usually file-system related: __getattrlist while scanning fonts one time, the open system call another).
Safari, on the other hand, works great.
I've tried performing a verification of my startup disk, which returns no errors, so although I'm not ruling out hardware failure at this point the problem started immediately after I upgraded to Lion, and persisted even after I wiped my hard drive completely and performed a clean install from the recovery partition. It also doesn't seem to be completely the fault of either Chrome or Firefox, since they're different browsers with different rendering engines using different system frameworks. They do both perform a lot of file I/O, so maybe that's a clue. Another possible lead is the seemingly random errors Console will spew out while the hang is occuring. Most recently I've gotten a screenful of '--ImageKit Error: updateGLTextureWithBitmapData: glPixelStorei returned an error : 506 ...', and before that it was 'Google Chrome Helper: CGSLookupServerRootPort: Failed to look up the port for "com.apple.windowserver.active" (1100)', "kernel: IOSurface: buffer allocation size is zero". Console spew being what it is, though, I don't know if any of that is relevant.
I figure I would be seeing quite a lot of angry forum threads if Chrome and Firefox were completely unusable on other people's machines, so I'm guessing there's something specific to my configuration happening here. With a clean install, though, I'm not sure what it could be. Here are detailed system specs:
24" iMac (Early 2008 -- just out of AppleCare coverage, figures) , 2.8 GHz, 2GB RAM, running Lion build 11A511 (which should be the 10.7 release version).
I would be massively indebted to anyone who has experienced or heard about this issue before and can give me something else to try.

Zeroing the disk serves no purpose in this situation. It is a common misconception that this is required to map out bad blocks on the drive, but the fact is that 1) modern hard drives map out bad blocks as part of everyday operation, and 2) zeroing the drive involves simply writing zeros with no checks to see if the zero was written successfully, so it wouldn't know if a block was bad anyway.
It's possible the drive is starting to go bad, although then there should be some problems with SL as well. I would recommend repartitioning the drive with Disk Utility. Make sure it's got one partition, using the GUID partition map scheme, and format that partition as Mac OS Extended (Journaled). Repartitioning should get rid of any gremlins lurking on the disk, unless the physical disk itself is dying. And after repartitioning, install straight from the flash drive, as Shootist recommends, rather than installing SL first.
Hardware could be an issue. It's entirely possible for an older system to work fine on slightly faulty hardware while a newer system does not. Running Apple Hardware Test wouldn't be a bad idea.
Firmware updates wouldn't be a bad idea. However, note that my mid-2010 MBP with the same specs is running Lion just fine, and I've never installed any firmware updates. (Firmware updates scare me... if my machine is running just fine, I'm reluctant to risk installing new firmware. But that's probably just a bit of paranoia talking. )

Oder prints causes Aperture to hang

Similar Messages

Maybe you are looking for