How to test cups printer system

Tim Waugh twaugh at redhat.com
Fri Nov 21 13:26:25 UTC 2008


On Fri, 2008-11-21 at 08:00 -0500, Dave Feustel wrote:
> There are quite a few reports of the "not connected" problem found by
> Google for a variety of operating systems using CUPS..  Is there a
> simple way to test the printer directly (eg bypassing the entire CUPS /
> LPD system )?

Not usefully.  The problem is that the CUPS backend has not been able to
"connect" to the device, whatever that means for the particular backend
type.  In IPP terms, the "connecting-to-device" state is still present
for the printer object, and has been for a while (60 seconds).

What this really means can depend on which backend is being used.  For
usb://... URIs it means that the USB device node couldn't be opened; for
hp://... URIs it means that HPLIP wasn't able to find/connect to the
device.  For network-type URIs (other than ipp) it might be a network
level problem, etc.

I'd really like to get the printing troubleshooter working in this
instance, as it performs different diagnostic checks depending on the
backend in use.

Tim.
*/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <http://listman.redhat.com/archives/fedora-list/attachments/20081121/162d21c9/attachment-0001.sig>


More information about the fedora-list mailing list