inkscape segfaults on opening this file

cannot reproduce this crash on Windows XP, Inkscape build 0.47pre2

I do get a large number of warnings, however:

** (inkscape.exe:4024): WARNING **: URI failed to parse: ##bfefff

these messages appear to come from the following source in the file:

style="fill:url(##bfefff);stroke:black;;"

I'm guessing that the line should read url(#bfefff), not url(##bfefff)

I'd take an error dialog or message about a bad SVG file, but not a segfault.
(Note, tidy did not complain, but that doesn't have the DTD.)

On Fri, Sep 4, 2009 at 5:18 PM, Alvin Penner<email address hidden> wrote:
> I do get a large number of warnings, however:
>
> ** (inkscape.exe:4024): WARNING **: URI failed to parse: ##bfefff
>
> these messages appear to come from the following source in the file:
>
> style="fill:url(##bfefff);stroke:black;;"
>
> I'm guessing that the line should read url(#bfefff), not url(##bfefff)
>
> --
> inkscape segfaults on opening this file
> https://bugs.launchpad.net/bugs/424564
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Inkscape: A Vector Drawing Tool: New
>
> Bug description:
> I  am  running  Debian  testing  on  AMD-64  hardware.  I have inscape 0.46-9
> installed.  The same thing happend  with  Ubuntu  Jaunty  i386  and  inkscape
> 0.46-5ubuntu4 installed.
>
> When you start inkscape with
>    inkscape pretty-out.svg
> it segfaults with the following output:
>
>    terminate called after throwing an instance of 'Inkscape::MalformedURIException'
>      what():  Malformed URI
>
>    Emergency save activated!
>    Emergency save completed. Inkscape will close now.
>    If you can reproduce this crash, please file a bug at www.inkscape.org
>    with a detailed description of the steps leading to the crash, so we can fix it.
>    Segmentation fault
>
> If you just start inkscape with no argument, go to the File/Open menu and try
> to open the file pretty-out.svg it dies with the output:
>
>    glibmm-ERROR **:
>    unhandled exception (type std::exception) in signal handler:
>    what: Malformed URI
>
>    aborting...
>
>    Emergency save activated!
>    Emergency save completed. Inkscape will close now.
>    If you can reproduce this crash, please file a bug at www.inkscape.org
>    with a detailed description of the steps leading to the crash, so we can fix it.
>    Segmentation fault
>
> eog, for example, has no problem displaying this SVG file.
>

1) reproduced with Inkscape 0.46-2 on OS X 10.5.8

 glibmm-ERROR **:
 unhandled exception (type std::exception) in signal handler:
 what: Malformed URI

2) not reproduced with Inkscape 0.46+devel r22179 on OS X 10.5.8

152 times this console message:
** (inkscape-bin:3164): WARNING **: URI failed to parse: ##bfefff

3) bug in Graphviz?

pretty-out.svg, line 4:
<!-- Generated by Graphviz version 2.20.2 (Mon Mar 30 10:11:53 UTC 2009)

fixed in Inkscape SVN - proposing to close this bug as 'Fix released' though I have no idea which revision...

@Henry, would you be willing to try a more recent build, it looks like this has been fixed recently?

If you tell me how to get the executable or source I can give it a shot, but
I don't know enough about inkscape internals to do more than to just try it
on the svc file I included with the bug report.

That svc file was produced by a genealogical program on a family tree and
then post-processed with a filter to adjust the appearance, so I could try a
few other sub-trees of the database.

Any way, if that is useful, can you point me at how to get the latest binary
or svn repository of the source?

Thanks

On Sat, Sep 5, 2009 at 5:00 PM, Alvin Penner<email address hidden> wrote:
> @Henry, would you be willing to try a more recent build, it looks like
> this has been fixed recently?
>
>
> ** Changed in: inkscape
>       Status: New => Incomplete
>
> --
> inkscape segfaults on opening this file
> https://bugs.launchpad.net/bugs/424564
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Inkscape: A Vector Drawing Tool: Incomplete
>
> Bug description:
> I  am  running  Debian  testing  on  AMD-64  hardware.  I have inscape 0.46-9
> installed.  The same thing happend  with  Ubuntu  Jaunty  i386  and  inkscape
> 0.46-5ubuntu4 installed.
>
> When you start inkscape with
>    inkscape pretty-out.svg
> it segfaults with the following output:
>
>    terminate called after throwing an instance of 'Inkscape::MalformedURIException'
>      what():  Malformed URI
>
>    Emergency save activated!
>    Emergency save completed. Inkscape will close now.
>    If you can reproduce this crash, please file a bug at www.inkscape.org
>    with a detailed description of the steps leading to the crash, so we can fix it.
>    Segmentation fault
>
> If you just start inkscape with no argument, go to the File/Open menu and try
> to open the file pretty-out.svg it dies with the output:
>
>    glibmm-ERROR **:
>    unhandled exception (type std::exception) in signal handler:
>    what: Malformed URI
>
>    aborting...
>
>    Emergency save activated!
>    Emergency save completed. Inkscape will close now.
>    If you can reproduce this crash, please file a bug at www.inkscape.org
>    with a detailed description of the steps leading to the crash, so we can fix it.
>    Segmentation fault
>
> eog, for example, has no problem displaying this SVG file.
>

unfortunately, I am on Windows so I don't know the details of which build to use, but recent versions are at:

http://sourceforge.net/projects/inkscape/files/

Despite the fact that I don't know where are daily builds I put my
recent build for you on my webspace.
I am on Ubuntu Jaunty aka 9.04. the link is here
http://www.theadib.net/inkscape.bz2

Your file uses a number of different formats to specify the colour:
a) fill: black
b) fill:url(#mistyrose)
c) fill:url(##bfefff)
d) fill:url(#none)
e) stop-color:rgb(255,0,0)

samples:
       <polygon style="fill:url(#mistyrose);stroke:mistyrose;;"
or <polygon style="fill:url(#black);stroke:black;;"

case a) and e) define an absolute colour known by svg standard or by
specifying the specific colour.
case b) c) d) reference to and colour that has been declared earlier
in the svg file like this:
the url none is defined like this:
    <linearGradient id="none" x1="0%" y1="0%" x2="100%" y2="100%">
      <stop offset="0%"
      style="stop-color:rgb(255,255,255);stop-opacity:1" />
      <stop offset="100%"
      style="stop-color:rgb(255,255,255);stop-opacity:1" />
    </linearGradient>

So what I am saying is that I think your svg file does not conform to
the SVG standard http://www.w3.org/TR/SVG/index.html
However Inkscape should not crash and give you the best result out of
your file.
Maybe you can export into an other fileformat that inkscape can handle
for you? i.e. pdf

HTH, Adib.

On Sun, Sep 6, 2009 at 12:46 AM, Alvin Penner<email address hidden> wrote:
> unfortunately, I am on Windows so I don't know the details of which
> build to use, but recent versions are at:
>
> http://sourceforge.net/projects/inkscape/files/
>
> --
> inkscape segfaults on opening this file
> https://bugs.launchpad.net/bugs/424564
> You received this bug notification because you are a member of Inkscape
> Bug Team, which is subscribed to Inkscape.
>

Cannot reproduce crash using given file on Inkscape 0.47 on Ubuntu Linux, i386. There does appear to be quirks in the way colors are defined within the file, though.