Bug 637124

Summary: Evince cannot open PDF file because of unsupported security in poppler
Product: Red Hat Enterprise Linux 5 Reporter: Olivier Fourdan <ofourdan>
Component: popplerAssignee: Marek Kašík <mkasik>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.5CC: ajb2, bmr, cww, herrold, jvillalo, kem, plyons, rdassen, spurrier, tao, theo_nra, vbenes
Target Milestone: rcKeywords: Patch
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: poppler-0.5.4-18.el5 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-02-21 06:11:40 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:
Bug Depends On:    
Bug Blocks: 668957, 716820, 719046    
Attachments:
Description Flags
Proposed patch to backport the support of recent PDF none

Description Olivier Fourdan 2010-09-24 11:46:45 UTC
Created attachment 449398 [details]
Proposed patch to backport the support of recent PDF

Description of problem:

Some PDF files cannot be opened with Evince because poppler 0.5.4 fails to recognize the security used (even if no password is required).

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

poppler-0.5.4

How reproducible:

Always

Steps to Reproduce:
1. Open the PDF attached with Evince on Red Hat Enterprise Linux 5
  
Actual results:

Error: Unsupported version/revision (4/4) of Standard security handler
Error: Incorrect password

Expected results:

Evince is able to open the PDF (without password being prompted).

Additional info:

This is fixed upstream as part of git commit bf7e0e98 but that's a huge commit which is the merge of xpdf302 branch in HEAD.

A less intrusive patch to backport just that functionality in poppler-0.5.4 is attached.

Comment 3 J.H.M. Dassen (Ray) 2011-03-17 10:00:04 UTC
*** Bug 566734 has been marked as a duplicate of this bug. ***

Comment 7 RHEL Program Management 2011-05-31 15:00:49 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated in the
current release, Red Hat is unfortunately unable to address this
request at this time. Red Hat invites you to ask your support
representative to propose this request, if appropriate and relevant,
in the next release of Red Hat Enterprise Linux.

Comment 9 RHEL Program Management 2011-09-23 00:41:19 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated in the
current release, Red Hat is unfortunately unable to address this
request at this time. Red Hat invites you to ask your support
representative to propose this request, if appropriate and relevant,
in the next release of Red Hat Enterprise Linux.

Comment 14 RHEL Program Management 2011-10-19 19:07:30 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated in the
current release, Red Hat is unfortunately unable to address this
request at this time. Red Hat invites you to ask your support
representative to propose this request, if appropriate and relevant,
in the next release of Red Hat Enterprise Linux.

Comment 15 RHEL Program Management 2011-10-21 07:50:41 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release.  Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products.  This request is not yet committed for inclusion in an Update
release.

Comment 18 errata-xmlrpc 2012-02-21 06:11:40 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2012-0236.html