akonadi_agent_launcher crashed with SIGSEGV in typeinfo name for KStandardDirs()

[mindphreak]

This happened after logging into the desktop.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: akonadi-server 1.6.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4
Uname: Linux 3.0.0-10-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 1.22.1-0ubuntu2
Architecture: i386
CrashCounter: 1
Date: Sun Sep 11 18:34:02 2011
ExecutablePath: /usr/bin/akonadi_agent_launcher
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta i386 (20110411.1)
ProcCmdline: /usr/bin/akonadi_agent_launcher akonadi_contacts_resource akonadi_contacts_resource_0
SegvAnalysis:
 Segfault happened at: 0x3e60352 <_ZTS13KStandardDirs>: xor %esi,(%ebx)
 PC (0x03e60352) ok
 source "%esi" ok
 destination "(%ebx)" (0x00842ff4) in non-writable VMA region: 0x0083c000-0x00843000 r--p /usr/lib/i386-linux-gnu/libQtCore.so.4.7.4
SegvReason: writing VMA /usr/lib/i386-linux-gnu/libQtCore.so.4.7.4
Signal: 11
SourcePackage: akonadi
StacktraceTop:
 typeinfo name for KStandardDirs () from /usr/lib/libkdecore.so.5
 QThreadStorage<QFontCache*>::deleteData (x=0x834a338) at ../../include/QtCore/../../src/corelib/thread/qthreadstorage.h:133
 QThreadStorageData::set (this=0x8317c30, p=0x0) at thread/qthreadstorage.cpp:165
 qThreadStorage_setLocalData<QFontCache> (d=..., t=<optimized out>) at ../../include/QtCore/../../src/corelib/thread/qthreadstorage.h:92
 setLocalData (t=0x0, this=0x8317c30) at ../../include/QtCore/../../src/corelib/thread/qthreadstorage.h:148
Title: akonadi_agent_launcher crashed with SIGSEGV in typeinfo name for KStandardDirs()
UpgradeStatus: Upgraded to oneiric on 2011-09-05 (6 days ago)
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 #815408, 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.