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

[James]

I was relogging after installing KVM to include myself as user, then when logged back in USC, Chromium, crashed along with this error. I had other crash reports come up for the others and a third which I can't recall, tried logging into launchpad for each, lol, and found I can only log in a single time, sorry for that, so I am just reporting this crash. Hope it helps.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: activity-log-manager 0.9.7-0ubuntu4
ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
Uname: Linux 3.11.0-4-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.12.1-0ubuntu3
Architecture: amd64
Date: Thu Sep 5 08:13:30 2013
ExecutablePath: /usr/bin/gnome-control-center
ExecutableTimestamp: 1377794895
InstallationDate: Installed on 2013-09-05 (0 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130904)
MarkForUpload: True
ProcCmdline: gnome-control-center --overview
ProcCwd: /home/james
SegvAnalysis:
 Segfault happened at: 0x7fbceeddb5b6 <gtk_builder_get_object+22>: mov (%rbx),%rdx
 PC (0x7fbceeddb5b6) ok
 source "(%rbx)" (0x00000004) not located in a known VMA region (needed readable region)!
 destination "%rdx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: activity-log-manager
StacktraceTop:
 gtk_builder_get_object () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/control-center-1/panels/libactivity-log-manager.so
 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
 g_cclosure_marshal_generic () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gnome-control-center crashed with SIGSEGV in gtk_builder_get_object()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[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 #1221192, 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.