Ubuntu
kde-runtime package

nepomukservicestub crashed with SIGSEGV in QObject::~QObject()

Bug #960078 reported by whitedragon75 on 2012-03-20

This bug report is a duplicate of: Bug #913024: nepomukservicestub crashed with SIGSEGV in pthread_cond_wait@@GLIBC_2.3.2(). Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	kde-runtime (Ubuntu)	New	Undecided	Unassigned

Bug Description

Description: Ubuntu precise (development branch)
Release: 12.04

kde-runtime:
  Installato: 4:4.8.1-0ubuntu1
  Candidato: 4:4.8.1-0ubuntu1
  Tabella versione:
*** 4:4.8.1-0ubuntu1 0
        500 http://archive.ubuntu.com/ubuntu/ precise/main i386 Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: kde-runtime 4:4.8.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-19.30-generic 3.2.11
Uname: Linux 3.2.0-19-generic i686
ApportVersion: 1.94.1-0ubuntu2
Architecture: i386
CrashCounter: 1
Date: Tue Mar 20 08:48:35 2012
Disassembly: => 0x0: Cannot access memory at address 0x0
ExecutablePath: /usr/bin/nepomukservicestub
InstallationMedia: Kubuntu 10.10 "Maverick Meerkat" - Release i386 (20101008)
ProcCmdline: /usr/bin/nepomukservicestub nepomukfilewatch
ProcEnviron:
PATH=(custom, no user)
LANG=it_IT.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x0: Cannot access memory at address 0x0
PC (0x00000000) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: kde-runtime
StacktraceTop:
?? ()
QObject::~QObject() () from /usr/lib/i386-linux-gnu/libQtCore.so.4
QObject::~QObject() () from /usr/lib/i386-linux-gnu/libQtCore.so.4
_start ()
Title: nepomukservicestub crashed with SIGSEGV in QObject::~QObject()
UpgradeStatus: Upgraded to precise on 2012-03-08 (11 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Tags:

Revision history for this message

whitedragon75 (francesco-gatti75) wrote on 2012-03-20:

Dependencies.txt Edit (7.7 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2012-03-20: 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 #913024, 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.