From owner-freebsd-questions@FreeBSD.ORG Tue Feb 7 10:49:27 2012 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 69DAF106568A for ; Tue, 7 Feb 2012 10:49:27 +0000 (UTC) (envelope-from freebsd-questions@herveybayaustralia.com.au) Received: from mail.unitedinsong.com.au (mail.unitedinsong.com.au [150.101.178.33]) by mx1.freebsd.org (Postfix) with ESMTP id 11CA48FC1F for ; Tue, 7 Feb 2012 10:49:26 +0000 (UTC) Received: from mail.unitedinsong.com.au (bell.herveybayaustralia.com.au [192.168.0.40]) by mail.unitedinsong.com.au (Postfix) with ESMTP id 249A25C46 for ; Tue, 7 Feb 2012 21:02:01 +1000 (EST) Received: from laptop1.herveybayaustralia.com.au (laptop1.herveybayaustralia.com.au [192.168.0.177]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.unitedinsong.com.au (Postfix) with ESMTPSA id EA80A5C45 for ; Tue, 7 Feb 2012 21:02:00 +1000 (EST) Message-ID: <4F3100A6.3000207@herveybayaustralia.com.au> Date: Tue, 07 Feb 2012 20:44:54 +1000 From: Da Rock User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:7.0.1) Gecko/20111109 Thunderbird/7.0.1 MIME-Version: 1.0 To: freebsd-questions@freebsd.org References: <4F30E384.1080003@mail.zedat.fu-berlin.de> In-Reply-To: <4F30E384.1080003@mail.zedat.fu-berlin.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: print/cups: CUPS-1.5.0 IPP protocoll issues -> no printing possible on IPP capable network printers X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-questions@freebsd.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Feb 2012 10:49:27 -0000 On 02/07/12 18:40, O. Hartmann wrote: > 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. I know the feeling- try it with network (wifi particularly...) :) What models out of curiosity? Have you tried other models? As for the patch situation: try the maintainer of cups port, but that does require a wait of about 2 weeks (doesn't sound like you can wait) so perhaps try ports@. Or both cc'ing ports@... HTH