Keyboard layout options crashed in gnome-control-center

[ILLIOS]

When I open and choose keyboard layout options, or run gnome-control-center region from terminal, gnome-control-center crashes with SIGSEGV

Ubuntu 11.10
gnome-control-center 3.2.0-ubuntu6

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gnome-control-center 1:3.2.0-0ubuntu6
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic-pae 3.0.4
Uname: Linux 3.0.0-12-generic-pae i686
ApportVersion: 1.23-0ubuntu3
Architecture: i386
Date: Tue Oct 18 10:00:54 2011
ExecutablePath: /usr/bin/gnome-control-center
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
ProcCmdline: gnome-control-center region
ProcEnviron:
 SHELL=/bin/zsh
 LANGUAGE=ru_RU:ru:en_GB:en
 PATH=(custom, user)
 LANG=ru_RU.utf8
SegvAnalysis:
 Segfault happened at: 0xb6d7227b <__strcmp_ssse3+11>: cmp %cl,(%edx)
 PC (0xb6d7227b) ok
 source "%cl" ok
 destination "(%edx)" (0x00000000) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: gnome-control-center
StacktraceTop:
 __strcmp_ssse3 () at ../sysdeps/i386/i686/multiarch/strcmp-ssse3.S:75
 g_str_equal () from /lib/i386-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/control-center-1/panels/libregion.so
 g_type_create_instance () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
Title: gnome-control-center crashed with SIGSEGV in __strcmp_ssse3()
UpgradeStatus: Upgraded to oneiric on 2011-10-14 (4 days ago)
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare
usr_lib_gnome-control-center:
 deja-dup 20.0-0ubuntu3
 gnome-bluetooth 3.2.0-0ubuntu2
 indicator-datetime 0.3.1-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 #839415, 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.