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

[Nathan Müller]

no

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: kde-runtime 4:4.8.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-18.29-generic-pae 3.2.9
Uname: Linux 3.2.0-18-generic-pae i686
NonfreeKernelModules: fglrx
ApportVersion: 1.94.1-0ubuntu2
Architecture: i386
Date: Tue Mar 13 22:15:02 2012
Disassembly: => 0x0: Cannot access memory at address 0x0
ExecutablePath: /usr/bin/nepomukservicestub
InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120228.1)
ProcCmdline: /usr/bin/nepomukservicestub nepomukfilewatch
ProcEnviron:
 LANGUAGE=de_DE
 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=0x8bca0b8, __in_chrg=<optimized out>) at kernel/qobject.cpp:854
 QObject::~QObject (this=0x8bca0b8, __in_chrg=<optimized out>) at kernel/qobject.cpp:940
 _start ()
Title: nepomukservicestub crashed with SIGSEGV in QObject::~QObject()
UpgradeStatus: Upgraded to precise on 2012-03-12 (1 days ago)
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 #913024, 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.