nepomukservicestub crashed with SIGSEGV

Bug #528841 reported by Ron Rhodes
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kdebase-runtime (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: kdebase-runtime

Kubuntu 10.04
4:4.4.0-0ubuntu3
Update to complete
Crash reported but update completed

ProblemType: Crash
Architecture: i386
Date: Wed Feb 24 10:28:23 2010
Disassembly: 0x0: Cannot access memory at address 0x0
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/nepomukservicestub
NonfreeKernelModules: nvidia
Package: kdebase-runtime 4:4.4.0-0ubuntu3
ProcCmdline: /usr/bin/nepomukservicestub nepomukstorage
ProcEnviron:
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
 LANGUAGE=
ProcVersionSignature: Ubuntu 2.6.32-14.20-generic
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: kdebase-runtime
Stacktrace:
 #0 0x00000000 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0xb5d9ffbc
StacktraceTop: ?? ()
Title: nepomukservicestub crashed with SIGSEGV
Uname: Linux 2.6.32-14-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors: (process:1466): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

Revision history for this message
Ron Rhodes (owdronrhodes) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

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

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
tags: added: apport-failed-retrace
tags: removed: need-i386-retrace
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Unfortunately the auto-submitted crash log was too damaged to be of any use. Thanks all the same for your bug report.

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.