Bug 710816 - Illegal entry in bfrange block in ToUnicode CMap
Summary: Illegal entry in bfrange block in ToUnicode CMap
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: poppler
Version: 6.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Marek Kašík
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks: 1271696
TreeView+ depends on / blocked
 
Reported: 2011-06-05 00:26 UTC by Zenon Panoussis
Modified: 2016-05-10 20:48 UTC (History)
4 users (show)

Fixed In Version: poppler-0.12.4-6.el6
Doc Type: Bug Fix
Doc Text:
Cause Poppler assumes that ToUnicode CMaps contains only 2-digit values <##> but there can be 4-digit values <####> too. Consequence "Illegal entry in bfrange block in ToUnicode CMap" appears when going trough pdf file. Fix Condition for checking 2-digit values has been extended to check also 4-digit values. Result The bug doesn’t present anymore.
Clone Of:
Environment:
Last Closed: 2016-05-10 20:48:30 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:0799 0 normal SHIPPED_LIVE evince and poppler bug fix update 2016-05-10 22:37:49 UTC

Description Zenon Panoussis 2011-06-05 00:26:46 UTC 
RHEL6 comes with poppler-0.12.4-3 and its users suffer all the symptoms of https://bugzilla.redhat.com/show_bug.cgi?id=574964 . The solution is the same too.
Comment 2 RHEL Program Management 2011-07-06 01:35:39 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. If you would like it considered as an
exception in the current release, please ask your support
representative.
Comment 9 errata-xmlrpc 2016-05-10 20:48:30 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.

https://rhn.redhat.com/errata/RHBA-2016-0799.html
Note You need to log in before you can comment on or make changes to this bug.