[keyboard]: gnome-control-center crashed with SIGSEGV in g_closure_invoke()

[bcbc]

Running Saucy, booted up, hit Ctrl+Alt+T to get to a terminal (probably before the desktop appeared as it was taking a while). Crash. That's about it.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: gnome-control-center 1:3.6.3-0ubuntu30
Uname: Linux 3.11.0-031100rc2-generic x86_64
ApportVersion: 2.11-0ubuntu1
Architecture: amd64
CheckboxSubmission: dd7f729683fa7fd3f2e256ba311e86cb
CheckboxSystem: d00f84de8a555815fa1c4660280da308
Date: Sat Jul 27 01:06:09 2013
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2011-10-08 (657 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20111006)
MarkForUpload: True
ProcCmdline: gnome-control-center
ProcCwd: /home/bcbc
SegvAnalysis:
 Segfault happened at: 0x7ff164030be4: cmpb $0x0,(%rax)
 PC (0x7ff164030be4) ok
 source "$0x0" ok
 destination "(%rax)" (0xaaaaaaaaaaaaaaaa) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: gnome-control-center
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/control-center-1/panels/libkeyboard.so
 ?? () from /usr/lib/x86_64-linux-gnu/control-center-1/panels/libkeyboard.so
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: [keyboard]: gnome-control-center crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: Upgraded to saucy on 2013-05-04 (83 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
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.20130725-0ubuntu1

[Apport retracing service (apport)]

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 #1205588, 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.