nepomukserver crashed with SIGSEGV in pthread_cond_wait@@GLIBC_2.3.2()

Bug #955076 reported by claudio
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kde-runtime (Ubuntu)
New
Undecided
Unassigned

Bug Description

open kubuntu

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
NonfreeKernelModules: nvidia
ApportVersion: 1.94.1-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Wed Mar 14 14:16:22 2012
ExecutablePath: /usr/bin/nepomukserver
InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120224)
ProcCmdline: /usr/bin/nepomukserver
ProcEnviron:
 LANGUAGE=it_IT
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f826ad99bd3 <_ZN9QHashData14detach_helper2EPFvPNS_4NodeEPvEPFvS1_Eii+227>: mov (%rax,%rdx,8),%rbx
 PC (0x7f826ad99bd3) ok
 source "(%rax,%rdx,8)" (0x000007d1) not located in a known VMA region (needed readable region)!
 destination "%rbx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: kde-runtime
StacktraceTop:
 pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0
 QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
 QThread::wait(unsigned long) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
 ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
Title: nepomukserver crashed with SIGSEGV in pthread_cond_wait@@GLIBC_2.3.2()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
claudio (claucurc) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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 #946115, 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.

visibility: private → public
visibility: private → public
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.