Bug#700243: cups: Could not print with a wheezy client and hpijs driver
Hello Jérôme,
Sorry for the slight delay in responding but, for some reason or other,
your mail did not show up in on the debian-printing mailing list, where
I usually keep an eye out for such things. Anyway, not to worry.
Your logs and the PPD file were very, very useful. Thank you.
On Tue 02 Apr 2013 at 17:40:29 +0100, Jérôme Frgacic wrote:
> I've followed your instructions.
> I attach the logs and the ppd file to the mail.
> It seems that there is an authentication problem on the server.
Your problem arises on the Wheezy client. You send a PDF:
I [02/Apr/2013:18:01:21 +0200] [Job 17] File of type application/pdf queued by "jerome".
cups-filters processes it ok:
D [02/Apr/2013:18:01:21 +0200] PID 15279 (/usr/lib/cups/filter/pdftopdf) exited with no errors.
The renderer uses ghostscript (gs) to contact an IJS server and turn the
PDF into something the printer can understand and process:
D [02/Apr/2013:18:01:22 +0200] [Job 17] Starting renderer with command: gs -dFirstPage=1
-q -dBATCH -dPARANOIDSAFER -dQUIET -dNOPAUSE -dNOINTERPOLATE -sDEVICE=ijs -sIjsServer=hpijs
-dDEVICEWIDTHPOINTS=595 -dDEVICEHEIGHTPOINTS=842 -sDeviceManufacturer="HEWLETT-PACKARD"
-sDeviceModel="HP Color LaserJet 2600n" -dDuplex=false -r300
-sIjsParams=Quality:Quality=4,Quality:ColorMode=0,Quality:MediaType=0,Quality:PenSet=2,
Quality:SpeedMech=1,PS:MediaPosition=7
-dIjsUseOutputFD -sOutputFile=- /var/spool/cups/tmp/foomatic-m1GsWx
The renderer encounters an error and stops:
D [02/Apr/2013:18:01:22 +0200] [Job 17] Possible error on renderer command line or
PostScript error. Check options.Kid3 exit status: 3
D [02/Apr/2013:18:01:22 +0200] PID 15280 (/usr/lib/cups/filter/foomatic-rip) stopped with status 9.
I think the part of the gs command line which could be confusing the IJS
server is
-sDeviceModel="HP Color LaserJet 2600n"
It gets this from the PPD file. If you look at the gs command on the
server you will see
-sDeviceModel="deskjet 5600"
which is known to work. If you particularily want to use hpijs on the
client (or just want to confirm this is the likely source of the bug)
you could simply copy the Squeeze PPD over to it.
So this looks like a bug in the PPD file or whatever generates it on
testing/unstable. I have been able to reproduce it using a file device
but am unsure which package it should be reassigned to. It would save me
having to think or make a mess of it if someone (hello, Odyx :)) did
know.
> > Was the print queue set up from cups web interface at localhost:631?
>
> Sorry, I don't understand the question. What did you mean by that ?
Printers are frequently set up by using
http://localhost:631
in a browser. But there are other ways.
Cheers,
Brian.
Reply to: