Updated to 10.6.8, now I can't print

Fiery is the brand name of the RIP by EFI. It's a PC that processes incoming print jobs for the Xerox Docucolor 252 that we own.

In more general terms, if your pritner is affected by this issue, see if you can't print to it via some other way - Windows printing, directly submitting files via it's webpage, etc.

Fixed the issue with printing

Here is what I did

1) Look at the console and validate the crash report which has the following output when the printing fails. Appears that there is a null / divide by zero error in the socket file.

Process: socket [312]

Path: /usr/libexec/cups/backend/socket

Identifier: socket

Version: ??? (???)

Code Type: X86-64 (Native)

Parent Process: cupsd [196]

Date/Time: 2011-06-24 16:02:45.913 -0400

OS Version: Mac OS X 10.6.8 (10K540)

Report Version: 6

Exception Type: EXC_ARITHMETIC (SIGFPE)

Exception Codes: EXC_I386_DIV (divide by zero)

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Thread 0 Crashed: Dispatch queue: com.apple.main-thread

0 socket 0x00000001a29832bc 0x1a2980000 + 12988

1 socket 0x00000001a298104a 0x1a2980000 + 4170

2 socket 0x00000001a2980950 0x1a2980000 + 2384

Thread 0 crashed with X86 Thread State (64-bit):

rax: 0x0000000000000000 rbx: 0x00000001a29858d8 rcx: 0x0000000000000004 rdx: 0x0000000000000000

rdi: 0x0000000000000000 rsi: 0x00007fff5fbf3f20 rbp: 0x00007fff5fbfdce0 rsp: 0x00007fff5fbf45a0

r8: 0x0000000000000001 r9: 0x000000000000000d r10: 0x0000000000000400 r11: 0x0000000000000246

r12: 0x00007fff5fbfdaa2 r13: 0x0000000000000001 r14: 0x0000000000000000 r15: 0x00000001001093e8

rip: 0x00000001a29832bc rfl: 0x0000000000010246 cr2: 0x00007fff5fbf1920

Binary Images:

0x1a2980000 - 0x1a2984fe7 socket ??? (???) <B3FC504E-0491-DF33-C9A0-EFACD245EAF2> /usr/libexec/cups/backend/socket

0x7fff5fc00000 - 0x7fff5fc3be0f dyld 132.1 (???) <29DECB19-0193-2575-D838-CF743F0400B2> /usr/lib/dyld

0x7fff80003000 - 0x7fff800b9ff7 libobjc.A.dylib 227.0.0 (compatibility 1.0.0) <03140531-3B2D-1EBA-DA7F-E12CC8F63969> /usr/lib/libobjc.A.dylib

0x7fff8042f000 - 0x7fff80433ff7 libmathCommon.A.dylib 315.0.0 (compatibility 1.0.0) <95718673-FEEE-B6ED-B127-BCDBDB60D4E5> /usr/lib/system/libmathCommon.A.dylib

0x7fff8048f000 - 0x7fff804d0fff com.apple.SystemConfiguration 1.10.8 (1.10.2) <78D48D27-A9C4-62CA-2803-D0BBED82855A> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfi guration

0x7fff813a7000 - 0x7fff81457fff edu.mit.Kerberos 6.5.11 (6.5.11) <085D80F5-C9DC-E252-C21B-03295E660C91> /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos

0x7fff824c6000 - 0x7fff8274fff7 com.apple.security 6.1.2 (55002) <4419AFFC-DAE7-873E-6A7D-5C9A5A4497A6> /System/Library/Frameworks/Security.framework/Versions/A/Security

0x7fff8290e000 - 0x7fff8298bfef libstdc++.6.dylib 7.9.0 (compatibility 7.0.0) <35ECA411-2C08-FD7D-11B1-1B7A04921A5C> /usr/lib/libstdc++.6.dylib

0x7fff83e4e000 - 0x7fff83e88fff libcups.2.dylib 2.8.0 (compatibility 2.0.0) <7982734A-B66B-44AA-DEEC-364D2C10009B> /usr/lib/libcups.2.dylib

0x7fff83e89000 - 0x7fff83ed5fff libauto.dylib ??? (???) <F7221B46-DC4F-3153-CE61-7F52C8C293CF> /usr/lib/libauto.dylib

0x7fff840fa000 - 0x7fff842bbfef libSystem.B.dylib 125.2.11 (compatibility 1.0.0) <9AB4F1D1-89DC-0E8A-DC8E-A4FE4D69DB69> /usr/lib/libSystem.B.dylib

