Date: Sat, 4 Feb 2012 11:22:28 GMT From: Oliver Hartmann <ohartman@zedat.fu-berlin.de> To: freebsd-gnats-submit@FreeBSD.org Subject: ports/164759: print/cups: printing malfunction "Unable to get print job status." or "The printer is busy." Message-ID: <201202041122.q14BMSaN009362@red.freebsd.org> Resent-Message-ID: <201202041130.q14BU9XJ040144@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>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:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201202041122.q14BMSaN009362>