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

[jerrylamos]

booted new 13.10 install was doing update

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: activity-log-manager 0.9.7-0ubuntu3
ProcVersionSignature: Ubuntu 3.10.0-2.10-generic 3.10.0
Uname: Linux 3.10.0-2-generic i686
ApportVersion: 2.10.2-0ubuntu4
Architecture: i386
Date: Mon Jul 15 21:47:04 2013
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2013-07-16 (0 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130712)
MarkForUpload: True
ProcCmdline: gnome-control-center
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
 LANGUAGE=en_US
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0xacb48fcf: mov 0x0(%ebp),%eax
 PC (0xacb48fcf) ok
 source "0x0(%ebp)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: activity-log-manager
StacktraceTop:
 ?? () from /usr/lib/i386-linux-gnu/control-center-1/panels/libactivity-log-manager.so
 ffi_call_SYSV () from /usr/lib/i386-linux-gnu/libffi.so.6
 ffi_call () from /usr/lib/i386-linux-gnu/libffi.so.6
 g_cclosure_marshal_generic () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 g_closure_invoke () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
Title: gnome-control-center crashed with SIGSEGV in ffi_call_SYSV()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Manish Sinha (मनीष सिन्हा) (manishsinha)]

Can anyone reproduce this crash with symbols installed?

[jerrylamos (jerrylamos)]

Synaptic lists lots and lots and lots of packages with the words "gnome" and "dbg" in them.

Can you be specific about which synaptic package(s) you would like installed? Thanks.

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