gnome-control-center crashed with SIGSEGV in gtk_builder_get_object()

Bug #838292 reported by hiptrop
30
This bug affects 6 people
Affects Status Importance Assigned to Milestone
gnome-control-center (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

played around with control settings ... crashes on colors for scanners etc. !

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gnome-control-center 1:3.1.5-0ubuntu4
ProcVersionSignature: Ubuntu 3.0.0-9.15-generic 3.0.3
Uname: Linux 3.0.0-9-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
CrashCounter: 1
Date: Wed Aug 31 20:13:12 2011
ExecutablePath: /usr/bin/gnome-control-center
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
ProcCmdline: gnome-control-center power
ProcEnviron:
 PATH=(custom, no user)
 LANG=de_AT.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x288ecb <gtk_builder_get_object+43>: mov (%esi),%edx
 PC (0x00288ecb) ok
 source "(%esi)" (0x00000100) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-control-center
StacktraceTop:
 gtk_builder_get_object () from /usr/lib/libgtk-3.so.0
 ?? () from /usr/lib/control-center-1/panels/libcolor.so
 g_cclosure_marshal_VOID__VOID () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 g_closure_invoke () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
Title: gnome-control-center crashed with SIGSEGV in gtk_builder_get_object()
UpgradeStatus: Upgraded to oneiric on 2011-07-13 (49 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
hiptrop (lilo5011) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 gtk_builder_get_object (builder=0x100, name=0x14b61c09 "dialog_virtual") at /build/buildd/gtk+3.0-3.1.12/./gtk/gtkbuilder.c:1106
 gcm_prefs_button_virtual_cancel_cb (widget=0x224cf638, prefs=0x22488050) at cc-color-panel.c:1846
 g_cclosure_marshal_VOID__VOID (closure=0x2251efb0, return_value=0x0, n_param_values=1, param_values=0x223f5f50, invocation_hint=0xbfabfb30, marshal_data=0x0) at /build/buildd/glib2.0-2.29.16/./gobject/gmarshal.c:85
 g_closure_invoke (closure=0x2251efb0, return_value=0x0, n_param_values=1, param_values=0x223f5f50, invocation_hint=0xbfabfb30) at /build/buildd/glib2.0-2.29.16/./gobject/gclosure.c:773
 signal_emit_unlocked_R (node=0x22156be0, detail=0, instance=0x224cf638, emission_return=0x0, instance_and_params=0x223f5f50) at /build/buildd/glib2.0-2.29.16/./gobject/gsignal.c:3271

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 gnome-control-center (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Revision history for this message
Pedro Villavicencio (pedro) wrote :

is this reproducible with GNOME Control Center 3.1.90?

Changed in gnome-control-center (Ubuntu):
status: New → Incomplete
visibility: private → public
Revision history for this message
Pedro Villavicencio (pedro) 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 can give us the missing information, 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 gnome-control-center (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.