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

Bug #1060155 reported by Petr Herynk
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
nepomuk-core (Ubuntu)
Medium
Unassigned

Bug Description

After Start of ubuntu.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: nepomuk-core 4:4.9.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4
Uname: Linux 3.5.0-16-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.6.1-0ubuntu1
Architecture: amd64
Date: Tue Oct 2 10:49:51 2012
ExecutablePath: /usr/bin/nepomukserver
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20120930)
ProcCmdline: /usr/bin/nepomukserver
ProcEnviron:
 PATH=(custom, no user)
 LANG=cs_CZ.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f01ea63381c <_ZN9QHashData14detach_helper2EPFvPNS_4NodeEPvEPFvS1_Eii+236>: mov (%rax,%rdx,8),%rbx
 PC (0x7f01ea63381c) ok
 source "(%rax,%rdx,8)" (0x00000040) not located in a known VMA region (needed readable region)!
 destination "%rbx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nepomuk-core
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
Petr Herynk (pherynk) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
 QWaitCondition::wait(QMutex*, unsigned long) () from /tmp/tmp6b2aP8/usr/lib/x86_64-linux-gnu/libQtCore.so.4
 QThread::wait(unsigned long) () from /tmp/tmp6b2aP8/usr/lib/x86_64-linux-gnu/libQtCore.so.4
 ?? () from /tmp/tmp6b2aP8/usr/lib/x86_64-linux-gnu/libQtCore.so.4
 __run_exit_handlers (status=0, listp=0x7f01ebba06a8, run_list_atexit=true) at exit.c:78

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in nepomuk-core (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
information type: Private → Public
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in nepomuk-core (Ubuntu):
status: New → Confirmed
Revision history for this message
Rohan Garg (rohangarg) wrote :

Hi there!

Thanks for reporting this bug! Your bug seems to be a problem with the KDE program itself, and not with our KDE packages. While we appreciate your issue, it would be better if it was tracked at https://bugs.kde.org, so that the KDE developers can deal with this speedily and have direct communication with you as the reporter for more effective debugging.

Thanks!

Changed in nepomuk-core (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers