Bug 477644

Summary: evince fails to properly print PDF
Product: [Fedora] Fedora Reporter: Matt Castelein <matt.castelein>
Component: evinceAssignee: Kristian Høgsberg <krh>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 10CC: jon.dufresne, krh
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-02-13 16:24:14 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Example PDF file none

Description Matt Castelein 2008-12-22 16:51:42 UTC
Created attachment 327671 [details]
Example PDF file

Description of problem: printed the attached PDF to a Konica Minolta 1050 Pro, and it quit at page 19, with one additional blank page followed by:

%%[ ERROR:ioerror; OFFENDING COMMAND: image]%%

STACK:

-dictionary-

In addition to this, there are several images missing from the pages that were printed.  I send the same job to a Xerox DocuPrint 75, and it also shows the same symptoms, quits at page 19 with missing images, although does not print out the PS error.  Printing it from Window$ with Acrobat reader produces correct output

Version-Release number of selected component (if applicable):
evince-2.24.2-1.fc10.i386

How reproducible:
always

Steps to Reproduce:
1.Open PDF
2.Print
3.
  
Actual results:
Printing fails

Expected results:
Correct output

Additional info:
I work for a printing company that deals with PS and PDF all day every day, I would be more than happy to provide hardcopy for comparison.

Comment 1 Jon Dufresne 2009-02-13 16:24:14 UTC
Thank you for the bug report. This particular bug has already been reported
into our bug tracking system, but please feel free to report any further
bugs you find.

*** This bug has been marked as a duplicate of bug 444364 ***