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

Bug#777286: foo2zjs: cups to cups via IPP with foo2zjs processed on client fails



On Mon 16 Feb 2015 at 12:47:04 +0100, Oskar Bożek wrote:

> Hello again,
> 
> IMHO there is a bug - mime type is incorrect in cups to cups scenario:
> 
> d [15/Feb/2015:16:09:18 +0100] add_file(con=0xb891d028[15], job=843,
> filetype=application/vnd.cups-pdf, compression=1)
> which causes filtering by foomatic and fail:
> D [15/Feb/2015:16:13:33 +0100] [Job 844] Cannot process "<STDIN>":
> Unknown filetype.
> 
> with windows client the mime is set correctly:
> d [15/Feb/2015:16:02:31 +0100] add_file(con=0xb891d028[15], job=842,
> filetype=application/octet-stream, compression=0) so it works.
> 
> I don't know if mime is set (forced?) by the client or detected by the
> server - although, as the data is already in zjstream it should not be
> detected as application/vnd.cups-pdf, as zjstream doesn't have its own
> application/octet-stream should be used.

I think the mime type is provided to the server by the client. The same
issue you raise is discussed at

  https://www.cups.org/str.php?L4494
 
> It's much less important as a working bypass is known, but it should
> work with default settings anyway.
> 
> If You need full debug logs of both scenario - I'll post them. If You
> choose to close this bug - it's fine too, as it works.

>From my point of view it would be useful to compare what I get with your
logs. So yes, please attach them to a mail sent here.

> Thank You for the working solution anyway

You're welcome.

Regards,

Brian.
> --
> Best Regards
> Oskar
> 
> 2015-02-16 12:23 GMT+01:00 Brian Potkin <claremont102@gmail.com>:
> > On Sun 15 Feb 2015 at 12:37:06 +0100, Oskar Bożek wrote:
> >
> >> Ok, so what should I try now? How I should prevent double-processing?
> >
> > If you are insisting on processing on the client
> >
> >   lpadmin -p <whatever> -v <whatever> -E -m raw
> >
> > on the server. This works for me.
> >
> > None of the problems you are having appear to be due to bugs in the
> > printing system. I'd suggest debian-user may be a more appropropiate
> > place to discuss them.
> >
> > Regards,
> >
> > Brian.


Reply to: