Printing PDF files from Linux to HP printer fails and causes a "Broken Pipe" error

Bug #1356565 reported by Jamison Warren
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
HPLIP
New
Undecided
Unassigned

Bug Description

We are trying to print a pdf file that was created from autocad that has coloring and 3d imaging. The printer is an HP LaserJet Pro MFP M521dn, we other HP printers having the same results. When the file prints it may print some pages but the pages with any sort of color or shading fail then in CUPS I get a "Broken Pipe" error message. We are using the following command:

lpr -o fitplot -P (printername) (filename)

I downloaded and installed hplip-3.13.8_rhel-5.0.x86_64.rpm and configured the printer to use this. still received problems but the error was different /usr/lib/cups/backend/hp failed

Next I tried using the command and had mixed results with it, sometimes the file would print sometimes it wouldn't

pdftops (filename) - | lpr -P (printername)

Revision history for this message
goutam kodu (goutam-hplip) wrote :

Hi Jamison,

Can you run command "hp-check" in terminal and paste its output here.

Thanks,
Goutam

Revision history for this message
Jamison Warren (jwarren) wrote :

Hi Goutam,
Sorry fo rthe delay here is the log file from the "hp-check"

Thanks,
Jamison

Revision history for this message
goutam (goutamkk) wrote :

Hi Jamison,

Can you please try deleting the print queues for printer "M521" in "system-config-printer" and re-configure the print queue using command "hp-setup" in terminal.

Fire a print job to that queue and check if you get the same error "/usr/lib/cups/backend/hp failed". If the issue is still present run command "su -c 'hp-logcapture' " in terminal. This tool will generate a tar file hplip_troubleshoot_logs.tar.gz . Please attach this file here for analysis of log files.

Thanks,
Goutam

Revision history for this message
Jamison Warren (jwarren) wrote :

Hi Goutam,
I had tried using the "hp-setup" and this did not help but that is also when we started getting the message "/usr/lib/cups/backend/hp failed".

I will try to created the printer again with the "hp-setup" and generate the log file

Thanks,
Jamison

Revision history for this message
Jamison Warren (jwarren) wrote :

hi Goutam,
I deleted theprinter from CUPS and created it using hp-setup -i
I then sent one of the pdf files over using the lpr -o fitplot -P option. The file is in the print queue but just sitting there and no error message yet.

Thanks,
Jamison

Revision history for this message
Jamison Warren (jwarren) wrote :

There is no error message but after 10 minutes only page 1 of 2 has printes

Revision history for this message
Jamison Warren (jwarren) wrote :

Hi Goutam,
After 26 minutes the printer has the error message "/usr/lib/cups/backend/hp failed". Created a second log once the printer showed this message

Revision history for this message
Jamison Warren (jwarren) wrote :

Hi Goutam,
Any updates on this yet?

Revision history for this message
goutam (goutamkk) wrote :

Hi Jamison,

Thanks for attaching the log files. We are not able to reproduce the issue here and the log files are not giving much information.

Lets try to setup the device with cups socket backend instead of hp.

Follow the below steps:

1. Delete the existing print queue for this printer by running command "hp-setup -i -r" in terminal.

2. unzip the PPD file.
su -c"gunzip /usr/share/ppd/HP/hp-laserjet_500_mfp_m521-ps.ppd.gz"

3. Configure the print queue using lpadmin command.
su -c "lpadmin -p M521dn -E -v socket://<IP_address_of_the_printer>:9100 -P /usr/share/ppd/HP/hp-laserjet_500_mfp_m521-ps.ppd "

4. print the file now and check if the issue is resolved.

Thanks,
Goutam

Revision history for this message
Jamison Warren (jwarren) wrote :

Hi Goutam,
I do not have the following folder /usr/share/ppd/HP/hp-laserjet_500_mfp_m521-ps.ppd.gz
however I can find this file /usr/share/cups/model/HP/hp-laserjet_mfp_m521-ps.ppd.gz

Thanks,
Jamison

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.