Can't print since CUPS (?) update

[dhfx]

I have 2 H-P printers set up thru CUPS on Hardy. I was always able to print fine but I just tried printing from kpdf and CUPS thinks both printers are offline. I can queue test pages but they never get to the printer. The print job status windows show both printers stopped. Using SystemSettings > Printers, I tried stopping and starting each printer - no effect. When I try to cancel the job in the print status window, I get a CUPS server error 'client-error-not-possible'.

But here's the funny thing: Both printers are shared via Samba. When I try to print remotely from a WinXP machine, it works!

Anyone have any idea what's going on?

[goinglinux]

Re: Can't print since CUPS (?) update

I had a similar problem after I installed Kubuntu Hardy on my HP laptop. I was connecting directly over the network using the URI socket://XXX.XXX.X.XXX:9100. The XXX represents the IP address of the LinkSys wireless print server, and 9100 is the first port on the print server (WPS54GU2).

When I connected directly by USB to my OfficeJet 6110 and via Parallel to my LaserJet 2100, everything worked great. When I connected over the network (wired or wireless), it took almost 15 minutes for each page to reach the printer and actually be printed. Both printers did the same thing. To make it even more aggravating, my other computer with Kubuntu Gutsy installed, was connected in exactly the same way, but had no problem printing over the network. There is definitely something different in the way that Hardy connects to printers!

The solution came, unfortunately, when 3 things changed at once. As a result, I can't really tell which change (or a combination of them) resolved the issue, but both printers now work over the network for all my computers. I'll list the 3 things that changed in the event that one or more of them might resolve your problem.

• The first change is that I replaced my Belkin F5D7230-4 router with an older D-Link DI-524. I discovered that the Belkin was using some advanced settings that were supposed to improve quality of service, but when I turned those "features" off, (and eventually replaced the router due to an overheating problem) my network performance improved overall.
• The second change is that new printer drivers were provided in a regular Kubuntu update, so I am using different drivers than I was before I changed the router
• The third change is that I updated to the 2.6.24-19-generic kernel.

I hope some of that helps with your situation.

[Cotopaxi]

Re: Can't print since CUPS (?) update

Try the instructions from this post:

http://kubuntuforums.net/forums/inde...opic=3089184.0

Go to the second port of tomstrong and follow the steps carfully.

I tried this one out after more than 8 weeks without printer and several re-installations of Kubuntu. This trick brought my printer back to live!

[dhfx]

Re: Can't print since CUPS (?) update

Cotopaxi: Thanks for the suggestion. I checked the referenced page, and it turns out I had already made that mod about 4 months ago. Tried turning the printer off and on - no luck.

Opened the CUPS screen at localhost:631 and checked the error log. Here's what I found after I tried to print a test page:

I [23/Sep/2008:20:59:52 -0500] [Job 91] Adding start banner page "none".
I [23/Sep/2008:20:59:52 -0500] [Job 91] Adding job file of type application/postscript.
I [23/Sep/2008:20:59:52 -0500] [Job 91] Adding end banner page "none".
I [23/Sep/2008:20:59:52 -0500] [Job 91] Queued on "HP-G85" by "homeuser".
I [23/Sep/2008:20:59:53 -0500] [Job 91] Started filter /usr/lib/cups/filter/pstops (PID 5871)
I [23/Sep/2008:20:59:53 -0500] [Job 91] Started filter /usr/lib/cups/filter/pstoraster (PID 5872)
I [23/Sep/2008:20:59:53 -0500] [Job 91] Started filter /usr/lib/cups/filter/rastertogutenprint.5.0 (PID 5873)
I [23/Sep/2008:20:59:53 -0500] [Job 91] Started backend /usr/lib/cups/backend/hp (PID 5874)
E [23/Sep/2008:20:59:55 -0500] PID 5872 (/usr/lib/cups/filter/pstoraster) stopped with status 1!
I [23/Sep/2008:20:59:55 -0500] Hint: Try setting the LogLevel to "debug" to find out more.
E [23/Sep/2008:21:00:05 -0500] [Job 91] Job stopped due to filter errors.

Using System Settings > Printers I tried stopping and restart the printer:

E [23/Sep/2008:21:00:18 -0500] Pause-Printer: Unauthorized
I [23/Sep/2008:21:00:18 -0500] Saving printers.conf...
I [23/Sep/2008:21:00:18 -0500] Printer "HP-G85" stopped by "root".
E [23/Sep/2008:21:00:22 -0500] Resume-Printer: Unauthorized
I [23/Sep/2008:21:00:22 -0500] Saving printers.conf...
I [23/Sep/2008:21:00:22 -0500] Printer "HP-G85" started by "root".

Tried the same thing on my other printer:

I [23/Sep/2008:21:18:46 -0500] [Job 93] Adding start banner page "none".
I [23/Sep/2008:21:18:46 -0500] [Job 93] Adding job file of type application/postscript.
I [23/Sep/2008:21:18:46 -0500] [Job 93] Adding end banner page "none".
I [23/Sep/2008:21:18:46 -0500] [Job 93] Queued on "HP-LJ4L" by "homeuser".
I [23/Sep/2008:21:18:46 -0500] [Job 93] Started filter /usr/lib/cups/filter/pstops (PID 6008)
I [23/Sep/2008:21:18:46 -0500] [Job 93] Started filter /usr/lib/cups/filter/foomatic-rip (PID 6010)
I [23/Sep/2008:21:18:46 -0500] [Job 93] Started backend /usr/lib/cups/backend/parallel (PID 6011)
I [23/Sep/2008:21:18:47 -0500] [Job 93] Completed successfully.

The pilot light on HP-LJ4L went on, but nothing came out.

What would explain the "filter error" on HP-G85?

[dhfx]

Re: Can't print since CUPS (?) update

Update 30Sep2008: Still can't print a test page on either printer.

Searched the forum again and found in post by marek_online,
http://kubuntuforums.net/forums/inde...25461#msg25461
"It turns out that printing from OpenOffice worked fine, and also from Firefox, suggesting that kprinter might have been the problem, rather than CUPS."

So, tried printing direct from Firefox: both printers work. Original problem arose with kpdf; it wouldn't print, and it still won't.

marek_online wonders if problem is with kprinter in KDE 3.5.3, and I found some other posts suggesting problems with kprinter in 3.5.3; I'm using 3.5.9 under Hardy with the 2.6.24-19-generic kernel.

Still troubleshooting this one. Further suggestions, anyone?