Red Hat Bugzilla – Bug 214876
USB printer won't print
Last modified: 2007-11-30 17:11:48 EST
Description of problem:
HP2420D printer connected via USB will not print
Version-Release number of selected component (if applicable):
cups-1.2.5-2.fc6.8 (also seen on cups-1.2.4-9)
Steps to Reproduce:
1.Set up USB printer with system-config-printer
2.Try to print test page (or try to print any file)
Lpq lists printer as ready and printing, but nothing ever prints.
Printer should print.
The printer printed with no problem with FC5. The kernel is booted with the
noapic flag, since otherwise the computer hangs eventually. Various web sites
report this same problem by people with other brands of USB printers under FC6
(but before cups-1.2.5-2.fc6.8 was released).
You'll need to give me more information than that. All the USB printers I'm
using work fine tiwh FC6, and I haven't spotted reports from other people about
USB printers not working on the fedora-* mailing lists.
1. What make and model of printer are you using?
2. How did you configure the printer?
3. What does 'lpstat -s' say?
4. I'd like to see the error_log output from when you print a job, so please do
this (as root):
/sbin/service cups stop
Clear out the error_log file:
Start CUPS again:
/sbin/service cups start
Then print your job. When it fails, please attach the /var/log/cups/error_log
file to this bug report. Thanks.
Created attachment 141097 [details]
Printer error log
1. HP 2420D
2. Using system-config-printer, I selected HP 2420 with Postscript (default) and
used lp as the printer name.
3. device for lp: hp:/usb/hp_LaserJet_2420?serial=CNGJD22636
4. The error_log output is included in the attachment from Comment #2.
D [25/Oct/2006:22:02:16 -0400] [Job 2] %%Creator: Gnome Print Version 2.12.1
D [25/Oct/2006:22:02:16 -0400] [Job 2] %%CreationDate: D:20061025220216
Hmm, this isn't the test page. Could you please attach that print job if
possible? This page should help you find out what file it was:
Please attach the file to bug #212290, which is another instance of this bug. I
have closed this bug as a duplicate of it.
*** This bug has been marked as a duplicate of 212290 ***