nepomukservicestub crashed with SIGSEGV

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

Bug Description

crash after login

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: kde-runtime 4:4.8.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-12.21-generic 3.2.2
Uname: Linux 3.2.0-12-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
Date: Fri Feb 3 15:13:24 2012
Disassembly: => 0x0: Cannot access memory at address 0x0
ExecutablePath: /usr/bin/nepomukservicestub
InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120201.1)
ProcCmdline: /usr/bin/nepomukservicestub nepomukstorage
ProcEnviron:
 LANG=en_US.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 0x0000000000000000 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x7ffff5714a68
StacktraceTop: ?? ()
ThreadStacktrace:
 .
 Thread 3 (LWP 1809):
 #0 0x00007fae8f737893 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x7fae7d48ec60
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
Tony Themelis (tony-athemelis) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

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

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