Hi,

Inkscape has started crashing when I try to import pdf files , error message reads "Inkscape encountered an internal error and will close now."

I have recently updated to Ubuntu 16.04 LTS.

Anyone having similar problems? Any suggestions?

Cheers.

EDIT: Using Inkscape 0.91

That could happen if the file is larger than your computer can handle. Are these very large files? Can you test with a small file? Let's say under 5 mb.

Edit
Also, there are a number of options in the dialog when you try to open a PDF file. Have you tried changing any of those?

Hi,

They are not large files, same thing happens with both 'large' (>5mb) and 'small' (<2mb) .pdf files (I've tried a few now).

When I try to import it does not make it to the 'options' dialogue, it just immediately gives the "Inkscape encountered an internal error and will close now." window, which has only one button, which is 'close'.

Cheers!

I think this should be reported in the bug tracker, so the developers can try to find out what's happening here.
@chm4tw: please head over to https://bugs.launchpad.net/inkscape and report a bug (if you can, please also provide a backtrace, see https://inkscape.org/en/contribute/report-bugs/ )

It may well be the bug is already known, but this can only be decided when all the data is available to the developers.

Moini wrote:I think this should be reported in the bug tracker, so the developers can try to find out what's happening here.
@chm4tw: please head over to https://bugs.launchpad.net/inkscape and report a bug (if you can, please also provide a backtrace, see https://inkscape.org/en/contribute/report-bugs/ )

It may well be the bug is already known, but this can only be decided when all the data is available to the developers.

OK, will do that now, thanks for your help!

After you make the report, would you please post the link to the report here? I'll be interested to follow the issue.

Bug report here:

https://bugs.launchpad.net/inkscape/+bug/1584659

PS I hope the GDP output is ok, first time I've used it - can try again if necessary.

Cheers

Thanks

Thanks from me, too Seems it was already known indeed - but without the debug output, the devs could not have known that. Well done! (unfortunately, it seems to be related to a specific poppler library version. Does it work if you uncheck 'import via poppler'?)

If pdf import is really important for you, you could maybe try if updating your poppler version will work (and does not break other things):
see http://askubuntu.com/questions/722950/h ... st-version

(latest version is 0.44.0, version in Ubuntu 16.04 seems to be 0.41.0, so they might have fixed this)

Moini wrote:you could maybe try if updating your poppler version will work …

I'd caution against attempting to install a different version of poppler than provided by the system's package manager (unless you are a developer, know about the caveats and compile apps from source with custom versions of the dependencies anyway all the time). Poppler tends to change the library's so version very often (with almost every release) - dependents of poppler like Inkscape need to be recompiled against newer/different poppler every time that happens (usually, the package manager takes care of that and provides updates as needed).

You risk potentially breaking applications installed via package manager if you install a custom newer poppler version into the default prefix (e.g. via a custom PPA, or from source); OTOH you would have to recompile from source whatever applications you want to use (build & link) with a newer poppler installed into custom prefix (after having figured out how to make sure the custom build doesn't pick up the default poppler anyway).

Also: based on the tests done for the earlier bug report (with same backtrace), the issue does not seem to be specific to a certain poppler version either (since import worked with older, same and newer poppler versions on other systems). The reason for the reported crashes on affected systems is unknown so far.

@suv: Wouldn't it make sense to update the info in the bug report accordingly? Adventurous non-experts might use google and stumble upon the same info as I did.

The 'try' already suggested that it may not work. One can always uninstall and reinstall the repo version.

Moini wrote:Wouldn't it make sense to update the info in the bug report accordingly? Adventurous non-experts might use google and stumble upon the same info as I did.

<opinion>Why? A bug tracker as such is not a user support forum. What is relevant in the bug tracker is gathering as much (technical) information as possible about the affected system, and the steps triggering the reported issue, to allow members of the bug team and/or developers to reproduce a reported issue, or at least to narrow down whether a reported issue is actually in Inkscape's code base (can/needs to be fixed within Inkscape), or elsewhere … </opinion>

It seems there is more info available than can be found in the report. If it is known that it's not the specific poppler version after all, then wouldn't it make sense to add that info there? The version the user has is a different one from those reported to have been tested.

(As a user, I *do* look for workarounds in the bug tracker, and I'm sure I'm not the only one.)

Just early last month, Inkscape internal error showed up on my system while uploading a color palette. I've been uploading palettes for months with no problem, then this error shows up. I've tried rebooting my system (Windows 10), uninstalling and reinstalling, but nothing works. Does anyone have an ideal about this 'internal error now closing' Inkscape issue? Is this a bug that Inkscape has? Appreciate any insights

I've just SOLVED my issue... I made sure that leftover files like palettes and fonts from Inkscape were removed in Program 86x files, then, I downloaded Inkscape again from the site. This time, when the box shows up asking how to install in TYPICAL or COMPLETE, I went for COMPLETE this time around and Inkscape opened with ease.