nepomukserver crashed with SIGSEGV in testAndSetOrdered()

Bug #1055980 reported by anagor
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
nepomuk-core (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Showed this crash information on the next login after a recent system update that required reboot.
The file indexer seems to function and the search working however.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: nepomuk-core 4:4.9.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-15.23-generic 3.5.4
Uname: Linux 3.5.0-15-generic x86_64
ApportVersion: 2.5.2-0ubuntu4
Architecture: amd64
Date: Tue Sep 25 04:36:52 2012
ExecutablePath: /usr/bin/nepomukserver
InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120423)
ProcCmdline: /usr/bin/nepomukserver
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f2edc682e04 <QProcess::state() const+4>: mov 0xf4(%rax),%eax
 PC (0x7f2edc682e04) ok
 source "0xf4(%rax)" (0x000000f4) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nepomuk-core
StacktraceTop:
 testAndSetOrdered (newValue=0, expectedValue=1, this=0xf28960) at ../../include/QtCore/../../src/corelib/arch/qatomic_x86_64.h:145
 testAndSetRelease (newValue=0, this=0xf28960, expectedValue=1) at ../../include/QtCore/../../src/corelib/arch/qatomic_x86_64.h:272
 unlockInline (this=0xf28bb0) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:171
 QObject::~QObject (this=0xf27630, __in_chrg=<optimized out>) at kernel/qobject.cpp:922
 ?? () from /usr/lib/kde4/libkdeinit/libkdeinit4_nepomukserver.so
Title: nepomukserver crashed with SIGSEGV in testAndSetOrdered()
UpgradeStatus: Upgraded to quantal on 2012-09-23 (1 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data

Revision history for this message
anagor (anagor) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 testAndSetOrdered (newValue=0, expectedValue=1, this=0xf28960) at ../../include/QtCore/../../src/corelib/arch/qatomic_x86_64.h:145
 testAndSetRelease (newValue=0, this=0xf28960, expectedValue=1) at ../../include/QtCore/../../src/corelib/arch/qatomic_x86_64.h:272
 unlockInline (this=0xf28bb0) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:171
 QObject::~QObject (this=0xf27630, __in_chrg=<optimized out>) at kernel/qobject.cpp:922
 Nepomuk2::ServiceController::~ServiceController (this=0xf27630, __in_chrg=<optimized out>) at ../../server/servicecontroller.cpp:155

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