inkscape crashed with SIGSEGV

Bug #448766 reported by Ivan Sagalaev
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Inkscape
Invalid
High
Unassigned
inkscape (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: inkscape

Inkscape crashed after dragging and dropping an SVG-file onto top panels in the main window.

ProblemType: Crash
Architecture: i386
Date: Sun Oct 11 18:58:39 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/inkscape
Package: inkscape 0.47~pre1-0ubuntu2
ProcCmdline: inkscape
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-13.44-generic
SegvAnalysis:
 Segfault happened at: 0x80b733c: mov 0xcc(%esi),%edi
 PC (0x080b733c) ok
 source "0xcc(%esi)" (0x000000cc) not located in a known VMA region (needed readable region)!
 destination "%edi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: inkscape
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: inkscape crashed with SIGSEGV
Uname: Linux 2.6.31-13-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Ivan Sagalaev (isagalaev) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:persp3d_unselected_boxes (selection=0xa032b48)
persp3d_split_perspectives_according_to_selection (
sp_group_set_transform (item=0xb2f3920, xform=@0xb2f39a0)
sp_item_write_transform (item=0xb2f3920, repr=0xb8525f0,
sp_selection_apply_affine (selection=0xa032b48,

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in inkscape (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Bryce Harrington (bryce)
visibility: private → public
su_v (suv-lp)
tags: added: 3dbox crash
Revision history for this message
su_v (suv-lp) wrote :

The 3dbox code has seen a major refactoring in revision 8911: the code where this crash happened does no longer exist in Inkscape trunk and in the branch for 0.48.

Can you test with 0.48pre1 or a nightly build of 0.47+devel (or 0.48+devel) if the crash still occurs or attach the file which caused this crash (as well as more detailed steps how to reproduce?)

Changed in inkscape:
status: New → Incomplete
importance: Undecided → High
Changed in inkscape (Ubuntu):
status: New → Incomplete
Revision history for this message
Ivan Sagalaev (isagalaev) wrote :

Guys, it was ten months ago! Of course I don't remember what I was doing that time exactly. And I'm sure I would describe steps to reproduce back then if I would able to do it. Most probably it was just a random crasher in the middle of something. Anyway since you've refactored the whole subsystem I think it's safe just mark the ticket as invalid and wait for other crashers if any.

Revision history for this message
su_v (suv-lp) wrote :

Sorry for the delayed response (the report only recently was changed from 'private' to 'public' and filed affecting the Inkscape project too). Closing for now - please reopen if the crash reoccurs with the current prerelease/nightlies or the upcoming stable version 0.48.

Changed in inkscape:
status: Incomplete → Invalid
Changed in inkscape (Ubuntu):
status: Incomplete → Invalid
status: Invalid → Incomplete
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.