nepomukservicestub crashed with SIGSEGV

Bug #967361 reported by Michael Zywek
34
This bug affects 7 people
Affects Status Importance Assigned to Milestone
kde-runtime (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

If there had been no bug-notification, I'd rather not noticed the problem. So I cannot give any helpful informations.

lsb_release -rd
Description: Ubuntu precise (development branch)
Release: 12.04
uname -a
Linux mz-vb-kubu 3.3-0.slh.3-aptosid-686 #1 SMP PREEMPT Sat Mar 24 01:06:52 UTC 2012 i686 i686 i386 GNU/Linux
apt-cache policy kde-runtime
kde-runtime:
  Installiert: 4:4.8.1-0ubuntu1
  Kandidat: 4:4.8.1-0ubuntu1
  Versionstabelle:
 *** 4:4.8.1-0ubuntu1 0
        500 http://de.archive.ubuntu.com/ubuntu/ precise/main i386 Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: kde-runtime 4:4.8.1-0ubuntu1
Uname: Linux 3.3-0.slh.3-aptosid-686 i686
ApportVersion: 1.95-0ubuntu1
Architecture: i386
Date: Wed Mar 28 18:07:28 2012
Disassembly: => 0x0: Cannot access memory at address 0x0
ExecutablePath: /usr/bin/nepomukservicestub
InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120325)
ProcCmdline: /usr/bin/nepomukservicestub nepomukstorage
ProcEnviron:
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: kde-runtime
Stacktrace:
 #0 0x00000000 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0xbfd0e66c
StacktraceTop: ?? ()
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
Michael Zywek (mzpc) wrote :
visibility: private → public
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in kde-runtime (Ubuntu):
status: New → Confirmed
Revision history for this message
Apport retracing service (apport) wrote :

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

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in kde-runtime (Ubuntu):
status: Confirmed → 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:

perl version 5.14.2-9 required, but 5.14.2-6ubuntu2 is available
perl-base version 5.14.2-9 required, but 5.14.2-6ubuntu2 is available
perl-modules version 5.14.2-9 required, but 5.14.2-6ubuntu2 is available

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.