Red Hat Bugzilla – Bug 857388
HP deskjet 6940 garbled print
Last modified: 2012-09-20 04:32:21 EDT
Description of problem:
HP Deskjet 6940 printer does not print or produces garbled print. This printer worked correctly under Fedora 14. The printer is connected by ethernet through a second NIC card using a dedicated IP address and 'ifconfig' shows no transfer errors during processing.
HPLIP does not see this printer automatically during configure and I have to manually specify it's IP address for HPLIP to find and configure the printer. This was the same in Fedora 14. This printer has internal web pages and access to these web pages from a browser is error free. A full page test print initiated from the printer's control panel works correctly.
The printer is currently configured by hplip version 3.12.9. This is an upgrade from the official Fedora version 3.12.6 which exhibited this same behavior. The upgrade didn't help but appears to work as far as configuring the printer. Results of printing are the same as with the fc17 version.
The error log; /var/log/cups/error.log reports; gstoraster failed. Then reports 'stopped unresponsive printer'.
Version-Release number of selected component (if applicable):
hplip-3.12.9 (from HP website)
Steps to Reproduce:
1.Select print option from a pdf or doc viewer.
There is a long delay before printing begins. Results are random. Mostly prints first few lines and then ejects or prints garbled bits from the original document.
Under Fedora 14 I regularly printed the pdf musical scores for my classical guitar lessons.
I have gone through the usual gyrations of uninstalling and reinstalling software and device configurations with no change.
Please follow the troubleshooting procedure outlined here:
You should end up with a troubleshoot.txt file which you should attach to this bug report.
Created attachment 613807 [details]
this is the troubleshoot.txt file produced by following the instructions in the webpage you pointed to.
The 'test page' was used for this test. The HP Device manager Showed the printer status as 'job started. Six minutes later it posted an 'idle' status, six minutes after that it posted a 'job continuing' status but the printer never actually did anything.
The hp backend stopped with a SIGPIPE signal:
D [17/Sep/2012:17:57:58 -0400] PID 2595 (/usr/lib/cups/backend/hp) did not catch or ignore signal 13.
Can you see anything in /var/log/messages around that time from hp?
(In reply to comment #3)
> Can you see anything in /var/log/messages around that time from hp?
I've made a scratch-build with debug messages in hp backend enabled.
Can you try that, Bob ?
I just uncommented #define HP_DEBUG in prnt/backend/hp.c
Hope it's everything we need to do to see the debug messages.
I know there can be set hpLogLevel in cupsd.conf but that's AFAICT no related to these backend debug messages.
Created attachment 614297 [details]
/var/log/messages during troubleshooting test page print
yum erased the original hplip files and rpm installed your debug files.
These are the log file messages during that time.
I will also attach the troubleshoot.txt file
Created attachment 614299 [details]
New troubleshoot.txt from 'test' hplip
(In reply to comment #5)
> /var/log/messages during troubleshooting test page print
I'm glad it (debug messages) works.
Sep 19 05:09:12 localhost hp: io/hpmud/jd.c 561: timeout write_channel hp:/net/Deskjet_6940_series?ip=169.254.78.213
Sep 19 05:21:11 localhost hp: io/hpmud/jd.c 567: unable to write_channel: Connection timed out hp:/net/Deskjet_6940_series?ip=169.254.78.213
Can you create a new printer queue (for example with system-config-printer) using the 'AppSocket/HP JetDirect' backend and print something? That way we'll know if that's really a hp backend problem or some other network communication problem. Thanks.
Sorry to switch horses in the middle of a race but I received the network hub I ordered last week and installed it; putting both the internet modem and the printer on the motherboard's ethernet connection. The printer is now functioning normally. I removed the network card from my PC since it's no longer needed.
Just to repeat a point,the dual NIC lash-up worked fine under FC14. I'm sure the second NIC was functioning because I could access the printers built-in web pages and printing actually did start sometimes and the first few lines were correct. Also 'ifconfig' showed no signs of data transfer errors on the second NIC.
I doubt we are able to investigate the previous problem any further, closing then. I'm happy it works now.