inkview crashes when going to next slide

[RIco]

on clicking on the slide buttons or left/down arrow on the keyboard to go to the next slide, inkview crashes
>Segmentation fault

ex:
1. type in terminal
~$ inkview Documents/SVG/*.svg (assuming SVG is the directory where i have my svg files)
Segmentation fault

Ubuntu 8.10, inkscape svn 20508

[Alvin Penner (apenner)]

running Windows XP and Inkview from March 2008, I cannot confirm the crash.
- could you confirm that every one of the .svg files can be individually loaded without causing a crash?
-could you try this with a different 'first' and 'second' file?

[RIco (rico-rootscore-deactivatedaccount)]

- every one of the .svg files can be loaded individually
- i tried it with different first and second file

still getting a segmentation fault

Ubuntu 9.04, Inkscape svn r21304

[Joel (jdy)]

Confirmed behaviour with Fedora 11 running 20090710 svn release.

inkview /usr/share/inkscape/clipart/*.svg*

Will not advance to the next svg. Exits instead.

[jazzynico (jazzynico)]

Confirmed on Ubuntu 9.04, rev. 22023.

[uwesch (uwesch)]

also confirmed with final 0.47-2 and Windows 7

[su_v (suv-lp)]

confirmed with Inkscape 0.46+devel r22575 on OS X 10.5.8

[Peter Hanappe (hanappe)]

It seems the bug is due to a memory corruption: the current document is deleted twice,
once in View::setDocument (view.cpp:148) and once in sp_svgview_set_document (inkview.cpp:450).

[John Culleton (john-wexfordpress)]

Confirmed with 47 final and Linux Slackware 13 under both XFCE and KDE.

John Culleton

[h1repp (heinz-repp)]

Confirmed on Win XP SP3 with stable Inkscape 0.47-3
Event-ID is 26 (application popup), I found only two different descriptions (exact addresses matching) distributed roughly equally:

first is:
Application popup: example.svg: inkview.exe - Application Error : The instruction at "0x00401c35" referenced memory at "0x00000004". The memory could not be "read".

second is:
Application popup: example.svg: inkview.exe - Application Error : The instruction at "0x00000000" referenced memory at "0x00000000". The memory could not be "written".

[Pablo Rodríguez (ousia)]

Would it be possible to have a patch to be able to fix inkscape 0.47?

Thanks for your help,

Pablo

[su_v (suv-lp)]

@Pablo - if you build 0.47 yourself, the patch can be downloaded as diff from
<http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/revision/9157>

Otherwise - the sources of Inkscape 0.48 (which includes the fix) have been released last week [1], and the announcement of new packages (win32/osx) is imminent.

[1] <http://sourceforge.net/projects/inkscape/files/inkscape/>

[Pablo Rodríguez (ousia)]

Thanks for the tip.

Pablo

[Pablo (pablo-redhat-bugs)]

As described at bug https://bugs.launchpad.net/inkscape/+bug/316506, inkview-0.47 crashes when going to next slide.

A patch is provided there (http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/revision/9157).

Would you be so kind to fix this in the Fedora 13 distribution?

Thanks for your help,

Pablo

[Pablo (pablo-redhat-bugs)]

I'm using F14 now, which ships inkscape-0.48.

This bug was specific to inkscape-0.47. I wonder whether this will be fixed in F13.

How about closing it was NEXTRELEASE or WONTFIX?

Thanks for your help,

Pablo

[Pablo (pablo-redhat-bugs)]

Closing myself, since Fedora 14 has no problems with that.