Date: Tue, 07 Feb 2012 09:40:36 +0100 From: "O. Hartmann" <ohartman@mail.zedat.fu-berlin.de> To: Ports FreeBSD <freebsd-ports@FreeBSD.org>, freebsd-questions@freebsd.org Subject: print/cups: CUPS-1.5.0 IPP protocoll issues -> no printing possible on IPP capable network printers Message-ID: <4F30E384.1080003@mail.zedat.fu-berlin.de>
next in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigB9833C17585EE7A7A04AF816 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable We use a bunch of HP and Xerox printers across our network, all capable of being accessed via network over IPP protocoall (so they claim). Printing worked for me flawless on FreeBSD 8.2-STABLE, 9.0-CURRENT, now 9.0-STABLE on all boxes in question. Since updating cups to revision 1.5.0 (this is the most recent port version and I recently updated/recompiled the port and dependencies for all parts of CUPS either with CLANG and GCC 4.2.1), I get massive problems accessing printers on the network. Most HP printers accept a print job, but after accepting, CUPS reports printer has been stopped, can not obtain printer status. The job remains in the queue. Then I "restart" printer via CUPS, print job gets printed, but immediateley after printing has finished, the same problem occurs again: printer stopped - can not get printer status. Job remains still in the queue. Restarting printer via CUPS will start the game again, with the result of printing endless the same job, first in queue. I have to check whether the printer indeed has printed the job, delete the first queue entry, restart the printer again to get next job started ... and so on. A similar game on the Xerox printer facility. The printer reports "Unablae to get printer status", printing is here impossible! The XEROX printer is now attached to a Linux print server box running CUPS, an older CUPS on something like CentOS, I do not know what crap is running on the hardware. But: the printer works fine with older CUPS! Digging the internet revealed an issue reported in an Ubuntu forum/list, I already filed a PR (ports/164759). The Ubuntu report is about to be found here: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/877958 I was wondering if this "patch", whatever the Ubuntu fellows patched, couldn't be introduced to FreeBSD's CUPS port. Well, sorry about my impatience, but I'm floating like a dead man in the water, since I have to prepare printouts for a conference and printing is some kind of "neurological point" around here. Thanks for your patience ... Regards, Oliver --------------enigB9833C17585EE7A7A04AF816 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iF4EAREIAAYFAk8w44kACgkQU6Ni+wtCKv9nuAEApo5vuk7m4GUmGx4wybpWpmdp LY692mSEb4Y53F9Rqf0A/iRw+o6TkOKiUZRI8IROVOGJa3PQA8N5JTpwoidv6S1L =DmuL -----END PGP SIGNATURE----- --------------enigB9833C17585EE7A7A04AF816--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4F30E384.1080003>