[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#769058: cups: "/usr/lib/cups/filter/foomatic-rip failed" after last CUPS update



On Tue 25 Nov 2014 at 10:58:01 -0430, Tom Maneiro wrote:

> Sorry for the delay, it has been a very busy week for me, and for some reason
> my last reply never arrived to the tracker.

No problem.
 
> I tried setting the print queue to raw, but... I can't still print.
> I even went and created a separate queue for the CL3005W in raw mode (device
> URI is "usb://KONICA%20MINOLTA/mc1600W?serial=06796", and I named the queue
> "CL3005Wr"), then I setup one of my remote clients to print to it. Not only
> nothing came out of the printer, this time I didn't even got any error on the
> server! Dunno if somehow the print job got mangled and the printer rejected the
> bad data (I did noticed that the printer "Ready" LED blinked briefly during one
> of the failed attempts), or it simply went to nowhere - I'll have to recheck
> this later.

I altered the queue on an unstable client we had in a previous mail to

  lpadmin -p test -v ipp://192.168.7.65:631/printers/CL3005Wr -E -m <the 1600W foo2zjs PPD>

On a Wheezy server sharing its queues I did

  lpadmin -p CL3005Wr -v file:/tmp/TEST -E -m raw

Printing /etc/debian_version produces TEST, which has the same size and
is the same type as the test file produced previously on the client.

With your printer I would expect TEST to print from the server with
something like 'cat TEST > /dev/usb/lp0' and by changing the device URI
to "usb://KONICA%20MINOLTA/mc1600W?serial=06796". I am at a loss to
understand why you have been unable to.
 
> Remote Windows clients can still print to the unmodified queue, sane as for
> anything running older CUPS versions. In fact, I've been using the same
> server/client setup since 2007 or so, in several Linux flavors (including older
> Debian Sid servers). using clients both in Windows and several Linux distros,
> and only in this year I had CUPS patches break it, because SOMEHOW it's now
> considered a "you're doing it wrong" case. At most I think the whole
> FINAL_CONTENT_TYPE should be exposed as an user-modifiable option somewhere in
> the config files.

Considerations such as altering the behaviour of cups are above my pay
grade. :)

Regards,

Brian.


Reply to: