Poppler, poppler-glib breaking Inkscape

Just a head up. The latest updates of poppler and poppler-glib seem to break Inkscape. A downgrade solves the problem. Inkscape is starting again.

yay -Qs poppler
local/poppler 24.09.0-3
    PDF rendering library based on xpdf 3.0
local/poppler-glib 24.09.0-3
    Poppler glib bindings

Updated versions would be : 24.09.0-4

I suspect this is fixed already (if you update again). There’s an update to poppler and I can confirm Inkscape is starting.

poppler 24.09.0-4
poppler-glib 24.09.0-4
1 Like

Inkscape isn’t starting with this version on my installation. I needed to go back one version.

Oh I see, so version 24.09.0-4 is causing you the issue, not 24.09.0-3?

Might it be related to any PDF related intervention on poppler-qt6?

My output of:
yay -Q | grep poppler

poppler 24.09.0-4
poppler-data 0.4.12-2
poppler-glib 24.09.0-4
poppler-qt6 24.09.0-4

poppler-qt6 doesn’t interfere at all. I only downgraded mentioned 2 packages. The qt6 package is still version 24.09.0-4 on my system. I just recognized it even exists, after downgrading poppler and poppler-glib.

Are you using inkscape or are you using inkscape-git?

Strange then, that the latest versions work here. Inkscape is version 1.4.1?

inkscape 1.4-1

I only had a look at the requirements of Inkscape. Only the 2 packages are required. poppler-qt6 isn’t.

extra/inkscape 1.4-1 (24.1 MiB 173.4 MiB) (Installiert)
Professional vector graphics editor

As far as I can tell, this version is still beta, although it is in the extra repository. I assume they offer this one because 1.3.2 requires older libraries and doesn’t work with the new ones.

The fix is already out, no need to downgrade anything. Inkscape works normally for me.

1 Like

I just tried before I wrote about the topic. I’ll give it another try and then report back. Maybe it was just an unlucky coincidence.

Perhaps a full update, restart, then try?

I always run full updates. :wink:

1 Like

Very strange. It works indeed, although I’m now using the same versions prior to the update. Maybe there was another update/exchange of one of or both packages.

Maybe a problem with the mirror.

System needed to be restarted after last update perhaps?

1 Like

No. No restart took place.

As a habit, I run a system update, and after it completes, restart the system.

Then I might run AUR updates, and use the system (unless one of these may benefit from another reboot after updating).

1 Like