nepomukservicestub crashed with SIGSEGV in QObject::~QObject()

[Ernest Hirose]

Failed imediately after reboot then logon

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: kde-runtime 4:4.8.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic-pae 3.2.14
Uname: Linux 3.2.0-23-generic-pae i686
ApportVersion: 2.0.1-0ubuntu2
Architecture: i386
CrashCounter: 1
Date: Thu Apr 12 10:43:06 2012
Disassembly: => 0x0: Cannot access memory at address 0x0
ExecutablePath: /usr/bin/nepomukservicestub
InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120129)
ProcCmdline: /usr/bin/nepomukservicestub nepomukstorage
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x0: Cannot access memory at address 0x0
 PC (0x00000000) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: kde-runtime
StacktraceTop:
 ?? ()
 QObject::~QObject (this=0x99fe078, __in_chrg=<optimized out>) at kernel/qobject.cpp:854
 QObject::~QObject (this=0x99fe078, __in_chrg=<optimized out>) at kernel/qobject.cpp:940
 _start ()
Title: nepomukservicestub crashed with SIGSEGV in QObject::~QObject()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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