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

Bug #983500 reported by Marcos Pérez
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kde-runtime (Ubuntu)
New
Undecided
Unassigned

Bug Description

It occured every start session

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: kde-runtime 4:4.8.2-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic-pae 3.2.14
Uname: Linux 3.2.0-23-generic-pae i686
NonfreeKernelModules: nvidia
ApportVersion: 2.0.1-0ubuntu3
Architecture: i386
CrashCounter: 1
Date: Mon Apr 16 23:39:25 2012
Disassembly: => 0x0: No se puede acceder a la memoria en la dirección 0x0
ExecutablePath: /usr/bin/nepomukservicestub
InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120328)
ProcCmdline: /usr/bin/nepomukservicestub nepomukfileindexer
ProcEnviron:
 LANGUAGE=es_ES
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x0: No se puede acceder a la memoria en la dirección 0x0
 PC (0x00000000) not located in a known VMA region (needed executable region)!
 source "0x0" (0x00000000) not located in a known VMA region (needed readable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason:
 executing NULL VMA
 reading 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: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout fax floppy games lpadmin plugdev sambashare scanner sudo syslog users vboxusers

Revision history for this message
Marcos Pérez (chuloyo) wrote :
Revision history for this message
Apport retracing service (apport) wrote : 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 #915934, 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.

visibility: private → public
visibility: private → public
tags: removed: need-i386-retrace
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.