inkscape crashed with SIGSEGV in IA__gtk_widget_set_sensitive()

Bug #1222524 reported by Alexander
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Inkscape
New
High
Unassigned
inkscape (Ubuntu)
New
Medium
Unassigned

Bug Description

draw poligon

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: inkscape 0.48.4-1ubuntu3
ProcVersionSignature: Ubuntu 3.11.0-5.11-generic 3.11.0
Uname: Linux 3.11.0-5-generic x86_64
ApportVersion: 2.12.1-0ubuntu3
Architecture: amd64
Date: Sun Sep 8 23:05:39 2013
ExecutablePath: /usr/bin/inkscape
InstallationDate: Installed on 2013-09-08 (0 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130908)
MarkForUpload: True
ProcCmdline: inkscape
SegvAnalysis:
 Segfault happened at: 0x7faf1d16fb8d <gtk_widget_set_sensitive+29>: cmp %rax,(%rdx)
 PC (0x7faf1d16fb8d) ok
 source "%rax" ok
 destination "(%rdx)" (0xaaaaaaaaaaaaaaaa) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: inkscape
StacktraceTop:
 gtk_widget_set_sensitive () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
 Inkscape::UI::Dialogs::colorItemHandleButtonPress(_GtkWidget*, _GdkEventButton*, void*) ()
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: inkscape crashed with SIGSEGV in gtk_widget_set_sensitive()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Alexander (greenev-a1987) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 IA__gtk_widget_set_sensitive (widget=0x7a2d450, sensitive=0) at /build/buildd/gtk+2.0-2.24.20/gtk/gtkwidget.c:6320
 Inkscape::UI::Dialogs::colorItemHandleButtonPress (widget=0x359ba20, event=0x5ed8420, user_data=0x2cab3e0) at ui/dialog/swatches.cpp:304
 _gtk_marshal_BOOLEAN__BOXED (closure=0x359f4b0, return_value=0x7fff6336c1f0, n_param_values=<optimized out>, param_values=0x7fff6336c2a0, invocation_hint=<optimized out>, marshal_data=0x0) at /build/buildd/gtk+2.0-2.24.20/gtk/gtkmarshalers.c:86
 g_closure_invoke (closure=0x359f4b0, return_value=0x7fff6336c1f0, n_param_values=2, param_values=0x7fff6336c2a0, invocation_hint=0x7fff6336c240) at /build/buildd/glib2.0-2.37.6/./gobject/gclosure.c:777
 signal_emit_unlocked_R (node=node@entry=0x1d6ba80, detail=detail@entry=0, instance=instance@entry=0x359ba20, emission_return=emission_return@entry=0x7fff6336c370, instance_and_params=instance_and_params@entry=0x7fff6336c2a0) at /build/buildd/glib2.0-2.37.6/./gobject/gsignal.c:3582

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in inkscape (Ubuntu):
importance: Undecided → Medium
summary: - inkscape crashed with SIGSEGV in gtk_widget_set_sensitive()
+ inkscape crashed with SIGSEGV in IA__gtk_widget_set_sensitive()
tags: removed: need-amd64-retrace
information type: Private → Public
tags: added: crash
Kris (kris-degussem)
Changed in inkscape:
importance: Undecided → High
Revision history for this message
Kris (kris-degussem) wrote :

Quite probably the underlying issue is the same as in bug #1219264. Unfortunately also no extra info here, that helps in checking on how to provoke the issue and see if it is fixed.
Hence, I propose to mark it is duplicate of bug #1219264.

Revision history for this message
jazzynico (jazzynico) wrote :

> Hence, I propose to mark it is duplicate of bug #1219264.

Agreed. It's almost at the same code location, and is probably fixed by your patch.

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.