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

[Brian Potkin <claremont102@gmail.com>]

Hello again, Tom. Still using your Delcop CL3005W we see! Thank you for
the report.

On Mon 10 Nov 2014 at 21:37:00 -0430, Tom Maneiro wrote:

> After the last CUPS packages update (1.7.5-7) on all of my Jessie boxes at
> home, I've been unable to print to my Konica-Minolta magicolor 1600W, which is
> plugged to a old box running Wheezy. My last successful print jobs were under
> 1.7.5-5, a week ago. Due to resource constraints on the print server box, using
> the remote print queue isn't an option (the print driver -foo2zjs- is very
> resource-hungry and the print server only has 128MB RAM, hence the queues must
> be local for the clients so they can crunch the print data before sending it to
> the server, and ultimately to the printer). Printing still works from Windows
> hosts, so there is nothing to blame in the server
> 
> After raising the debug level on CUPS, and taking a look at error_log, I've
> noticed something... odd:

[Debug2 log snipped]

> So... the filter (foomatic-rip) successfully exits, yet it fails!? This makes
> no sense.

Please would you set up a print queue with

   lpadmin -p test -v file:/home/tomman/test -E -m <the 1600W foo2zjs PPD>

Then

   lp -d test /etc/debian_version

followed by

   chmod 666 /home/tomman/test

if you want to switch away from the root account.

We want the information from

   ls -l /etc/debian_version
   ls -l /home/tomman/test
   file /home/tomman/test

How does the error_log compare with the one we have?

Regards,

Brian.