nepomukservicestub crashed with SIGSEGV in Soprano::Error::ErrorCache::clearError()

Bug #506534 reported by Jonathan Thomas
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
kdebase-runtime (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: kdebase-runtime

Posting here to get a backtrace. Will forward upstream/close here after apport retraces. (Unfortunately it looks like nepomukservicestub doesn't use KDE's crash handler.)

ProblemType: Crash
Architecture: i386
Date: Tue Jan 12 12:26:23 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/nepomukservicestub
InstallationMedia: Kubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
Package: kdebase-runtime 4:4.3.90-0ubuntu2
ProcCmdline: /usr/bin/nepomukservicestub nepomukstorage
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-10.14-generic-pae
SegvAnalysis:
 Segfault happened at: 0xb61cc87d: mov (%edx),%ecx
 PC (0xb61cc87d) ok
 source "(%edx)" (0x007b0020) not located in a known VMA region (needed readable region)!
 destination "%ecx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: kdebase-runtime
StacktraceTop:
 ?? () from /usr/lib/libsoprano.so.4
 Soprano::Error::ErrorCache::clearError() const ()
 Soprano::Error::ErrorCache::setError(Soprano::Error::Error const&) const () from /usr/lib/libsoprano.so.4
 Soprano::FilterModel::executeQuery(QString const&, Soprano::Query::QueryLanguage, QString const&) const () from /usr/lib/libsoprano.so.4
 Soprano::NRLModel::executeQuery(QString const&, Soprano::Query::QueryLanguage, QString const&) const () from /usr/lib/libsoprano.so.4
Tags: lucid
Title: nepomukservicestub crashed with SIGSEGV in Soprano::Error::ErrorCache::clearError()
Uname: Linux 2.6.32-10-generic-pae i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Jonathan Thomas (echidnaman) wrote :
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Guess it won't retrace... :/

Changed in kdebase-runtime (Ubuntu):
status: New → Invalid
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.