nepomukservicestub crashed with SIGSEGV

Bug #947870 reported by Tim Richardson
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kde-runtime (Ubuntu)
New
Undecided
Unassigned

Bug Description

I don't know what happened, I just found myself reporting this bug ... 12.04 kubuntu beta

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: kde-runtime 4:4.8.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-18.28-generic-pae 3.2.9
Uname: Linux 3.2.0-18-generic-pae i686
ApportVersion: 1.94-0ubuntu1
Architecture: i386
Date: Tue Mar 6 14:19:24 2012
Disassembly: => 0x0: Cannot access memory at address 0x0
ExecutablePath: /usr/bin/nepomukservicestub
InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120228.1)
ProcCmdline: /usr/bin/nepomukservicestub nepomukstorage
ProcEnviron:
 LANGUAGE=en_AU:en
 LANG=en_AU.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
Stacktrace:
 #0 0x00000000 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0xbfdce68c
StacktraceTop: ?? ()
ThreadStacktrace:
 .
 Thread 3 (LWP 1555):
 #0 0xb77aa424 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0xb1d1e090
Title: nepomukservicestub crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Tim Richardson (tim-richardson) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

Stacktrace:
 #0 0x00000000 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0xbfdce68c
StacktraceTop: ?? ()

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
tags: added: apport-failed-retrace
tags: removed: need-i386-retrace
visibility: private → public
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.