Red Hat Bugzilla – Bug 91359
cannot print with hp 3420 configured with printconf
Last modified: 2007-04-18 12:53:54 EDT
Description of problem:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.add a printer in printconf
2.select hp 3420 (hpijs driver)
3.send a cups test page
no page at all is printed, the printconf gui says Media Tray Empty!
a page should be printed
Created attachment 91866 [details]
messages takaen for /var/log/cups/error_log (full debug is set)
The 'Media Tray Empty!' message is harmless, and isn't the cause of this
problem. (It is mistaken, and this bug has since been fixed.)
Please attach the output of 'printconf-tui --Xexport'. Thanks.
Created attachment 91901 [details]
output of printconf-tui --Xexport
Please fetch this file:
Uncompress it like this:
Then send it to the printer like this (as root):
cat hp3420 > /dev/usb/lp0
Does that give any better results? This is the output from a newer version of
the printer driver (hpijs) for that model.
[root@164-tor-1 download]# chown root:root hp3420
[root@164-tor-1 download]# cat hp3420 > /dev/usb/lp0
a perfect test page was printed, what do I have to upgrade to make it work
with printconf to all users?
Just the hpijs package. The current rawhide (untested) version, which
hp3420.bz2 was generated by, is hpijs-1.4-2. You can get it from
You could try upgrading that package and seeing if you can print afterwards; if
not, obviously the problem is elsewhere.
I installed hpijs 1.4 from rawhide. Now I'm getting the following message from
/var/log/messages when trying to print the cups test page
May 24 14:09:11 164-tor-1 hpijs: unable to read client data err=-2
Can you give me any hints where elsewhere to look, or what logs to take?
Perhaps you also need to upgrade ghostscript.
You could set 'LogLevel debug' in /etc/cups/cupsd.conf and look in
/var/log/cups/error_log for more logs.
Created attachment 91943 [details]
/var/log/cups/error_log with full debug turned on, when trying to print test page
Did you also try upgrading ghostscript?
After upgrading ghostscript it works perfectly
thanks for your help