nepomukservicestub crashed with SIGSEGV in QObject::event()

[Pritesh Jain]

nepomukservicestub crashed with SIGSEGV in QObject::event()

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: nepomuk-core 4:4.9.2-0ubuntu2
ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
Uname: Linux 3.5.0-18-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.6.1-0ubuntu6
Architecture: amd64
Date: Thu Nov 29 21:56:17 2012
ExecutablePath: /usr/bin/nepomukservicestub
InstallationDate: Installed on 2012-04-30 (212 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
MarkForUpload: True
ProcCmdline: /usr/bin/nepomukservicestub nepomukfileindexer
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f06d7cfed0a: mov 0x10(%rax),%rax
 PC (0x7f06d7cfed0a) ok
 source "0x10(%rax)" (0x00000010) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nepomuk-core
StacktraceTop:
 ?? () from /usr/lib/libsopranoclient.so.1
 ?? () from /usr/lib/libsoprano.so.4
 ?? () from /usr/lib/kde4/nepomukfileindexer.so
 ?? () from /usr/lib/kde4/nepomukfileindexer.so
 QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
Title: nepomukservicestub crashed with SIGSEGV in QObject::event()
UpgradeStatus: Upgraded to quantal on 2012-10-21 (39 days ago)
UserGroups: adm cdrom dialout dip lpadmin netdev plugdev sambashare sudo
XsessionErrors:
 (process:2671): GLib-GIO-WARNING **: Received property menu with type s does not match expected type o in the expected interface
 (process:3906): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed

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