[Precise] nepomukservicestub crashed with SIGSEGV in pthread_cond_wait@@GLIBC_2.3.2()

[Scott Testerman]

This is the first time I've seen this particular crash. I was notified about it upon a cold boot of my laptop, an Acer 7552G.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: kde-runtime 4:4.8.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9
Uname: Linux 3.2.0-18-generic x86_64
ApportVersion: 1.94.1-0ubuntu2
Architecture: amd64
Date: Wed Mar 14 02:07:02 2012
Disassembly: => 0x0: Cannot access memory at address 0x0
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/nepomukservicestub
InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120228.1)
ProcCmdline: /usr/bin/nepomukservicestub nepomukfilewatch
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() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
 QObject::~QObject() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
 _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)]

StacktraceTop:
 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
 wait (time=18446744073709551615, this=0x20caa80) at thread/qwaitcondition_unix.cpp:86
 QWaitCondition::wait (this=<optimized out>, mutex=0x20cc688, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:158
 QThread::wait (this=<optimized out>, time=18446744073709551615) at thread/qthread_unix.cpp:651
 Nepomuk::FileWatch::~FileWatch (this=0x2067310, __in_chrg=<optimized out>) at ../../../../nepomuk/services/filewatch/nepomukfilewatch.cpp:189

[Launchpad Janitor (janitor)]

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

[ajw107 (alex-wood-bcs)]

I had this bug (although the crash was from a an object rather than a wait timeout thread) upon a reboot of my system following a apt-get upgrade

[Scott Testerman (scott-testerman)]

I've experienced this again, this time caused by a crash of VLC due to a known issue with fglrx. I can also reproduce the crash with Dragon Player, also using fglrx. On crashing, the system immediately returns to the login screen (again, known issue) and this error is reported upon logging in again.

[leprovost (leprovost-philippe)]

com!puter need to reboot each time I use a any video player