Crash is repeatable:
1. open control center
2. click on 'keyboard'
3. click on 'layout settings' link
4. click on 'keyboard settings...' link
5. go back to the 'typing' tab
6. click on the 'layout settings' link -> crash
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: gnome-control-center 1:3.6.3-0ubuntu31
ProcVersionSignature: Ubuntu 3.11.0-3.8-generic 3.11.0-rc6
Uname: Linux 3.11.0-3-generic x86_64
ApportVersion: 2.12.1-0ubuntu2
Architecture: amd64
Date: Sat Aug 24 15:32:46 2013
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2013-06-22 (63 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130621)
MarkForUpload: True
ProcCmdline: gnome-control-center region layouts
ProcEnviron:
SHELL=/bin/bash
XDG_RUNTIME_DIR=<set>
PATH=(custom, no user)
LANGUAGE=en_AU:en
LANG=en_AU.UTF-8
Signal: 6
SourcePackage: gnome-control-center
StacktraceTop:
?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
ibus_config_get_value () from /usr/lib/x86_64-linux-gnu/libibus-1.0.so.5
?? () from /usr/lib/x86_64-linux-gnu/control-center-1/panels/libregion.so
Title: [region]: gnome-control-center crashed with SIGABRT in g_assertion_message()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
usr_lib_gnome-control-center:
activity-log-manager 0.9.7-0ubuntu4
deja-dup 27.3.1-0ubuntu1
gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1
gnome-control-center-unity 1.3daily13.06.14.1-0ubuntu1
indicator-datetime 12.10.3+13.10.20130822.1-0ubuntu1
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1216192, 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.