nepomukservicestub crashed with SIGSEGV in QMutex::lock()

[Jure Koren]

I believe it happened at normal shutdown, but I'm not completely certain.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: kde-runtime 4:4.8.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9
Uname: Linux 3.2.0-18-generic x86_64
ApportVersion: 1.94.1-0ubuntu1
Architecture: amd64
Date: Wed Mar 7 19:58:19 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/nepomukservicestub
InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
ProcCmdline: /usr/bin/nepomukservicestub nepomukqueryservice
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
 LANGUAGE=
SegvAnalysis:
 Segfault happened at: 0x7fdbc7cb7931 <_ZN6QMutex4lockEv+17>: testb $0x1,0x4(%rbx)
 PC (0x7fdbc7cb7931) ok
 source "$0x1" ok
 destination "0x4(%rbx)" (0x100000004) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: kde-runtime
StacktraceTop:
 QMutex::lock() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
 ?? () from /usr/lib/libsopranoclient.so.1
 ?? () from /usr/lib/libsopranoclient.so.1
 QThreadStorageData::set(void*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
 ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
Title: nepomukservicestub crashed with SIGSEGV in QMutex::lock()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:
 QMutex::lock (this=0x8090b8) at thread/qmutex.cpp:153
 lockInline (this=0x8090b8) at /usr/include/qt4/QtCore/qmutex.h:198
 QMutexLocker (m=0x8090b8, this=<synthetic pointer>) at /usr/include/qt4/QtCore/qmutex.h:109
 Soprano::Client::SocketHandler::~SocketHandler (this=0x6ec150, __in_chrg=<optimized out>) at ../../client/clientconnection.cpp:58
 Soprano::Client::SocketHandler::~SocketHandler (this=0x6ec150, __in_chrg=<optimized out>) at ../../client/clientconnection.cpp:61

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.