gnome-control-center produces this crash when you go to open up "User Accounts".
I am doing a "GNOME" (GNOME 3) session.
I am filing this at the suggestion of Sebastien Bacher on bug 854231.
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gnome-control-center 1:3.2.0-0ubuntu6
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: Fri Oct 7 21:42:52 2011
ExecutablePath: /usr/bin/gnome-control-center
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901)
ProcCmdline: gnome-control-center --overview
ProcCwd: /home/mike
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7fed2cc62b30 <g_str_hash>: movzbl (%rdi),%edx
PC (0x7fed2cc62b30) ok
source "(%rdi)" (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 (v=0x0) at /build/buildd/glib2.0-2.30.0/./glib/gstring.c:142
g_hash_table_lookup_node (hash_return=<synthetic pointer>, key=0x0, hash_table=0x7fed303be5e0) at /build/buildd/glib2.0-2.30.0/./glib/ghash.c:360
g_hash_table_lookup (hash_table=0x7fed303be5e0, key=0x0) at /build/buildd/glib2.0-2.30.0/./glib/ghash.c:1022
count_languages_and_territories () at gdm-languages.c:638
collect_locales () at gdm-languages.c:663
Title: gnome-control-center crashed with SIGSEGV in g_str_hash()
UpgradeStatus: Upgraded to oneiric on 2011-10-01 (6 days ago)
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-0ubuntu3
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.