inkscape crashed with SIGSEGV in sp_repr_do_read

Bug #213303 reported by Chris Moore
12
Affects Status Importance Assigned to Milestone
inkscape (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: inkscape

I tried to run it, it crashed, and something asked me to let it report the crash, so that's what I'm doing. It seems to want me to fill in this form, but how am I supposed to know if it's the same bug as the many other "inkscape crashed with SIGSEGV" bugs?

ProblemType: Crash
Architecture: i386
Date: Mon Apr 7 13:44:18 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/inkscape
NonfreeKernelModules: fglrx
Package: inkscape 0.46-0ubuntu1
PackageArchitecture: i386
ProcCmdline: inkscape hueco.svg
ProcEnviron:
 SHELL=/bin/bash
 PATH=/home/username/programs/git/install/bin:/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_GB.UTF-8
Signal: 11
SourcePackage: inkscape
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: inkscape crashed with SIGSEGV
Uname: Linux 2.6.24-14-generic i686
UserGroups: adm admin audio cdrom dialout dip disk floppy fuse lpadmin netdev plugdev powerdev sambashare scanner video www-data
SegvAnalysis:
 Segfault happened at: 0xb6bcc3b5 <GC_malloc+85>: mov 0x4(%eax),%edx
 PC (0xb6bcc3b5) ok
 source "0x4(%eax)" (0x000000cc) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA

Revision history for this message
Chris Moore (dooglus) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? ()
?? ()
sp_repr_do_read (doc=0x883b570, default_ns=0x0) at ./xml/node.h:41
sp_repr_read_mem (buffer=0x883b570 "", length=13163, default_ns=0x0) at xml/repr-io.cpp:309
Inkscape::Preferences::loadSkeleton () at preferences.cpp:34

Revision history for this message
Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount) wrote :

 Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

Changed in inkscape:
status: New → Incomplete
Revision history for this message
Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount) wrote :

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

Revision history for this message
Bryce Harrington (bryce) wrote :

There's already a fairly good backtrace on this one, and inkscape hasn't changed version, so no particular reason we'd think this is fixed. Looks like a basic null pointer issue.

Changed in inkscape (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Bryce Harrington (bryce) wrote :

A pre-release of the upcoming Inkscape 0.47 is now available in Ubuntu
Karmic for testing. Because *so* much stuff has changed compared with
the version you reported your bug against, would you mind re-testing
this new version and see if this bug is now resolved?

Karmic Alpha CD ISO images are available at:

  http://cdimage.ubuntu.com/releases/karmic/

If you're not testing Karmic yet, there are .debs of this new Inkscape
for Jaunty, Hardy, and Intrepid here:

  https://launchpad.net/~inkscape.testers/+archive/ppa

You might find further bugs when testing this alpha release. If that is
the case, please file a NEW bug report here:

   https://edge.launchpad.net/inkscape/+filebug

Thanks ahead of time for your testing efforts, and enjoy the new Inkscape!

Changed in inkscape (Ubuntu):
status: Confirmed → New
status: New → Incomplete
Revision history for this message
Alex Valavanis (valavanisalex) wrote :

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

Kees Cook (kees)
description: updated
Revision history for this message
Alex Valavanis (valavanisalex) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you still experience the bug with the latest 0.47 development release of inkscape, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in inkscape (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.