FS#17524 - [Inkscape] PDF import is broken

Attached to Project: Arch Linux
Opened by Martin Schmidt (Blind) - Tuesday, 15 December 2009, 22:16 GMT
Last edited by Jan de Groot (JGC) - Sunday, 24 January 2010, 20:23 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Tobias Kieslich (tobias)
Jan de Groot (JGC)
Architecture i686
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description:
Trying to import a PDF graphic containing an image will result in a crash of the application.

Additional info:
* package version(s)
$ pacman -Qi inkscape
Name : inkscape
Version : 0.46-14

* config and/or log files etc.
Error message when started in console:
inkscape: symbol lookup error: inkscape: undefined symbol: _ZN13GfxColorSpace5parseEP6Object

Steps to reproduce:
1. have a PDF file with a (in this case) grayscale image
2. File -> Import -> [chose PDF]
3. Bang!

Very annoying bug, as the PDF import is one of the killer features of inkscape.
This task depends upon

Closed by  Jan de Groot (JGC)
Sunday, 24 January 2010, 20:23 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed in testing.
Comment by Martin Schmidt (Blind) - Tuesday, 15 December 2009, 22:23 GMT
I think this is related to poppler.
Maybe inkscape just needs to be recompiled against a new poppler?

> nm /usr/lib/libpoppler.so | grep GfxColorSpace5
000b8860 T _ZN13GfxColorSpace5parseEP6ObjectP3Gfx
Comment by Denis A. Altoe Falqueto (denisfalqueto) - Wednesday, 16 December 2009, 01:56 GMT
I would suggest one of two things:

* wait until 0.47 hits the repos;
* use inkscape-nognome from AUR. I'm using it and just imported a simple PDF to test and it worked fine.
Comment by Martin Schmidt (Blind) - Wednesday, 16 December 2009, 19:51 GMT
Honestly, I would suggest to fix this bug.

But thanks for your suggestions :)
Comment by Jan de Groot (JGC) - Monday, 21 December 2009, 08:33 GMT
Fixing this bug is not so easy as it looks. The 0.47 version doesn't compile either with poppler 0.12.2, and the suggested patch at launchpad is a dirty hack that will likely break whenever that piece of code is called.
Comment by Martin Schmidt (Blind) - Monday, 21 December 2009, 16:51 GMT
Thanks for looking into it.
Do you have a suggestion as to how to proceed from here (except wait for a fix)?
Comment by Jan de Groot (JGC) - Monday, 21 December 2009, 17:36 GMT
You have 4 options:
- revert to poppler 0.12.1
- revert the commit in poppler 0.12.2 that caused this break
- compile with the wrong patch anyways
- compile without poppler support, meaning no PDF import
Comment by Martin Schmidt (Blind) - Monday, 21 December 2009, 18:08 GMT
I think that the first option is sanest and easiest.
Thank you for the help.
Comment by Tobias Kieslich (tobias) - Monday, 21 December 2009, 21:30 GMT
There are many package depending on poppler, epdfview, gimp, evince you name them. So Option one is not an option, IMHO.
Comment by Martin Schmidt (Blind) - Monday, 21 December 2009, 23:32 GMT
Hehe, ok.
It seems the minor upgrade doesn't seem to be a problem (tested gimp), but I can see your point, Tobias.
Comment by Julien (ganymede) - Sunday, 27 December 2009, 22:58 GMT
I confirm that inkscape-nognome-0.47 from AUR compiles and runs fine, and that it can import PDF file.
Comment by Jan de Groot (JGC) - Sunday, 03 January 2010, 22:03 GMT
Fixed in svn, still need to build and upload though.

Loading...