From owner-freebsd-ports-bugs@FreeBSD.ORG Sat Feb 4 11:30:10 2012 Return-Path: Delivered-To: freebsd-ports-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 33DEB106564A for ; Sat, 4 Feb 2012 11:30:10 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id E8B5B8FC15 for ; Sat, 4 Feb 2012 11:30:09 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q14BU9A0040145 for ; Sat, 4 Feb 2012 11:30:09 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q14BU9XJ040144; Sat, 4 Feb 2012 11:30:09 GMT (envelope-from gnats) Resent-Date: Sat, 4 Feb 2012 11:30:09 GMT Resent-Message-Id: <201202041130.q14BU9XJ040144@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-ports-bugs@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Oliver Hartmann Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 138AC106566B for ; Sat, 4 Feb 2012 11:22:29 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from red.freebsd.org (red.freebsd.org [IPv6:2001:4f8:fff6::22]) by mx1.freebsd.org (Postfix) with ESMTP id 016A38FC12 for ; Sat, 4 Feb 2012 11:22:29 +0000 (UTC) Received: from red.freebsd.org (localhost [127.0.0.1]) by red.freebsd.org (8.14.4/8.14.4) with ESMTP id q14BMSpG009363 for ; Sat, 4 Feb 2012 11:22:28 GMT (envelope-from nobody@red.freebsd.org) Received: (from nobody@localhost) by red.freebsd.org (8.14.4/8.14.4/Submit) id q14BMSaN009362; Sat, 4 Feb 2012 11:22:28 GMT (envelope-from nobody) Message-Id: <201202041122.q14BMSaN009362@red.freebsd.org> Date: Sat, 4 Feb 2012 11:22:28 GMT From: Oliver Hartmann To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 Cc: Subject: ports/164759: print/cups: printing malfunction "Unable to get print job status." or "The printer is busy." X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Feb 2012 11:30:10 -0000 >Number: 164759 >Category: ports >Synopsis: print/cups: printing malfunction "Unable to get print job status." or "The printer is busy." >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-ports-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sat Feb 04 11:30:09 UTC 2012 >Closed-Date: >Last-Modified: >Originator: Oliver Hartmann >Release: FreeBSD 9.-STABLE/amd64 and FreeBSD 10-CURRENT/amd64 >Organization: FU Berlin >Environment: >Description: Installing cups-base and siblings and configuring printers, which seemed to work with cups 1.4.X prior to the update cups 1.5.0, all Hewlett-Packard priners show the follwoing behaviour: printing a job, then immediately change to status: Stopped - "Unable to get print job status.". All subsequent jobs get queued. When selecting "Restart printer" in printer management/admin, the next job in queue gets printed and the printer then changes immediately to the above reported status. Regarding to this behaviour, I found a thread describing this error and it is obviously a bug in cups 1.5.0: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/877958 It is Ubuntu Linux, but it seems they have had the same problem and they obviously solved it. It would be nice if we, FreeBSD people, also could benefit from that. >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: