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

[Michael Zywek]

It happened directly after booting. I did not have noticed without that crash-apport.
lsb_release -rd
Description: Ubuntu precise (development branch)
Release: 12.04
apt-cache policy kde-runtime
kde-runtime:
  Installiert: 4:4.8.2-0ubuntu2
  Kandidat: 4:4.8.2-0ubuntu2
  Versionstabelle:
 *** 4:4.8.2-0ubuntu2 0
        500 http://de.archive.ubuntu.com/ubuntu/ precise/main i386 Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: kde-runtime 4:4.8.2-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic-pae 3.2.14
Uname: Linux 3.2.0-23-generic-pae i686
NonfreeKernelModules: nvidia
ApportVersion: 2.0.1-0ubuntu3
Architecture: i386
CrashCounter: 1
Date: Tue Apr 17 01:21:13 2012
Disassembly: => 0x0: Cannot access memory at address 0x0
ExecutablePath: /usr/bin/nepomukservicestub
InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120325)
ProcCmdline: /usr/bin/nepomukservicestub nepomukstorage
ProcEnviron:
 LANG=de_DE.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=0x8efe048, __in_chrg=<optimized out>) at kernel/qobject.cpp:854
 QObject::~QObject (this=0x8efe048, __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 vboxusers

[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.