Updated to 10.6.8, now I can't print

We are having issues at our school too. HP 4100 printers and Toshiba e-studio 352 Copiers for sure do not work. We add our printers via IP Address on the machines not Bonjour if that makes a difference.

HP 4250s appear to work for us.

Had same error with C253 Konica Minolta.

Fixed problem by turning off snmp through C253's web admin page.

Now printing fine.

Thank you very much, I couldn't print to my Konica C451 any more. Turned off the SNMP and I can now print. When I talked to Apple Tech Support they told me the driver was probably not compatiable and the manufacture would need to update. It took me two years to get a drive that worked well.

Bryan Cooper - Social Director wrote:

It sounds like there are 2 printer bugs. The main bug affecting network printers is acknowledged as a regression bug at cups.org. That is, it was a bug introduced in 1.4.7 cups driver.

There also seems to be a standard printer driver upgrade type bug affecting some Epson printers that can by resolved by deleting the Epson driver for the upgrade.

I just thought it interesting to note that the original main bug can be seen in the source code from cups.org.

The errant function is called 'backendSNMPSupplies()'

It is called by several 'backend' programs, including socket, lpd, lpd, ipp.

In that function, a 'divide by zero' error will occur IF the object 'supplies' is not properly initialized.

That error kills any program calling that function and shows up in the console.

A source code patch to cups has already been posted which shows the bug:

http://cups.org/strfiles/3875/str3875.patch

A fairly simple and straightforward fix if you are only dealing with a couple of 10.6.8 machines:

Go to the 10.6.8 machine where you are going into the printer pause as soon as a job gets submitted. Run /Applications/Utilities/Console, and push the "Show Log List" button in the upper left. Fold down the triangle on the Files list, and then on Library/logs (not ~Library/logs) CrashReporter. There will be a boatload of crash files that start "lpd_2011_timeStamp_localhost.crash -- one for each time you submitted a job to the printer and it paused the queue. Look at them, and they will all start out the same -- mine start out like this:

Process: lpd [7781]

Path: /usr/libexec/cups/backend/lpd

Identifier: lpd

Version: ??? (???)

Code Type: X86-64 (Native)

Parent Process: cupsd [7775]

Date/Time: 2011-07-01 14:24:15.191 -0500

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

What this is telling me is that /usr/libexec/cups/backend/lpd (which got replaced in the 10.6.8 upgrade) is broken. So I went to /usr/libexec/cups/backend, renamed lpd to lpd.10.6.8 and then got a/usr/libexec/cups/backend/lpd file off of a 10.6.7 machine and replaced it with that.

That seems to do the least violence to the filesystem -- changes a single file, and if Apple ever figures out the problem and distributes an update with a new and fixed /usr/libexec/cups/backend/lpd, then it will just seamlessly go back to a standard OS X install.

Many thanks again to Lykeios! After days of being unable to print on our Xerox after upgrading (?), running your program has reset everything back to normal. This issue has been dragging for weeks and I feel very concerned that the Apple people haven't fixed it within a couple of days. Should we really buy LION in view of bugs like this?

This fixed several of my Mac's quickly and easily. Click the link or read below.

http://reviews.cnet.com/8618-13727_7-20074154.html?communityId=2123&targetCommun ityId=2123&blogId=263&messageId=10987461&tag=mncol

1. OS X 10.6.8 Update

Apple's 10.6.8 update has caused some printers to break (printers that have been working fine for years), and we are looking for a resolution to this from Apple. For users who are seeing this problem in the field and can't wait for a fix from Apple, there is a workaround.

This workaround consists of adding a *cupsSNMPSupplies: False line to a ppd file in the /etc/cups/ppd folder. You'll need administrative privileges to perform this workaround. Detailed steps are outlined below.

For this example we will use ColorPrinter as the name of the printer affected by the 10.6.8 update.

1. From the Finder menu choose Go, then Go to Folder...

2. Enter /etc/cups/ppd in the Go to Folder dialog box and choose Go.

3. Find the ppd named ColorPrinter.ppd. (This is the same name as the ColorPrinter in Print and Fax with a .ppd extension. )

4. Drag the ColorPrinter.ppd to the Desktop.

5. Open the ColorPrinter.ppd with TextEdit.

6. At the end of the PPD add the following line exactly as written: *cupsSNMPSupplies: False

7. Save the modified ColorPrinter.ppd to the Desktop.

8. From the /etc/cups/ppd folder, move the original ColorPrinter.ppd to the trash. Authenticate when prompted.

9. Drag the modified ColorPrinter.ppd from the Desktop to the /etc/cups/ppd folder. Authenticate when prompted.

10. Printing should now work as expected. (You may have to start the print queue if it was previously paused

The .ppd hack worked for me.

HP Color Laserjet network printer.

No problem printing yet but now i have a message saying there is not enough ink in the toners although they are new (Lexmark E120N & Kyoceramita KM1650).

Lexmark C540, Brother MFC6490CW seem fine for the moment.

Someone has an Epson Stylus Photo RX640 ?

Thanks !

I tried this fix on a machine that had a time machine backup and it worked, but I'm having trouble getting the lpd file to copy to another machine that needs to be repaired. Ive tried copy and pasting, attaching the file in an email, I've tried copying from desktop to desktop, but I can't get it to work. How do I fix this machine that doesn't have Time Machine backup?

I thought I initially solved the problem by turning off SNMB on the networked printer (Konica Minolta C253), but turning off SNMB resulted in compromising the PC printer server.

The second idea I came up with was to try printer sharing. As long as the Mac that is doing the sharing (serving) is running 10.6.7 or earlier, then it should work. It's working for us (it's a short term fix until Apple resolves the problem).

Posted a fix on my blog, check it out here:

http://vcboy.com/mac-users-after-updating-to-10-6-8-getting-paused-printer-messa ge-fixed/

Download from:

http://s.vcboy.com/fixprinters

I finally got the lpd replaced on a machine that didn't have Time Machine backup. Thanks cathy fasano for the info. Does anyone know when Apple will fix this problem?

Hey Warrenwawa I do and have fixed it for myself - all you need is a backup from before Apple's Epson driver update 2.7. If you have one then it's a pretty easy fix. If not then I think it's possible to sort it for now by uninstalling and reinstalling Gutenprint drivers ( http://gimp-print.sourceforge.net/MacOSX.php ). Or download Apple's Epson driver update 2.6 ( http://support.apple.com/kb/DL900 ) and install that - just bear in mind that it's 800mb+ to download ... as my connection is really slow at the moment I haven't been able to test that method yet.

Ok..

For me basically I checked system.log in the Console utility while trying to print and spotted this info:

iMac24-2 EPSON_Stylus_Photo_RX640[993]: Error loading /Library/Printers/EPSON/InkjetPrinter2/MW/IraMW1.framework/IraMW1: dlopen(/Library/Printers/EPSON/InkjetPrinter2/MW/IraMW1.framework/IraMW1, 265): no suitable image found. Did find:\n /Library/Printers/EPSON/InkjetPrinter2/MW/IraMW1.framework/IraMW1: truncated mach-o error: segment __LINKEDIT extends to 148880 which is past end of file 148872

My fix:

Search for and the 'IraMW1.framework' folder via - /Library/Printers/EPSON/InkjetPrinter2/MW/IraMW1.framework

Then trash all the files inside the 'IraMW1.framework' folder (as it contains the offending 'IraMW1' file) and replace with the contents from the same folder in a pre-2.7 backup.

See my process in a little more detail here: https://discussions.apple.com/thread/3159754?answerId=15588737022#15588737022

Hope that helps! 🙂

Thank You. Your Terminal command worked for me.