nepomukservicestub crashed with SIGSEGV

Bug #1016107 reported by Xavier Besnard
34
This bug affects 7 people
Affects Status Importance Assigned to Milestone
nepomuk-core (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Configuration: ACER netbook d531h with Kubuntu 12.10 Quantal alpha 1, updated dayly. Includes KDE 4.8.9

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: nepomuk-core 4:4.8.90-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-1.1-generic 3.5.0-rc3
Uname: Linux 3.5.0-1-generic i686
ApportVersion: 2.2.4-0ubuntu1
Architecture: i386
Date: Thu Jun 21 12:54:29 2012
Disassembly: => 0x0: Cannot access memory at address 0x0
ExecutablePath: /usr/bin/nepomukservicestub
InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120530)
ProcCmdline: /usr/bin/nepomukservicestub nepomukstorage
ProcEnviron:
 LANGUAGE=fr_FR
 LANG=fr_FR.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: nepomuk-core
Stacktrace:
 #0 0x00000000 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0xbf84c7ec
StacktraceTop: ?? ()
ThreadStacktrace:
 .
 Thread 13 (LWP 1835):
 #0 0xb7788424 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0xadcfa070
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
Xavier Besnard (xavier-besnard) 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 0xbf84c7ec
StacktraceTop: ?? ()
ThreadStacktrace:
 .
 Thread 13 (LWP 1835):
 #0 0xb7788424 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0xadcfa070

Changed in nepomuk-core (Ubuntu):
status: New → Invalid
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

debconf version 1.5.43ubuntu1 required, but 1.5.44ubuntu1 is available
procps version 1:3.3.3-2ubuntu1 required, but 1:3.3.3-2ubuntu2 is available
outdated debug symbol package for procps: package version 1:3.3.3-2ubuntu2 dbgsym version 1:3.3.3-2ubuntu1
libprocps0 version 1:3.3.3-2ubuntu1 required, but 1:3.3.3-2ubuntu2 is available
outdated debug symbol package for libprocps0: package version 1:3.3.3-2ubuntu2 dbgsym version 1:3.3.3-2ubuntu1
outdated debug symbol package for module-init-tools: package version 3.16-1ubuntu3 dbgsym version 3.16-1ubuntu2
outdated debug symbol package for kde-style-oxygen: package version 4:4.8.90-0ubuntu2 dbgsym version 4:4.8.3-0ubuntu0.2
outdated debug symbol package for kde-workspace-bin: package version 4:4.8.90-0ubuntu2 dbgsym version 4:4.8.3-0ubuntu0.2

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

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.