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

Bug #846840 reported by doweller
52
This bug affects 6 people
Affects Status Importance Assigned to Milestone
gnome-control-center
Won't Fix
Critical
gnome-control-center (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Oneiric Beta 1 installation is up to date. This happend after I added a new user and tried to activate his account.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gnome-control-center 1:3.1.91-0ubuntu5
ProcVersionSignature: Ubuntu 3.0.0-10.16-generic-pae 3.0.4
Uname: Linux 3.0.0-10-generic-pae i686
NonfreeKernelModules: nvidia wl
ApportVersion: 1.22.1-0ubuntu2
Architecture: i386
Date: Sun Sep 11 09:04:38 2011
ExecutablePath: /usr/bin/gnome-control-center
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110901)
ProcCmdline: gnome-control-center
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
SegvAnalysis:
 Segfault happened at: 0xb6ef9d11 <g_type_check_instance+33>: mov (%eax),%edx
 PC (0xb6ef9d11) ok
 source "(%eax)" (0x5e5e5e5e) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-control-center
StacktraceTop:
 g_type_check_instance () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 g_signal_emit () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/control-center-1/panels/libuser-accounts.so
 ?? () from /usr/lib/control-center-1/panels/libuser-accounts.so
Title: gnome-control-center crashed with SIGSEGV in g_type_check_instance()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
usr_lib_gnome-control-center:
 deja-dup 19.91-0ubuntu3
 empathy 3.1.91-0ubuntu2
 gnome-bluetooth 3.1.4-0ubuntu1
 indicator-datetime 0.2.93-0ubuntu2

Revision history for this message
doweller (do-weller) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_type_check_instance (type_instance=0xb7ab9760) at /build/buildd/glib2.0-2.29.90/./gobject/gtype.c:4059
 g_signal_emit_valist (instance=0xb7ab9760, signal_id=352, detail=0, var_args=0xbfa5a05c "@\260\016\270p\263\344\267\001") at /build/buildd/glib2.0-2.29.90/./gobject/gsignal.c:2936
 g_signal_emit (instance=0xb7ab9760, signal_id=352, detail=0) at /build/buildd/glib2.0-2.29.90/./gobject/gsignal.c:3060
 remove_user_from_dupe_ring (manager=0xb7ab9760, user=0xb80eb040) at um-user-manager.c:144
 user_changed_handler (user=0xb80eb040, manager=0xb7ab9760) at um-user-manager.c:199

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
Launchpad Janitor (janitor) wrote : Re: gnome-control-center crashed with SIGSEGV in g_type_check_instance()

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

Changed in gnome-control-center (Ubuntu):
status: New → Confirmed
visibility: private → public
Revision history for this message
Sebastien Bacher (seb128) wrote :

There is a duplicate from current 3.2 with that description

"Crashed while I was changing my user image. After the cropping, it froze and then crashed, but the photo seems to have changed."

summary: - gnome-control-center crashed with SIGSEGV in g_type_check_instance()
+ gnome-control-center crashed with SIGSEGV in
+ remove_user_from_dupe_ring()
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=661802

Changed in gnome-control-center (Ubuntu):
status: Confirmed → Triaged
Changed in gnome-control-center:
importance: Undecided → Unknown
status: New → Unknown
Changed in gnome-control-center:
importance: Unknown → Critical
status: Unknown → New
Changed in gnome-control-center:
status: New → Won't Fix
Revision history for this message
Sebastien Bacher (seb128) wrote :

the code which had that issue has been rewritten since which deprecates the bug

Changed in gnome-control-center (Ubuntu):
status: Triaged → 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.