Thoughtful, detailed coverage of the Mac, iPhone, and iPad, plus the best-selling Take Control ebooks.



Pick an apple! 
Fixing Save as Adobe PDF Crashes

There have been many reported instances of the "Save as Adobe PDF" workflow crashing regardless of application, but precious few workarounds or resolutions. In troubleshooting, I discovered that there were three instances of the "Save as Adobe PDF.action" in three different locations: /Library/Automator; ~/Library/Automator; and /System/Library/Automator. By eliminating all except the version in /System/Library/Automator, the workflow started behaving, and I was able to cut PDFs directly from the Print dialog.

Submitted by
John Zielinski



Related Articles



PGP Causes Leopard Slowdown, But Fix Is Simple

Send Article to a Friend

I don't like being kept waiting. And the 10 to 15 seconds it was taking for a beta of Bare Bones Software's Mailsmith 2.2 to preview each email message in Leopard was far, far too long. Bare Bones head and founder Rich Siegel is a pal of mine, so my quality assurance email report was full of detail and umbrage. Rich suggested that Spotlight under Leopard might be engaged in some activity - Mailsmith 2.2 uses Spotlight quite effectively - and that I might see an improvement after a couple of days.

Drat the man, he was right, and he's a gloater. He sent me a tweet via Twitter: "@glennf Stay after class and write on the board a hundred times: 'I will never doubt @siegel again.' Hm. Might make a good 'Simpsons' intro."

But after installing QuickTime 7.3 and restarting the PowerBook, the problem recurred. I sent Rich some more troubleshooting data - a Sample Application report available with a button click via Leopard's Activity Monitor that pulls in tons of low-level detail about what a program is doing - and he saw the problem: PGP Desktop.

Although I didn't have PGP Desktop 9 launched, the pgp-agent process was still running. I disabled the item in the Login Items portion of my account setup in the Accounts preference pane and restarted. No good. Terminal showed me that when Mailsmith launched, several pgp-agent daemons would also appear. Mailsmith works directly with PGP's encryption tools; other mail programs tend to rely on AppleScript for integration.

I was unable to find instructions for uninstalling all the PGP components, and the company confirmed for me via email that I should have taken the wise step of uninstalling the program and its pieces via the PGP application before upgrading to Leopard if I was worried about compatibility.

Rich suggested I upgrade to PGP's Leopard-compatible beta of Desktop 9.7 to see if that solved the problem. Of course I did, and the problem went away. (See the tweet above.) With this version installed, I can also now easily uninstall the software through the application. The folks at PGP also said that their support group can provide an uninstaller script for those who don't want to run or even install a beta.

Upgrading PGP seemed to solve a host of mysterious other slowdowns that might have been related to Mailsmith's interaction with PGP, and my PowerBook no longer feels nearly unusable under Leopard. In fact, Mailsmith 2.2 (build 227) is notably zippier under Leopard than in Tiger.

I'd like to believe there's a moral to this story. Check all your software for upgrades and compatibility issues before moving to a new operating system? But I didn't think I was "running" PGP as the obvious application portion wasn't running. Perhaps the moral is "have a revert position in case of failure." Or just, "I will never doubt @siegel again."


CrashPlan is easy, secure backup that works everywhere. Back up
to your own drives, friends, and online with unlimited storage.
With 30 days free, backing up is one resolution you can keep.
Your life is digital; back it up! <>