Bug 781991 - Mangled printer output with Default Printer Language set to PDF, works with Postscript
Summary: Mangled printer output with Default Printer Language set to PDF, works with P...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: cups
Version: 16
Hardware: i686
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Tim Waugh
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-16 09:27 UTC by Kai Hambrecht
Modified: 2013-02-13 23:50 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-13 23:50:17 UTC
Type: ---


Attachments (Terms of Use)

Description Kai Hambrecht 2012-01-16 09:27:59 UTC
Description of problem:

For Postscript Printers (from CUPS), the default Printer Language Type is set to PDF instead of Postscript. This produces garbeled printer output. Setting Language to "Postscript (Level from Driver)" works, but the Printer Language will get reverted to PDF.

Version-Release number of selected component (if applicable):
libreoffice 3.4.4.2-6.fc16

Steps to Reproduce:
1. Open Document, select "File -> Print ...", select your Printer, click "Properties ...", select Tab "Device", Printer Language Type is set to "PDF"
2. Change Printer Language Type to "Postscript (Level from Driver)", Print. Document.
3. Close Document (without saving) and re-open Document, Check Printer Language.
  
Actual results:
Printer Language is set to PDF again.

Expected results:
Printer Language is set to Postscript.

Additional info:
The Printer Language only sticks to Postscript if you change the Language Type, then print and save the Document afterwards. But it's reverted to PDF if you either choose another Printer or open another Document.

Comment 1 Caolan McNamara 2012-09-11 19:55:19 UTC
This bug has lingered a bit because I'm lacking the details of the problem with the default pdf ? Does the printer print the raw pdf file or some horribly bad rendering of the document ?

Comment 2 Kai Hambrecht 2012-09-12 08:04:27 UTC
second one: bad rendering, as the printer is not capable of printing raw pdf.

Comment 3 Caolan McNamara 2012-09-12 09:01:10 UTC
can we get the what printer driver is being used, i.e. system-config-printer and paste in the "make and model" entry

Comment 4 Kai Hambrecht 2012-09-12 09:47:29 UTC
Printer is a HP LJ 4300

from system-config-printer:

Device URI: ipp://server-xx.xxxxx:631/printers/rose
Make and Model: HP LaserJet 4300 PS on server-xx.xxxxx

Comment 5 Caolan McNamara 2012-09-12 10:19:26 UTC
caolanm->twaugh: anything here ring any bells for you. My understanding is that using pdf as the default print job format is the current "right thing to do" for an app.

Comment 6 Tim Waugh 2012-09-17 10:41:12 UTC
The best thing is for applications to generate PDF when printing.  CUPS will convert PDF to PostScript in order to process it and send it to the printer.

In a future release, CUPS will process PDF as necessary and send it directly to printers that are capable of understanding it. Of course, for other printers it will still convert to whichever format they need.

If sending a print job to CUPS in PDF gives bad rendering, but sending it in PostScript is fine, the problem could be either (a) the application's generated PDF, or (b) the CUPS filter chain, in particular the filter converting PDF to PostScript.

For this model, the recommended printer driver is "HP LaserJet 4300 Series Postscript".

In this situation, it looks like the CUPS filter chain is running on "server-xx.xxxxx".  Is that running some version of Fedora?

Comment 7 Fedora End Of Life 2013-01-16 20:26:58 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. 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 '16'.

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 16'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 16 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, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

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: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 8 Fedora End Of Life 2013-02-13 23:50:29 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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.


Note You need to log in before you can comment on or make changes to this bug.