nepomukservicestub crashed with SIGSEGV

Bug #545277 reported by Rohan Garg
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

On an initial login to kubuntu lucid lynx,nepomuk crashes everytime,this bug might be a duplicate of https://bugs.launchpad.net/bugs/545067 but im unsure since that bug occurred when i had been working for about half an hour and this one occurs just after logging in.

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Tue Mar 23 23:22:02 2010
Disassembly: => 0x7f3b4fedccff: Cannot access memory at address 0x7f3b4fedccff
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/nepomukservicestub
InstallationMedia: Kubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100317)
NonfreeKernelModules: nvidia
Package: kdebase-runtime 4:4.4.1-0ubuntu3
ProcCmdline: /usr/bin/nepomukservicestub nepomukfilewatch
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
 LANGUAGE=
ProcVersionSignature: Ubuntu 2.6.32-16.25-generic
SegvAnalysis:
 Segfault happened at: 0x7f3b4fedccff: Cannot access memory at address 0x7f3b4fedccff
 PC (0x7f3b4fedccff) ok
 SP (0x7fffa6b2bdf8) ok
 Reason could not be automatically determined.
Signal: 11
SourcePackage: kdebase-runtime
Stacktrace:
 #0 0x00007f3b4fedccff in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x7fffa6b2bdf8
StacktraceTop: ?? ()
Title: nepomukservicestub crashed with SIGSEGV
Uname: Linux 2.6.32-16-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (process:1617): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (npviewer.bin:1820): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libqtcurve.so: wrong ELF class: ELFCLASS64

Revision history for this message
Rohan Garg (rohangarg) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

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

Changed in kdebase-runtime (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 an useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

libk5crypto3: installed version 1.8+dfsg~alpha1-7, latest version: 1.8+dfsg~alpha1-7ubuntu1
libudev0: installed version 151-5, latest version: 151-6
libglib2.0-0: installed version 2.23.5-1ubuntu3, latest version: 2.23.6-1ubuntu2
libsoprano4: installed version 2.4.0.1+dfsg.1-0ubuntu4, latest version: 2.4.1+dfsg.1-1ubuntu1
soprano-daemon: installed version 2.4.0.1+dfsg.1-0ubuntu4, latest version: 2.4.1+dfsg.1-1ubuntu1
libgssapi-krb5-2: installed version 1.8+dfsg~alpha1-7, latest version: 1.8+dfsg~alpha1-7ubuntu1
shared-desktop-ontologies: installed version 0.2.0-1, latest version: 0.3-1
udev: installed version 151-5, latest version: 151-6
libaspell15: installed version 0.60.6-3, latest version: 0.60.6-3ubuntu1
libkrb5-3: installed version 1.8+dfsg~alpha1-7, latest version: 1.8+dfsg~alpha1-7ubuntu1
libkrb5support0: installed version 1.8+dfsg~alpha1-7, latest version: 1.8+dfsg~alpha1-7ubuntu1

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-amd64-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.