Re: How to test cups printer system

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, Nov 21, 2008 at 08:57:23AM -0500, Dave Feustel wrote:
> On Fri, Nov 21, 2008 at 01:26:25PM +0000, Tim Waugh wrote:
> > 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.
> > */
> 
> The troubleshooting function seems to always stop responding as soon
> as the printer is selected and the 'foreward' button is selected.
> 
> There is a way (which I have forgotten) to send data directly to the
> printer port. I would like to try that just to verify that the printer
> port itself is working.

If the printer itself can print plain text when you send it plain text (not all can)
you could try something like:

	ls -l > /dev/device

where /dev/device is whatever device node the printer is attached to.

-- 
-------------------------------------------------------------------------------
    Under no circumstances will I ever purchase anything offered to me as
    the result of an unsolicited e-mail message. Nor will I forward chain
    letters, petitions, mass mailings, or virus warnings to large numbers
    of others. This is my contribution to the survival of the online
    community.
 --Roger Ebert, December, 1996
----------------------------- The Boulder Pledge -----------------------------

Attachment: pgp3uEx7a4Ol2.pgp
Description: PGP signature

-- 
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [Fedora Magazine]     [Fedora News]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Maintainers]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [Fedora Fonts]     [ATA RAID]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [SSH]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Tux]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Asterisk PBX]     [Fedora Sparc]     [Fedora Universal Network Connector]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux