nepomukservicestub crashed with SIGSEGV in QObject::~QObject()
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
ProcVersionSign
Uname: Linux 3.2.0-23-
NonfreeKernelMo
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/
InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120328)
ProcCmdline: /usr/bin/
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:
_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
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.