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

Bug #861579 reported by Daryl Wong
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
gnome-control-center
Expired
Critical
gnome-control-center (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Occurred after adding a network printer shared through windows (HP Colour Laser Jet 2605 Postscript driver)

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gnome-control-center 1:3.2.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
ApportVersion: 1.23-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Thu Sep 29 00:51:33 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/gnome-control-center
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcCmdline: gnome-control-center
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_SG.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f3c671144db <gtk_tree_store_append+43>: mov 0x18(%rdi),%r13
 PC (0x7f3c671144db) ok
 source "0x18(%rdi)" (0x00000019) not located in a known VMA region (needed readable region)!
 destination "%r13" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-control-center
StacktraceTop:
 gtk_tree_store_append () from /usr/lib/libgtk-3.so.0
 ?? () from /usr/lib/control-center-1/panels/libcolor.so
 ?? () from /usr/lib/control-center-1/panels/libcolor.so
 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: gnome-control-center crashed with SIGSEGV in gtk_tree_store_append()
UpgradeStatus: Upgraded to oneiric on 2011-09-19 (9 days ago)
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev sambashare video
usr_lib_gnome-control-center:
 deja-dup 20.0-0ubuntu3
 gnome-bluetooth 3.2.0-0ubuntu1
 indicator-datetime 0.2.95-0ubuntu1

Revision history for this message
Daryl Wong (theazure) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 gtk_tree_store_append (tree_store=0x1, iter=0x7fff6809f310, parent=0x0) at /build/buildd/gtk+3.0-3.2.0/./gtk/gtktreestore.c:1737
 gcm_prefs_add_device (prefs=0x7f3c68826000, device=0x7f3c689922d0) at cc-color-panel.c:1716
 gcm_prefs_device_added_cb (client=<optimized out>, device=<optimized out>, prefs=0x7f3c68826000) at cc-color-panel.c:1810
 g_closure_invoke (closure=0x7f3c688318e0, return_value=0x0, n_param_values=2, param_values=0x7f3c68908e10, invocation_hint=<optimized out>) at /build/buildd/glib2.0-2.30.0/./gobject/gclosure.c:774
 signal_emit_unlocked_R (node=<optimized out>, detail=0, instance=0x7f3c688ae6a0, emission_return=0x0, instance_and_params=0x7f3c68908e10) at /build/buildd/glib2.0-2.30.0/./gobject/gsignal.c:3272

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-amd64-retrace
visibility: private → public
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for your bug report. This bug has been reported to the developers of the software. You can track it and make comments at:
 https://bugzilla.gnome.org/show_bug.cgi?id=660479

Changed in gnome-control-center (Ubuntu):
status: New → Triaged
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Daryl, may you please tell us exactly what were you doing when the app crashed? thanks in advance!.

Changed in gnome-control-center:
importance: Unknown → Critical
status: Unknown → New
Changed in gnome-control-center:
status: New → Incomplete
Changed in gnome-control-center (Ubuntu):
status: Triaged → Incomplete
Changed in gnome-control-center:
status: Incomplete → Expired
Revision history for this message
Sebastien Bacher (seb128) wrote :

no reply, closing the bug

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.