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

[Kaloyan Grancharov]

The Control Panel where are the System Settings is crashing when I click on the icon of "User Accounts". So it is inaccessible, at least for me. I added a screenshot where the mouse pointer is just below this icon.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gnome-control-center 1:3.2.0-0ubuntu3
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic-pae 3.0.4
Uname: Linux 3.0.0-12-generic-pae i686
ApportVersion: 1.23-0ubuntu2
Architecture: i386
Date: Fri Sep 30 21:45:45 2011
ExecutablePath: /usr/bin/gnome-control-center
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110922)
ProcCmdline: gnome-control-center bluetooth
ProcEnviron:
 LANG=bg_BG.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xb6e4799a <g_str_hash+10>: movzbl (%ecx),%edx
 PC (0xb6e4799a) ok
 source "(%ecx)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-control-center
StacktraceTop:
 g_str_hash () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_hash_table_lookup () from /lib/i386-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/control-center-1/panels/libuser-accounts.so
 ?? () 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_str_hash()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
usr_lib_gnome-control-center:
 deja-dup 20.0-0ubuntu3
 gnome-bluetooth 3.2.0-0ubuntu1
 indicator-datetime 0.3.0-0ubuntu1

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #841280, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.