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

[Martin Schaaf]

Crashed on pressing button marked in attached screenshot.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gnome-control-center 1:3.1.91-0ubuntu5
ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4
Uname: Linux 3.0.0-10-generic x86_64
ApportVersion: 1.22.1-0ubuntu2
Architecture: amd64
Date: Sun Sep 11 23:32:11 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/gnome-control-center
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcCmdline: gnome-control-center keyboard
ProcEnviron:
 PATH=(custom, user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f49b3a5cea0 <g_str_hash>: movzbl (%rdi),%edx
 PC (0x7f49b3a5cea0) 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.29.90/./glib/gstring.c:142
 g_hash_table_lookup_node (hash_return=<synthetic pointer>, key=0x0, hash_table=0x7f49b74ae240) at /build/buildd/glib2.0-2.29.90/./glib/ghash.c:360
 g_hash_table_lookup (hash_table=0x7f49b74ae240, key=0x0) at /build/buildd/glib2.0-2.29.90/./glib/ghash.c:1022
 ?? () from /usr/lib/control-center-1/panels/libregion.so
 ?? () from /usr/lib/control-center-1/panels/libregion.so
Title: gnome-control-center crashed with SIGSEGV in g_str_hash()
UpgradeStatus: Upgraded to oneiric on 2011-09-10 (1 days ago)
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

[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.