Red Hat Bugzilla – Bug 456366
Printing certain documents results in garbled text
Last modified: 2009-01-09 01:41:15 EST
Description of problem:
Hello. I was attempting to print a document in OpenOffice Writer using a
Brother HL-1650 printer (the Make and Model according to the printer
configuration is 'Brother HL-1650 Foomatic/Postscript,' and I am using the
'AppSocket/HP JetDirect' method for printing). However, the printed document
showed garbled text (see 'cups-printout.png' in the 'cups.zip' attachment), as
opposed to what it should have been (see 'normal-printout.png' in the attachment
- this copy was printed from Windows XP with OpenOffice, so this is apparently
not an OpenOffice bug). No errors show up in the CUPS error log; it simply
indicates that the job has "Completed successfully." The 'messages' log file
also did not show any errors regarding CUPS.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Download the attached 'cups.zip' attachment.
2. Open 'cups.zip.'
3. Launch 'pol-sci-letter-1-demo.odt' from whichever zip utility opened.
4. Print the document.
The printout had garbled text. CUPS did not show any errors, and errors related
to CUPS were not present in any of the log files.
The printout should not have any problems.
Created attachment 312424 [details]
This zip archive contains the images of the expected printout and the actual printout, and the file for reproducing the problem.
I have not been able to reproduce this. I need further information:
1. Please attach the PPD for the queue from /etc/cups/ppd/.
2. Please try the printing troubleshooter (System->Administration->Printing from the main menu, then Help->Troubleshoot from the menu bar) and, when it asks you to print a test page, print from OpenOffice as before. You will probably end up with a troubleshoot.txt file -- please attach that here using the 'Add an attachment' link.
Created attachment 313510 [details]
This zip archive contains the PPD file and the troubleshoot text file.
Created attachment 313535 [details]
I've attached the result of File->Print, Print To File (PostScript) from OpenOffice.org. Please try this:
lp -dHL-1650_70N_BR-Script3 -oraw print-to-file.ps
Does that result in garbled output?
Yes, the printout comes out garbled.
Created attachment 313590 [details]
This picture proves the result using the command "lp -dHL-1650_70N_BR-Script3 -oraw print-to-file.ps".
Created attachment 313607 [details]
Here is a PDF generated by OpenOffice.org from Fedora 8 (2.3.0-6.15.fc8).
Please try printing it like this:
lp -dHL-1650_70N_BR-Script3 pol-sci-letter-1-demo.pdf
Does that look garbled?
Printing the exported PDF file does NOT result in garbled text.
This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '8'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 8's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 8 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Fedora 8 changed to end-of-life (EOL) status on 2009-01-07. Fedora 8 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.