Bug 901520 - xpdf fails to print without error indication
Summary: xpdf fails to print without error indication
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: xpdf
Version: 17
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Tom "spot" Callaway
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-18 11:38 UTC by Wolfgang Denk
Modified: 2013-02-08 08:21 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-02-07 18:14:10 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Testfile showing the problem. (46.22 KB, application/pdf)
2013-01-18 11:38 UTC, Wolfgang Denk
no flags Details

Description Wolfgang Denk 2013-01-18 11:38:13 UTC
Created attachment 682363 [details]
Testfile showing the problem.

Description of problem:

Some PDF documents (generated by LibreOffice from a ODT file with an
included BMP image) fail to print: ther eis no error indication nor
any other hint that ther emight be a problem, but no print job is ever
generated.

The problem appears o depend on the included image - replacing this
with another one makes the problem go away.

Version-Release number of selected component (if applicable):

xpdf-3.03-5.fc17.x86_64

How reproducible:

always

Steps to Reproduce:
1. Open test file in xpdf
2. Print to your favorite printer
  
Actual results:

No error indications, everything looks OK - but no data gets printed.

Expected results:

A print job with the expected output should be generated.

Additional info:

acroread or evince will print this file just fine.

Comment 1 Tom "spot" Callaway 2013-02-07 18:14:10 UTC
I can't reproduce this failure with your testfile on xpdf-3.03-5.fc18.x86_64.

xpdf's printing mechanism is idiotically simple, it pipes postscript results into lpr. My best guess is that there is a failure somewhere beyond xpdf where the postscript isn't getting handled.

I don't know how acroread works (due to a lack of source), but evince is using the gnome printing dialog, which is notably more complex than lpr, so perhaps thats why it works better.

I hate to close this CANTFIX, but I don't know what else to do.

Comment 2 Wolfgang Denk 2013-02-08 08:21:38 UTC
(In reply to comment #1)
> I can't reproduce this failure with your testfile on xpdf-3.03-5.fc18.x86_64.

for me the problem is still present with xpdf-3.03-5.fc18.x86_64, using the very same testfile attached above.

> xpdf's printing mechanism is idiotically simple, it pipes postscript results
> into lpr. My best guess is that there is a failure somewhere beyond xpdf
> where the postscript isn't getting handled.
> 
> I don't know how acroread works (due to a lack of source), but evince is
> using the gnome printing dialog, which is notably more complex than lpr, so
> perhaps thats why it works better.
> 
> I hate to close this CANTFIX, but I don't know what else to do.

OK, so I open a new bug against cups (Bug 909090).


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