Bugzilla Bug 199827

Xpdf 3.02 (poppler version) crashes on some files. Maybe, some
fontconfig-related problem (see stack backtrace).

Reproducible: Always

Steps to Reproduce:
1. Try to open, for example,
http://oss.org.cn/up_soft/rsn/NVIDIA_Linux_Advantage.pdf

Created an attachment (id=136543) [edit]
Stack backtrace

Created an attachment (id=136545) [edit]
emerge --info

Currently installed fontconfig-2.4.2, poppler-0.6.1-r1

Please, attach a more useful backtrace...

http://www.gentoo.org/proj/en/qa/backtraces.xml

Created an attachment (id=136556) [edit]
Stack backtrace

I have xpdf, poppler and fontconfig rebuilded with debugging info. More
informative stack trace attached.

Much better indeed... :)

hmh, thomas, do you have an idea why this is? How have you made that poppler
version exactly? Is there any chance we could get this upstream to either
poppler or xpdf? ;)

(In reply to comment #7)
> hmh, thomas, do you have an idea why this is? How have you made that poppler
> version exactly? Is there any chance we could get this upstream to either
> poppler or xpdf? ;)
> 

Hard to tell, either this is a mere poppler problem, because if you do a: 

$ pdf2ps yourpdffile.pdf
$ ps2pdf yourpdffile.ps

the resulting pdf will work. (both are poppler command line tools.)

Or it is indeed the conflict of the redundant code in xpdf, the GlobalParams.*
are right now included in the xpdf-3.02-poppler package, even though they are
also provided by poppler (some functions are missing there though)
In poppler uses fcfg slightly differently in their constructor, compared to
xpdf.

I will try to compile xpdf with the patched poppler and see if the problem
remains.

Ok, with the patched poppler version it works correct.
So it seems xpdf doesn't initialize some Fontconfig stuff, that poppler later
wants to access, so basically we need to patch poppler, I will try to get the
patch upstream, again.

regards,
Thomas

Created an attachment (id=136636) [edit]
xpdf-3.92-poppler source package

Poppler doesn't really want to include xpdf specific stuff it seems, they
provide the xpdf headers only per flag, anyhow, this package should fix the
breakage for now

Created an attachment (id=136638) [edit]
source package (updated)

sorry, I forgot to clean the package, before uploading it :p

I wonder, how have you fixed it now? Anyway, thanks for fixing.

Well, instead of patching poppler with the xpdf code, I patched xpdf with the
poppler code :p

This solution is also sub-optimal though, but it should do the trick now.
I hope no other bug will emerge, and I will keep trying to get the xpdf patch
for poppler upstream, but xpdf never was supposed to be spereated in library
style, so it is kind of a compromise for the poppler guys whether to include
xpdf code or not.

regards,
Thomas