Print Jobs Stop on hp1320

jhogeterp

Registered
Hello,

I got into work this morning, tried printing on my hp1320 (connected through airport extreme), and the printing jobs automatically stopped. It has worked fine since I have had the printer and I can't relate the problem with anything that has changed on my system. I have tried printing to another printer and it works, so it seems to be limited to this one printer.

I have been working on this for hours and have tried everything! (not necessarily in order)

1. Reintstalling drivers (and deleting hptoolbox files)
2. Repairing disk permissions
3. Replacing cupsd.conf file
4. trashing cups folder and replacing with an empty one
5. Reset the Printing system
6. tried everything in "Printer Setup Repair" application
7. tried printing from a new user.

The printer is recognized, communicating over bonjour. Test page works (manually from the printer itself). I just don't know what to do.

My intel machine is running 10.4.9, ppd is 4.5.2 (from the 5.5.2 install).

I am pasting the info I am getting from cups error log. Can someone please help!

[23/Mar/2007:16:48:23 -0400] Saving printers.conf...
I [23/Mar/2007:16:48:30 -0400] Saving printers.conf...
I [23/Mar/2007:16:48:30 -0400] Printer 'hp_LaserJet_1320_series' started by ''.
I [23/Mar/2007:16:48:30 -0400] Started filter /usr/libexec/cups/filter/cgpdftops (PID 437) for job 1.
I [23/Mar/2007:16:48:30 -0400] Started filter /usr/libexec/cups/filter/pstops (PID 438) for job 1.
I [23/Mar/2007:16:48:30 -0400] Started filter /Library/Printers/hp/filter/hppostprocessing (PID 439) for job 1.
I [23/Mar/2007:16:48:30 -0400] Started backend /usr/libexec/cups/backend/mdns (PID 440) for job 1.
E [23/Mar/2007:16:48:30 -0400] PID 438 crashed on signal 5!
I [23/Mar/2007:16:48:30 -0400] Hint: Try setting the LogLevel to "debug" to find out more.
E [23/Mar/2007:16:48:30 -0400] PID 440 crashed on signal 5!
I [23/Mar/2007:16:48:30 -0400] Hint: Try setting the LogLevel to "debug" to find out more.
I [23/Mar/2007:16:48:30 -0400] Saving printers.conf...
I [23/Mar/2007:16:52:38 -0400] Saving printers.conf...
I [23/Mar/2007:16:52:38 -0400] Printer 'hp_LaserJet_1320_series' started by ''.
I [23/Mar/2007:16:52:38 -0400] Started filter /usr/libexec/cups/filter/cgpdftops (PID 455) for job 1.
I [23/Mar/2007:16:52:38 -0400] Started filter /usr/libexec/cups/filter/pstops (PID 456) for job 1.
I [23/Mar/2007:16:52:38 -0400] Started filter /Library/Printers/hp/filter/hppostprocessing (PID 457) for job 1.
I [23/Mar/2007:16:52:38 -0400] Started backend /usr/libexec/cups/backend/mdns (PID 458) for job 1.
E [23/Mar/2007:16:52:39 -0400] PID 456 crashed on signal 5!
I [23/Mar/2007:16:52:39 -0400] Hint: Try setting the LogLevel to "debug" to find out more.
E [23/Mar/2007:16:52:39 -0400] PID 458 crashed on signal 5!
I [23/Mar/2007:16:52:39 -0400] Hint: Try setting the LogLevel to "debug" to find out more.
I [23/Mar/2007:16:52:39 -0400] Saving printers.conf...

Thanks!
 
Is there any chance this is only one specific file that is having troubles? The error occurs in a background process called pstops (postscript to postscript), which adds some page options, counts pages and preps the file for the next filter.
Please try some other print jobs for troubleshooting. You may also want to use Reset Printer Setup, a menu item in Printer Setup (you'll have to re-Add the printer).
 
I have tried printing in many different applications, and the jobs stop in all of them. I have reset the printing system multiple times. It is driving me crazy! :)
 
I'd make a last ditch effort by downloading the Combo 10.4.9 updater and re-update. If that doesn't do it, time to reinstall OSX using the Archive & Install option in the installer.
 
Just to let anyone know who is having this same problem...

I fixed it by downloading cups from http://www.cups.org/ and reinstalling cups. It seems to have fixed the problem (must have overwritten a correupt file, possibly the "pstops" filter).

The only problem now is that the persmissions are screwed up (I don't have permission restart the printing system), but the problems are not recognized by disk utility. But the printer works!

Thanks for your help!
 
Back
Top