Summary: | Poppler crash on PDF file | ||
---|---|---|---|
Product: | poppler | Reporter: | Wouter Bolsterlee <uws+freedesktop> |
Component: | general | Assignee: | poppler-bugs <poppler-bugs> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | critical | ||
Priority: | high | CC: | bugzilla, mdke, philsf79 |
Version: | unspecified | ||
Hardware: | x86 (IA32) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: |
PDF file that triggers the bug
pdf file with uming fonts embedded. |
Description
Wouter Bolsterlee
2006-04-25 01:28:24 UTC
Created attachment 5458 [details]
PDF file that triggers the bug
Some information about the pdf file: it uses embedded fonts created from the Truetype freefont Serif set. It was created by apache fop[1] [1] http://xmlgraphics.apache.org/fop/0.20.5/fonts.html I'm afraid that I don't run poppler/evince from cvs or compile it, so I'm not able to check whether that patch fixes it. Perhaps someone else is able to confirm? I'm really keen that this is fixed in Ubuntu before the next version is released, because otherwise lots of PDFs will not be working properly. In the mean time, I'll attach another pdf file with different fonts embedded that has the same problem. Created attachment 5599 [details]
pdf file with uming fonts embedded.
rettagging, the missing font happens on splash also, maybe freetype can not handle that font? need to investigate further, but need more time to do things, arrrrgggg It doesn't crash with cairo anymore but still doesn't render the text. I think this has been fixed (or at least improved) using version 0.8.6. All I get is the following error: $ evince attachment.cgi Error: Found a bad table definition on true type definition, trying to continue... Maybe the bug can be closed or redefined. Thanks, Pablo Right, using a new poppler and the yet to be released Freetype this will work, that is, not crash and get the fonts rendered. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.