0x7fff842d4000 - 0x7fff8444bfe7 com.apple.CoreFoundation 6.6.5 (550.43) <31A1C118-AD96-0A11-8BDF-BD55B9940EDC> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation

0x7fff84bc2000 - 0x7fff84d80fff libicucore.A.dylib 40.0.0 (compatibility 1.0.0) <4274FC73-A257-3A56-4293-5968F3428854> /usr/lib/libicucore.A.dylib

0x7fff875fd000 - 0x7fff8760eff7 libz.1.dylib 1.2.3 (compatibility 1.0.0) <97019C74-161A-3488-41EC-A6CA8738418C> /usr/lib/libz.1.dylib

0x7fff88de8000 - 0x7fff88ea1fff libsqlite3.dylib 9.6.0 (compatibility 9.0.0) <2C5ED312-E646-9ADE-73A9-6199A2A43150> /usr/lib/libsqlite3.dylib

0x7fff89680000 - 0x7fff896a1fff libresolv.9.dylib 41.0.0 (compatibility 1.0.0) <9F322F47-0584-CB7D-5B73-9EBD670851CD> /usr/lib/libresolv.9.dylib

0x7fffffe00000 - 0x7fffffe01fff libSystem.B.dylib ??? (???) <9AB4F1D1-89DC-0E8A-DC8E-A4FE4D69DB69> /usr/lib/libSystem.B.dylib

2) I then compare /usr/libexec/cups/backend/socket to a previous TimeMachine version prior to the update and noticed that the file sizes / time stamps differed

3) I backed up my current /usr/libexec/cups/backend/socket and copied over my TimeMachine version over it

4) Created a new printer with my regular settings and was able to print again

For folks that cannot get the old socket file I have posted it here, please backup your own file incase of issue. I am not guaranteeing this will work but it worked for me.

10.6.7 socket file : http://www.2shared.com/file/B7sx4kYT/socket.html

look at this also http://gimp-print.sourceforge.net/MacOSX.php

@Carlo - I'm glad its working for you.. you probably have a printer that's directly supported under OS X. I have two printers, a network printer and a desktop inkjet. The inkjet is natively supported, and works after the update (especially since it at the same time there was an Epson update).

The network printer does not work after the update. I was printing all morning, and soon as I restarted after the updated I get the errors that everyone else is reporting. The person your responding to does have every right to be upset, especially if it's affecting their business.

I'm sure Apple will address this quickly, however I'm less than impressed by the QA that went into this patch.

You can add me to the list of people not working, Running an iMac 10.6.8 and a Konica Minolta Bizhub C452, I have users running 10.6.7 on the same network and they all print just fine to the bizhub. The 10.6.8 computer are able to print to a HP 4100 and HP 4600 on the same network just fine.

Hmm. The socket file hack isn't working for me here. We're having the issue with a Xerox Docucolor 242 with a Fiery EX controller.

How exactly would one go about locating this socket file? I've tried looking in Finder for the "/usr/libexec/cups" directory, but I can't find it (which tells me that I'm probably looking incorrectly). Thanks!

Please try repairing your disk permissions as the file came directly from my machine. Applications -> Utilities -> Disk Utility -> Verify first and then Repair

The network printer does not work after the update. I was printing all morning, and soon as I restarted after the updated I get the errors that everyone else is reporting. The person your responding to does have every right to be upset, especially if it's affecting their business.

I had the same problem. I simply reverted back to 10.6.7. Problem solved.

NEVER get an update unless you have a specific problem you are trying to solve. If everything is working on your computer, do nothing.

From finder either use Shift + Option + G or from the Finder menu Go - > Go to Folder and type /usr/libexec/cups/backend

Make sure to verify / repair your permissions afterwards: Applications -> Utilities -> Disk Utility -> Verify first and then Repair

Permission repair didn't help. I haven't restarted or anything but am able to print to the printer with the same pausing and dnssd error.

With a brand new printer connection or an existing one ? I had to create a new one before it took effect. Not sure if a restart is required but you can always try it.

Try this:

1. Go to /etc/cups/ppds directory, and find a file with the same name of the printer queue, with a .ppd extension.

2. Add a line "*cupsSNMPSupplies: False" to the end of that .ppd file.

I did re-create the printer (old habit with printer issues such as this). I thought maybe I should re-start CUPs or something via the web interface (http://127.0.0.1:631), but that has changed.

When it's convenient I'll try to restart and maybe double-check everything I did.

Same problem since yesterday with my HP Color LJ 1515n .. made the mac OS-security update 10.6.8. .. and can´t print anything ..

/usr/libexec/cups/backend/dnssd failed

Need help !! URGENT !!!