Description of problem: /usr/bin/pdftops generates invalid postscript file. Below error is logged while opening file with ghostscript : GPL Ghostscript 9.15 (2014-09-22) Copyright (C) 2014 Artifex Software, Inc. All rights reserved. This software comes with NO WARRANTY: see the file PUBLIC for details. Error: /syntaxerror in (bin obj seq, type=128, elements=1, size=61698, non-zero unused field) Operand stack: Execution stack: %interp_exit .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- false 1 %stopped_push 1951 1 3 %oparray_pop 1950 1 3 %oparray_pop 1934 1 3 %oparray_pop 1820 1 3 %oparray_pop --nostringval-- %errorexec_pop .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- Dictionary stack: --dict:1178/1684(ro)(G)-- --dict:0/20(G)-- --dict:84/200(L)-- --dict:66/75(L)-- Current allocation mode is local Current file position is 11024 GPL Ghostscript 9.15: Unrecoverable error, exit code 1 Version-Release number of selected component (if applicable): poppler-utils-0.12.4-3.el6_0.1.x86_64 How reproducible: Always. Steps to Reproduce: 1. Download attached pdf file 2. Execute '/usr/bin/pdftops 20-200002-001.PDF' 3. Open file using ghostscript 'gs 20-200002-001.ps' Actual results: ghostscript exits due to unrecoverable error Expected results: ghostscript should show .ps file Additional info: This error is not reproducible if ghostscript is used as backend (instead of poppler) to generate .ps file.
The problem here is that the Type1 font embedded in the PDF is in PFB format and includes PFB headers which are not removed before embedding the font again to the resulting PostScript file. I've prepared a patch which fixes the problem for me and attached it here: https://bugs.freedesktop.org/show_bug.cgi?id=19747 I would like to have upstream's opinion on the patch so I'll wait with devel_ack.
The patch was accepted by upstream so I'm giving this bug devel_ack+.
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