inkscape crashed with SIGSEGV in Inkscape::Preferences::_getNode()

Bug #983843 reported by Porx Grinder
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Inkscape
Invalid
High
Unassigned
inkscape (Ubuntu)
Expired
Medium
Unassigned

Bug Description

1) Description: Ubuntu precise (development branch)
Release: 12.04

2) inkscape:
  Installed: 0.48.3.1-1ubuntu1
  Candidate: 0.48.3.1-1ubuntu1
  Version table:
 *** 0.48.3.1-1ubuntu1 0
        500 http://archive.ubuntu.com/ubuntu/ precise/main i386 Packages
        100 /var/lib/dpkg/status

3) Tried to merge paths

4) Inkscape crashed

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: inkscape 0.48.3.1-1ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
Uname: Linux 3.2.0-23-generic i686
ApportVersion: 2.0.1-0ubuntu4
Architecture: i386
CrashCounter: 1
Date: Mon Apr 16 19:20:31 2012
ExecutablePath: /usr/bin/inkscape
InstallationMedia: Xubuntu 11.04 "Natty Narwhal" - Release i386 (20110427)
ProcCmdline: inkscape
SegvAnalysis:
 Segfault happened at: 0x829d01c <_ZN8Inkscape11Preferences8_getNodeERKN4Glib7ustringEb+92>: mov (%eax),%edx
 PC (0x0829d01c) ok
 source "(%eax)" (0x00000288) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: inkscape
Stacktrace:
 #0 0x0829d01c in Inkscape::Preferences::_getNode(Glib::ustring const&, bool) ()
 No symbol table info available.
 Cannot access memory at address 0xbff66fec
StacktraceTop: Inkscape::Preferences::_getNode(Glib::ustring const&, bool) ()
ThreadStacktrace:
 .
 Thread 3 (LWP 7422):
 #0 0x0049f416 in __kernel_vsyscall ()
 No symbol table info available.
 .
Title: inkscape crashed with SIGSEGV in Inkscape::Preferences::_getNode()
UpgradeStatus: Upgraded to precise on 2012-03-07 (40 days ago)
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev sambashare scanner tape video

Revision history for this message
Porx Grinder (marx-grinder) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop: Inkscape::Preferences::_getNode (this=Cannot access memory at address 0xbff66ff0

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in inkscape (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Revision history for this message
Alex Valavanis (valavanisalex) wrote :

Thanks for reporting this bug. We'll need some more information to help you, though:

1. Has this just happened once, or is it a reproducible issue? If it's reproducible, please could you provide step-by-step instructions for how we can reproduce the problem?

2. Does it happen when you are editing a specific file? If so, please could you provide it?

visibility: private → public
tags: added: crash node-editing
tags: removed: node-editing
Changed in inkscape:
importance: Undecided → High
status: New → Incomplete
Changed in inkscape (Ubuntu):
status: New → Incomplete
Revision history for this message
su_v (suv-lp) wrote :

Like bug #937835 “inkscape crashed with SIGSEGV in Inkscape::Preferences::_getNode()” a duplicate of Bug #941317 “inkscape crashed with SIGSEGV in getObject()”?

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for inkscape (Ubuntu) because there has been no activity for 60 days.]

Changed in inkscape (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Kris (kris-degussem) wrote :

@Porx Grinder: could you check whether you are still affected? If so, could you have a look at comment 5?

Revision history for this message
Porx Grinder (marx-grinder) wrote :

Well... I haven't experienced crashes for a while... Can't really remember what I did at the time it happened... Is there any other way to check?

Revision history for this message
Kris (kris-degussem) wrote :

OK. Thanks for the update.
Considering this as a duplicate of another bug (see comment 6), but because it could not be checked anymore, marking this report as invalid.

Changed in inkscape:
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.