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

[Afterlifesol]

Was adding a dot folder to the list. First time doing this and it crashed after I hit the ok button, when I returned to the window after the folder was there and I added another without issue.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: activity-log-manager-control-center 0.9.4-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14
Uname: Linux 3.2.0-22-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.0.1-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Wed Apr 11 00:34:39 2012
ExecutablePath: /usr/bin/gnome-control-center
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
ProcCmdline: gnome-control-center background
SegvAnalysis:
 Segfault happened at: 0x7fd1571571b8 <g_type_check_instance+56>: testb $0x4,0x16(%rdx)
 PC (0x7fd1571571b8) ok
 source "$0x4" ok
 destination "0x16(%rdx)" (0x7fd100000382) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: activity-log-manager
StacktraceTop:
 g_type_check_instance () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_by_name () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/control-center-1/panels/libactivity-log-manager.so
 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: gnome-control-center crashed with SIGSEGV in g_type_check_instance()
UpgradeStatus: Upgraded to precise on 2012-04-11 (0 days ago)
UserGroups: adm admin cdrom dialout fuse lpadmin plugdev sambashare

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