Crash on pdf import, openSUSE 11.2

Could you add more information about Inkscape and Poppler versions installed on openSUSE 11.2?

related to bug #487038 “0.47 build error with poppler 0.12.2 on Linux”
<https://bugs.launchpad.net/inkscape/+bug/487038>

Linux 2.6.31.12-0.2-default x86_64
4.3.5 (KDE 4.3.5)

inkscape-extensions-extra-0.47-6.1.x86_64
inkscape-extensions-fig-0.47-6.1.x86_64
inkscape-extensions-gimp-0.47-6.1.x86_64
inkscape-lang-0.47-6.1.noarch
inkscape-0.47-6.1.x86_64
inkscape-extensions-dia-0.47-6.1.x86_64

libpoppler-glib4-0.12.3-1.1.1.x86_64
poppler-data-0.2.1-2.1.1.noarch
libpoppler4-0.10.1-1.7.1.x86_64
libpoppler-glib3-0.8.2-1.3.x86_64
libpoppler5-0.12.3-1.1.1.x86_64
libpoppler-qt2-0.12.3-1.1.1.x86_64
libpoppler-qt4-3-0.12.3-1.1.1.x86_64
libpoppler3-0.8.2-1.3.x86_64
poppler-tools-0.12.3-1.1.1.x86_64

Your version of Inkscape was compiled with Poppler <= 0.12.1 but your system currently has Poppler >= 0.12.2. These releases are not ABI-compatible. This is actually a monumental screw-up on Poppler's (or packagers') side - they released an ABI-incompatible version without bumping the soname.

I don't see any way of fixing this on Inkscape's side, short of adding some popup at runtime that tells you that PDF import can crash.

@Krzysztof - I don't understand why bug #258504 would be the same - that crash was reported for certain PDFs only (appears to be related to code handling ICC cache) and has been reproduced with (a patched) inkscape compiled against poppler 0.12.3 (see comment #17-18).

I am 100% sure this bug is due to an ABI mismatch - this message tells it:
inkscape: symbol lookup error: inkscape: undefined symbol: _ZN13GfxColorSpace5parseEP6Object

ScislaC was running r9100, and I only fixed the build failure with poppler >= 0.12.2 in r9217. He must have compiled his version before the Lucid upgrade. I did not reproduce those crashes on any of the attached PDFs after a clean recompile on the same system (Ubuntu Lucid).

I don't know why sometimes it will fail with a symbol lookup error, and sometimes junk from the stack will be passed in the second parameter to ColorSpace::parse, but the underlying cause (ABI mismatch) is the same in both cases. I suspect it depends on whether Inkscape is built with debugging information or not. Backtraces in bug 258504 appear to confirm it.

Not sure if it helps, or just confuses the issue further, but when running Inkscape 0.46 on same (openSUSE 11.2) PCs, some PDF imports failed, others didn't. Now, with version 0.47, ALL crash.

On Sat, 2010-03-27 at 01:05 +0000, Krzysztof Kosinski wrote:
> *** This bug is a duplicate of bug 258504 ***
> https://bugs.launchpad.net/bugs/258504
> ScislaC was running r9100, and I only fixed the build failure with
> poppler >= 0.12.2 in r9217. He must have compiled his version before the
> Lucid upgrade. I did not reproduce those crashes on any of the attached
> PDFs after a clean recompile on the same system (Ubuntu Lucid).

For what I can contribute... I land on a +1 release in about 3 weeks
(whenever repos are opened) before I switch. The base libs are never
settled and everyone thinks I'm crazy... stabilized = boring for me. :D
If the base libs are stabilized, the only thing I have to look forward
to are third party packages and I build most of my art apps from source.

Stargate Universe is ramping up again soon... I am stoked. :D (bleeding
edge rocks regardless of awesome history)

Cheers,
Josh

Cf. https://bugs.archlinux.org/task/17524 , http://lists.altlinux.org/pipermail/sisyphus/2010-January/345142.html , https://bugzilla.novell.com/show_bug.cgi?id=638525 .