akonadi_agent_launcher crashed with SIGSEGV in vtable for __cxxabiv1::__class_type_info()

[bra10n]

Clean install of Kubuntu 11.10
Applied all updates, installed Firefox via provided menu installer
Problem noted after first log-out...
Crash notifier at top of blank-screen, also in system tray after sucessful log-in

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: akonadi-server 1.6.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-9.15-generic 3.0.3
Uname: Linux 3.0.0-9-generic x86_64
Architecture: amd64
Date: Fri Sep 2 12:44:40 2011
ExecutablePath: /usr/bin/akonadi_agent_launcher
InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901)
ProcCmdline: /usr/bin/akonadi_agent_launcher akonadi_contacts_resource akonadi_contacts_resource_0
ProcEnviron:
 LANGUAGE=en_AU:en
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x60f5b0 <_ZTVN10__cxxabiv117__class_type_infoE+16>: (bad)
 PC (0x0060f5b0) in non-executable VMA region: 0x0060f000-0x00610000 rw-p /usr/bin/akonadi_agent_launcher
SegvReason: executing writable VMA /usr/bin/akonadi_agent_launcher
Signal: 11
SourcePackage: akonadi
StacktraceTop:
 vtable for __cxxabiv1::__class_type_info ()
 QThreadStorageData::set(void*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
 ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
 QApplication::~QApplication() () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
 ?? ()
Title: akonadi_agent_launcher crashed with SIGSEGV in vtable for __cxxabiv1::__class_type_info()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #815273, 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.