Bug 501714

Summary: Ghostscript pdf2ps fail to generate correct content from Xerox WorkCentre generated pdf file
Product: Red Hat Enterprise Linux 5 Reporter: Tuomo Soini <tis>
Component: ghostscriptAssignee: Tim Waugh <twaugh>
Status: CLOSED DUPLICATE QA Contact: QE Internationalization Bugs <qe-i18n-bugs>
Severity: medium Docs Contact:
Priority: low    
Version: 5.3CC: pknirsch
Target Milestone: rcKeywords: Patch
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: ghostscript-8.70-1.el5 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-07-16 15:13:23 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
Proposed patch for problem
none
Sample pdf generated by xerox workcentre none

Description Tuomo Soini 2009-05-20 13:22:04 UTC 
Created attachment 344799 [details]
Proposed patch for problem

Description of problem:

pdf2ps generates empty ps file from Xerox WorkCentre generated pdf file.

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

8.15.2-9.4.el5_3.7

How reproducible:

Always

Steps to Reproduce:
1. scan document with xerox
2. try to convert it to ps with pdf2ps
3. open file with evince, it's empty
  
ghostscript svn has fix for this issue:

http://svn.ghostscript.com/viewvc?view=rev&revision=8778
Comment 1 Tuomo Soini 2009-05-20 13:24:09 UTC 
Created attachment 344801 [details]
Sample pdf generated by xerox workcentre
Comment 2 RHEL Program Management 2009-11-06 18:42:12 UTC 
This request was evaluated by Red Hat Product Management for
inclusion, but this component is not scheduled to be updated in
the current Red Hat Enterprise Linux release. If you would like
this request to be reviewed for the next minor release, ask your
support representative to set the next rhel-x.y flag to "?".
Comment 4 Tim Waugh 2010-07-16 15:13:23 UTC 

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