Save as PDF crashes every application

When I select Print > Save as PDF, it immediately crashes any application that I am in. I cannot create PDFs anymore, tried Safari, Mail, Chrome, TextEdit, Word.


Word's Error Reporting tool gave this error info:


Error Signature:

Exception: EXC_BAD_ACCESS

Date/Time: 2014-10-07 22:37:06 +0000

Application Name: Microsoft Word

Application Bundle ID: com.microsoft.Word

Application Signature: MSWD

Application Version: 14.4.4.140807

Crashed Module Name: libobjc.A.dylib

Crashed Module Version: unknown

Crashed Module Offset: 0x000044a7

Blame Module Name: FXPSACEAccount

Blame Module Version: 1.71

Blame Module Offset: 0x000139db

Application LCID: 1033

Extra app info: Reg=en Loc=0x0409

Crashed thread: 0


Anyone has any ideas how to fix this? Thanks!

MacBook Air, OS X Mavericks (10.9.5)

Posted on Oct 7, 2014 3:41 PM

Reply
5 replies

Oct 7, 2014 4:53 PM in response to Marcus Foth

Launch the Console application in any of the following ways:

☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)

☞ In the Finder, select Go Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.

☞ Open LaunchPad. Click Utilities, then Console in the icon grid.

Step 1

For this step, the title of the Console window should be All Messages. If it isn't, select

SYSTEM LOG QUERIES All Messages

from the log list on the left. If you don't see that list, select

View Show Log List

from the menu bar at the top of the screen.

In the top right corner of the Console window, there's a search box labeled Filter. Initially the words "String Matching" are shown in that box. Enter the name of the crashed application or process. For example, if Safari crashed, you would enter "Safari" (without the quotes.)

Each message in the log begins with the date and time when it was entered. Select the messages from the time of the last crash, if any. Copy them to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.

☞ The log contains a vast amount of information, almost all of which is irrelevant to solving any particular problem. When posting a log extract, be selective. A few dozen lines are almost always more than enough.

Please don't indiscriminately dump thousands of lines from the log into this discussion.

Please don't post screenshots of log messages—post the text.

☞ Some private information, such as your name, may appear in the log. Anonymize before posting.

Step 2

In the Console window, select

DIAGNOSTIC AND USAGE INFORMATION User Diagnostic Reports

(not Diagnostic and Usage Messages) from the log list on the left. There is a disclosure triangle to the left of the list item. If the triangle is pointing to the right, click it so that it points down. You'll see a list of crash reports. The name of each report starts with the name of the process, and ends with ".crash". Select the most recent report related to the process in question. The contents of the report will appear on the right. Use copy and paste to post the entire contents—the text, not a screenshot.

I know the report is long, maybe several hundred lines. Please post all of it anyway.

If you don't see any reports listed, but you know there was a crash, you may have chosen Diagnostic and Usage Messages from the log list. Choose DIAGNOSTIC AND USAGE INFORMATION instead.

In the interest of privacy, I suggest that, before posting, you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if it’s present (it may not be.)

Please don’t post other kinds of diagnostic report—they're very long and rarely helpful.

Oct 7, 2014 5:20 PM in response to Linc Davis

Hi Linc, thank you. Here's what I got. From my reading of this, it seems that it is something to do with the file permissions. I recall that I used the Disk Utility tool the other day, and clicked, "Repair Disk Permissions." It seems to have done the opposite, it broke them rather than repaired them... What's your advice? Thank you!


Step 1:


8/10/2014 8:33:26.809 am TextEdit[19014]: view service marshal for <NSRemoteView: 0x7f90e9d0b2e0> failed to forget accessibility connection due to Error Domain=NSCocoaErrorDomain Code=4099 "Couldn’t communicate with a helper application." (The connection was invalidated from this process.) UserInfo=0x608000463140 {NSDebugDescription=The connection was invalidated from this process.}

timestamp: 08:33:26.808 Wednesday 08 October 2014

process/thread/queue: TextEdit (19014) / 0x104a75000 / com.apple.NSXPCConnection.user.endpoint

code: line 2972 of /SourceCache/ViewBridge/ViewBridge-46.2/NSRemoteView.m in __57-[NSRemoteView viewServiceMarshalProxy:withErrorHandler:]_block_invoke

domain: communications-failure


8/10/2014 8:33:29.935 am sandboxd[146]: ([19014]) TextEdit(19014) deny file-read-data /Library/Preferences/org.cups.PrintingPrefs.plist

8/10/2014 8:33:30.861 am sandboxd[146]: ([19014]) TextEdit(19014) deny file-read-data /Library/Preferences/org.cups.PrintingPrefs.plist

8/10/2014 8:33:30.909 am sandboxd[146]: ([19014]) TextEdit(19014) deny file-read-data /Library/Preferences/org.cups.PrintingPrefs.plist

8/10/2014 8:33:32.705 am TextEdit[19014]: Unable to read contents in the Interface Builder file at path /Library/Printers/FujiXerox/PDEs/FXPSACEAccount.plugin/Contents/Resources/FXPri ntType_Default03.nib due to error: The file “FXPrintType_Default03.nib” couldn’t be opened because you don’t have permission to view it..

8/10/2014 8:33:33.267 am com.apple.launchd.peruser.124196747[224]: (com.apple.TextEdit.38928[19014]) Job appears to have crashed: Segmentation fault: 11

8/10/2014 8:33:33.497 am ReportCrash[19032]: Saved crash report for TextEdit[19014] version 1.9 (310) to /Users/foth/Library/Logs/DiagnosticReports/TextEdit_2014-10-08-083333_CIF-FMN-0 69231.crash



Step 2:


Process: TextEdit [19014]

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

Identifier: com.apple.TextEdit

Build Info: TextEdit-310000000000000~1

Responsible: TextEdit [19014]

0x1008ea000 - 0x100904fff com.apple.TextEdit (1.9 - 310) <E2039C6D-7A45-39B9-A5EF-1B155ACE905E> /Applications/TextEdit.app/Contents/MacOS/TextEdit

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Save as PDF crashes every application

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.