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

[Stefan K.]

Crashed directly after reboot (after updates were installed).

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: akonadi-server 1.6.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
Uname: Linux 3.0.0-11-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu1
Architecture: amd64
Date: Wed Sep 14 21:34:51 2011
ExecutablePath: /usr/bin/akonadi_agent_launcher
InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110830.1)
ProcCmdline: /usr/bin/akonadi_agent_launcher akonadi_contacts_resource akonadi_contacts_resource_3
ProcEnviron:
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
 LANGUAGE=
SegvAnalysis:
 Segfault happened at: 0x60f5b0 <_ZTVN10__cxxabiv117__class_type_infoE+16>: rolb $0x0,0x7f492ee9(%rbp)
 PC (0x0060f5b0) in non-executable VMA region: 0x0060f000-0x00610000 rw-p /usr/bin/akonadi_agent_launcher
 source "$0x0" ok
 destination "0x7f492ee9(%rbp)" (0x7f492ef0) not located in a known VMA region (needed writable region)!
SegvReason:
 executing writable VMA /usr/bin/akonadi_agent_launcher
 writing unknown VMA
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
 ?? ()
 ?? ()
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 #847826, 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.