Bug#1021917: inkscape: Inkscape cannot import PDF files

[Andreas Tepe]

Package: inkscape
Version: 1.1.2-3+b1
Severity: normal
X-Debbugs-Cc: a...@muenster.de

Dear Maintainer,


* I tried to convert a PDF file to an SVG file on command line

* For this I used the command

/usr/bin/inkscape --pdf-page=1 --export-overwrite --export-type=svg file.pdf

* Inkscape crashed with the message

Emergency save activated!
Emergency save completed. Inkscape will close now.
If you can reproduce this crash, please file a bug at https://inkscape.org/report
with a detailed description of the steps leading to the crash, so we can fix it.
** Message: 12:46:01.750: Error: Inkscape encountered an internal error and will close now.

Segmentation fault

* A clean exit is what I expected.



-- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.19.0-2-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages inkscape depends on:
ii lib2geom1.1.0 1.2-1
ii libatkmm-1.6-1v5 2.28.3-1
ii libboost-filesystem1.74.0 1.74.0-17
ii libc6 2.35-3
ii libcairo2 1.16.0-6
ii libcairomm-1.0-1v5 1.14.4-1
ii libcdr-0.1-1 0.1.6-2+b1
ii libdbus-glib-1-2 0.112-2
ii libfontconfig1 2.13.1-4.5
ii libfreetype6 2.12.1+dfsg-3
ii libgc1 1:8.2.2-3
ii libgcc-s1 12.2.0-3
ii libgdk-pixbuf-2.0-0 2.42.9+dfsg-1
ii libglib2.0-0 2.74.0-3
ii libglibmm-2.4-1v5 2.66.5-1
ii libgomp1 12.2.0-3
ii libgsl27 2.7.1+dfsg-3+b1
ii libgspell-1-2 1.12.0-1
ii libgtk-3-0 3.24.34-3
ii libgtkmm-3.0-1v5 3.24.7-1
ii libharfbuzz0b 5.2.0-2
ii libjpeg62-turbo 1:2.1.2-1+b1
ii liblcms2-2 2.13.1-1+b1
ii libmagick++-6.q16-8 8:6.9.11.60+dfsg-1.3+b3
ii libpango-1.0-0 1.50.10+ds-1
ii libpangocairo-1.0-0 1.50.10+ds-1
ii libpangoft2-1.0-0 1.50.10+ds-1
ii libpangomm-1.4-1v5 2.46.3-1
ii libpng16-16 1.6.38-2
ii libpoppler-glib8 22.08.0-2.1
ii libpoppler118 22.02.0-3
ii libpotrace0 1.16-2
ii libreadline8 8.2-1
ii librevenge-0.0-0 0.0.4-6+b1
ii librsvg2-common 2.54.5+dfsg-1
ii libsigc++-2.0-0v5 2.10.8-1
ii libsoup2.4-1 2.74.3-1
ii libstdc++6 12.2.0-3
ii libvisio-0.1-1 0.1.7-1+b2
ii libwpg-0.3-3 0.3.3-1
ii libx11-6 2:1.8.1-2
ii libxml2 2.9.14+dfsg-1+b1
ii libxslt1.1 1.1.35-1
ii python3 3.10.6-1
ii zlib1g 1:1.2.11.dfsg-4.1

Versions of packages inkscape recommends:
ii aspell 0.60.8-4+b1
ii fig2dev 1:3.2.8b-3
ii imagemagick 8:6.9.11.60+dfsg-1.3+b3
ii imagemagick-6.q16 [imagemagick] 8:6.9.11.60+dfsg-1.3+b3
ii libimage-magick-perl 8:6.9.11.60+dfsg-1.3
ii libwmf-bin 0.2.12-5
ii python3-lxml 4.9.1-1+b1
ii python3-numpy 1:1.21.5-1+b1
ii python3-scour 0.38.2-2

Versions of packages inkscape suggests:
pn dia <none>
pn inkscape-tutorials <none>
pn libsvg-perl <none>
pn pstoedit <none>
pn python3-uniconvertor <none>
ii ruby 1:3.0+3.1

-- no debconf information

[Martin]

Quoting Andreas Tepe <a...@muenster.de>:
> * Inkscape crashed with the message

Does this happen only with specific PDFs?

Because this works for me with inkscape stable backport:

$ dpkg -l inkscape
...
ii inkscape 1.1.2-3~bpo11+1 amd64 vector-based drawing program
$ wget
https://buergernetz-muenster.de/wp-content/uploads/2019/06/Digitaler-Nachlass.pdf
...
$ inkscape --pdf-page=1 --export-overwrite --export-type=svg
Digitaler-Nachlass.pdf
$ file Digitaler-Nachlass.svg
Digitaler-Nachlass.svg: SVG Scalable Vector Graphics image

Cheers

[fab...@greffrath.com]

Hi all,

Am 17.10.2022 12:47, schrieb Andreas Tepe:
> ii libpoppler-glib8 22.08.0-2.1
> ii libpoppler118 22.02.0-3

could this version mismatch be the culprit?

- Fabian

[Andreas]

Hello Fabian,

that could be. The only package that is requiring libpoppler118 is
inkscape. libpoppler-glib8 and libpoppler123 are required by a bunch o
packages. So removing libpoppler-glib8 and libpoppler123 is apparently
not a good option. And I cannot remove libpoppler118 because inkscape
will be removed then as well.

Cheers,
Andreas

Am 17.10.22 um 13:32 schrieb fab...@greffrath.com:

[fab...@greffrath.com]

Hi,

Am 17.10.2022 13:37, schrieb Andreas:
> not a good option. And I cannot remove libpoppler118 because inkscape
> will be removed then as well.

the inkscape package is currently stuck at an old revision in testing,
because migration from unstable is blocked by bugs. However, the poppler
package has migrated in the meantime, so you end up with an outdated
inkscape requiring an old libpoppler and a new libpoppler providing its
own new glib-bindings - which seem to be incompatible with the ones
expected by the older libpoppler.

Could you upgrade your inkscape package to the one in unstable?

- Fabian

[Andreas]

Hello Fabian,

thanks for your advice!
Yes, that solved the issue. :)

Cheers,
Andreas

Am 17.10.22 um 14:57 schrieb fab...@greffrath.com: