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

Bug #1158433 reported by Andy Choens
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nepomuk-core (Ubuntu)
New
Medium
Unassigned

Bug Description

nepomukserver crashes during log in. It is connected to an akonadi instance that has a connection to GMail, Google Calendar and Google Contacts. I'm not sure if this is part of the problem or not.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: nepomuk-core 4:4.10.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-13.23-generic 3.8.3
Uname: Linux 3.8.0-13-generic x86_64
ApportVersion: 2.9.2-0ubuntu2
Architecture: amd64
Date: Thu Mar 21 13:52:56 2013
ExecutablePath: /usr/bin/nepomukserver
InstallationDate: Installed on 2011-12-05 (471 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
MarkForUpload: True
ProcCmdline: /usr/bin/nepomukserver
SegvAnalysis:
 Segfault happened at: 0x7f30f3a478cc <_ZN9QHashData14detach_helper2EPFvPNS_4NodeEPvEPFvS1_Eii+236>: mov (%rax,%rdx,8),%rbx
 PC (0x7f30f3a478cc) ok
 source "(%rax,%rdx,8)" (0x00000000) 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 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
 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
 __run_exit_handlers (status=0, listp=0x7f30f4fc96a8 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true) at exit.c:77
Title: nepomukserver crashed with SIGSEGV in pthread_cond_wait@@GLIBC_2.3.2()
UpgradeStatus: Upgraded to raring on 2013-03-17 (3 days ago)
UserGroups: adm admin cdrom debian-tor dialout lpadmin plugdev sambashare

Revision history for this message
Andy Choens (andy-choens) 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:185
 wait (time=18446744073709551615, this=0xd1d400) at thread/qwaitcondition_unix.cpp:86
 QWaitCondition::wait (this=<optimized out>, mutex=0xd1d5c8, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:158
 QThread::wait (this=<optimized out>, time=18446744073709551615) at thread/qthread_unix.cpp:691
 QProcessManager::~QProcessManager (this=0x7f30f3e86540 <processManager()::processManager>, __in_chrg=<optimized out>) at io/qprocess_unix.cpp:212

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
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.