Ubuntu

inkscape crashed with SIGABRT in raise()

Reported by Rodolfo Pereira on 2011-07-14
32
This bug affects 6 people
Affects Status Importance Assigned to Milestone
Inkscape
High
Unassigned
inkscape (Ubuntu)
Medium
Unassigned

Bug Description

Crash when trying to edit a shadow filter

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: inkscape 0.48.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-5.6-generic 3.0.0-rc7
Uname: Linux 3.0.0-5-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Wed Jul 13 22:19:22 2011
ExecutablePath: /usr/bin/inkscape
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
ProcCmdline: inkscape
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: inkscape
StacktraceTop:
 raise () from /lib/x86_64-linux-gnu/libc.so.6
 abort () from /lib/x86_64-linux-gnu/libc.so.6
 g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 sp_document_maybe_done(SPDocument*, char const*, unsigned int, Glib::ustring) ()
Title: inkscape crashed with SIGABRT in raise()
UpgradeStatus: Upgraded to oneiric on 2011-07-13 (0 days ago)
UserGroups: adm admin cdrom dialout fuse lpadmin plugdev sambashare

Rodolfo Pereira (phinpho) wrote :

StacktraceTop:
 raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
 abort () at abort.c:121
 g_assertion_message (domain=<value optimized out>, file=<value optimized out>, line=<value optimized out>, func=0xcea2a0 "void sp_document_maybe_done(SPDocument*, const gchar*, unsigned int, Glib::ustring)", message=0xb2c5100 "assertion failed: (doc->priv->sensitive)") at /build/buildd/glib2.0-2.29.10/./glib/gtestutils.c:1425
 g_assertion_message_expr (domain=0x0, file=0xcea19d "document-undo.cpp", line=172, func=0xcea2a0 "void sp_document_maybe_done(SPDocument*, const gchar*, unsigned int, Glib::ustring)", expr=<value optimized out>) at /build/buildd/glib2.0-2.29.10/./glib/gtestutils.c:1436
 sp_document_maybe_done (doc=0x24a8f00, key=0xa5e3568 "filtereffects:stdDeviation", event_type=204, event_description=...) at document-undo.cpp:172

Changed in inkscape (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
visibility: private → public
~suv (suv-lp) wrote :

Not reproduced with Inkscape 0.48.2 r9819 on Mac OS X 10.5.8 (i386)
Applying 'Filters > Shadows and Glows > Drop Shadow', and editing any of the filter primitives values of the drop shadow later on does not cause Inkscape to crash.

> Crash when trying to edit a shadow filter

Please provide a more detailed 'steps to reproduce' and attach a sample SVG file which can be used to reproduce the crash (Based on the provided information, it is unclear how to try to reproduce the crash: does it crash when changing the settings in the extension dialog, or when opening the 'Filter Editor' dialog, or when applying changes in the Filter Editor, limited to certain objects or files only etc.)

Changed in inkscape:
importance: Undecided → High
status: New → Incomplete
tags: added: crash filters-svg
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in inkscape (Ubuntu):
status: New → Confirmed
TK (tkrishan) wrote :

Inkscape crashed with version 0.48.2-0ubuntu4 (precise).

The operation being performed was File / Import From Open Clip Art Library. The search term was "arrow". In viewing the various arrows from the library, Inkscape crashed.

~suv (suv-lp) wrote :

@TK - a crash when browsing files in "Import From Open Clip Art Library…" is not related with the reported issue here (bug #810238), which was described as:
> Crash when trying to edit a shadow filter

Bug status for the 'Inkscape' project will not be changed - see comment #5.

Kris (kris-degussem) wrote :

Rodolfo, do you still encounter this error? If so could you try with a more recent Inkscape version and have provide a more detailed overview of actions that lead to the error?

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers