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

[YuBerion]

After login akonadi_agent_launcher crashes
in __cxxabiv1::__class_type_info()

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
CrashCounter: 1
Date: Fri Sep 16 03:14:11 2011
ExecutablePath: /usr/bin/akonadi_agent_launcher
InstallationMedia: Kubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427)
ProcCmdline: /usr/bin/akonadi_agent_launcher akonadi_contacts_resource akonadi_contacts_resource_5
ProcEnviron:
 LANGUAGE=ru_UA
 LANG=ru_UA.UTF-8
 LC_MESSAGES=ru_UA.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x60f5b0 <_ZTVN10__cxxabiv117__class_type_infoE+16>: rolb $0x0,0x7fe546b3(%rbp)
 PC (0x0060f5b0) in non-executable VMA region: 0x0060f000-0x00610000 rw-p /usr/bin/akonadi_agent_launcher
 source "$0x0" ok
 destination "0x7fe546b3(%rbp)" (0x7fe546be) 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 (this=0x1110110, p=0x0) at thread/qthreadstorage.cpp:165
 qt_cleanup () at kernel/qapplication_x11.cpp:2687
 QApplication::~QApplication (this=0x7fff3bb93c90, __in_chrg=<optimized out>) at kernel/qapplication.cpp:1185
 ?? ()
Title: akonadi_agent_launcher crashed with SIGSEGV in vtable for __cxxabiv1::__class_type_info()
UpgradeStatus: Upgraded to oneiric on 2011-09-02 (14 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers

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