On Wed 10 Jul 2013 at 15:11:37 -0400, Daniel Kahn Gillmor wrote:
> Brian Potkin writes:
>
> > Please see how the ipp14 backend performs. You might also want to look
> > at bug #712719.
>
> Ah! thank you. Printing does work to this machine when i do
>
> lpadmin -p cringer -v ipp14://cringer/
>
> So i'm sticking with that as a workaround for now.
>
> The tight loop of DEBUG: error output on the regular ipp backend in the
> event of a Validate-Job failure is still probably a bug in cups -- it
> should at least fail gracefully, instead of spinning like that. But it
> sure is nice to have the workaround :)
It is possible that
*
debian/patches/ipp-backend-abort-the-outer-loop-if-we-get-a-failure-from-send-document.patch,
debian/patches/ipp-backend-could-get-stuck-in-an-endless-loop-on-certain-network-errors.patch:
Prevent IPP backend from falling into an infinite loop in certain
situations (CUPS STR #4194).
in unstable's cups is a fix. Testing on an unstable install would be a
way of finding out. However, it may be sufficient to use the ipp backend
from 1.6.2-10. (If this is not a valid procedure, I hope someone will
say so).
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
