Launchpad has imported 3 comments from the remote bug at https://bugs.freedesktop.org/show_bug.cgi?id=75232.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2014-02-19T23:09:00+00:00 Roland Dreier wrote: I've found that the version of poppler in current Ubuntu 14.04 (I have poppler-utils 0.24.5-2ubuntu1) has perhaps become too strict and won't parse PDF files that work fine in other readers. For example with the SPC-4 SCSI spec available from http://www.t10.org/cgi- bin/ac.pl?t=f&f=spc4r36q.pdf , I get: $ pdfinfo spc4r36q.pdf Syntax Error: Couldn't find trailer dictionary Syntax Error: Couldn't read xref table However, the built-in firefox PDF renderer works with that file, as does mupdf. Both seem to be able to render the whole document and don't produce any warnings etc. Reply at: https://bugs.launchpad.net/poppler/+bug/1282151/comments/3 ------------------------------------------------------------------------ On 2014-02-19T23:52:47+00:00 Albert Astals Cid wrote: The file is very broken, Adobe Acrobat for Linux won't open it either. We can relax one of the checks and open it, but I am not sure if it will break other files. Basically the problem is that the linearization dict length and the file length do not match, if i comment that check in PDFDoc::isLinearized all works, but i am scared it may break some other files. OTOH the pdf spect says it may happen that linearization dict length and the file length do not match and speaks about how to recover, but... Hib, what's your opinion shall we relax that check in PDFDoc::isLinearized and run a regtest ? Or maybe turn it into at least an isOk that checks all the mandated fields of the dict are there? Reply at: https://bugs.launchpad.net/poppler/+bug/1282151/comments/4 ------------------------------------------------------------------------ On 2014-02-20T00:04:09+00:00 Albert Astals Cid wrote: Created attachment 94392 Patch for the issue Actually this seems it should be pretty safe since we're only relaxing the condition if all failed. Hib, comments? Reply at: https://bugs.launchpad.net/poppler/+bug/1282151/comments/5 ** Changed in: poppler Status: Unknown => Confirmed ** Changed in: poppler Importance: Unknown => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1282151 Title: evince won't open PDF files other readers can handle Status in Poppler: Confirmed Status in “poppler” package in Ubuntu: New Bug description: I've found that the version of evince in 14.04 has perhaps become too strict and won't open PDF files that work in other readers. For example with the SPC-4 SCSI spec available from http://www.t10.org /cgi-bin/ac.pl?t=f&f=spc4r36q.pdf , I get: $ evince spc4r36q.pdf Syntax Error: Couldn't find trailer dictionary Syntax Error: Couldn't read xref table Syntax Error: Couldn't find trailer dictionary Syntax Error: Couldn't read xref table and the evince window has a red bar saying "PDF document is damaged" However, the built-in firefox PDF renderer works fine with that file, as does mupdf. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: evince 3.10.3-0ubuntu7 ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Wed Feb 19 08:12:32 2014 InstallationDate: Installed on 2014-01-11 (39 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140109) KernLog: SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/poppler/+bug/1282151/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
