nepomukservicestub crashed with SIGSEGV in librdf_world_open()

Bug #320688 reported by Alessandro Ghersi
10
Affects Status Importance Assigned to Milestone
kdebase-runtime (Ubuntu)
Triaged
Medium
Unassigned

Bug Description

Binary package hint: kdebase-runtime

Kubuntu 64bit livecd (daily live 22 January '09) after start kde nepomuk crashed.

ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/nepomukservicestub
Package: kdebase-runtime 4:4.1.96-0ubuntu2
ProcCmdline: /usr/bin/nepomukservicestub nepomukstorage
ProcEnviron:
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
 LANGUAGE=
Signal: 11
SourcePackage: kdebase-runtime
StacktraceTop:
 librdf_world_open () from /usr/lib/librdf.so.0
 librdf_new_hash_datum () from /usr/lib/librdf.so.0
 librdf_hash_get_one () from /usr/lib/librdf.so.0
 librdf_new_uri () from /usr/lib/librdf.so.0
 raptor_namespaces_init ()
Title: nepomukservicestub crashed with SIGSEGV in librdf_world_open()
Uname: Linux 2.6.28-4-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Tags: apport-crash
Revision history for this message
Alessandro Ghersi (alessandro-ghersi) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:librdf_new_hash_datum (world=0x10, data=0x0, size=0)
librdf_hash_get_one (hash=0xb006b0,
librdf_new_uri (world=0xb00440,
raptor_namespaces_init (nstack=0xbac310,
raptor_new_namespaces (uri_handler=0x7f7c2aee2b80,

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in kdebase-runtime:
importance: Undecided → Medium
Connor Imes (ckimes)
Changed in kdebase-runtime:
status: New → Triaged
Revision history for this message
Bruce Miller (brm0423) wrote :

Similar experience with Kubuntu daily live CD i386 20090125

first attempt to start Kubuntu led to pulsating graphics when kdm log-in expected
after rebooting to recovery console and running xfix, system booted but nepomukservicestub crashed

Revision history for this message
Connor Imes (ckimes) wrote :

Bruce, you need to open a new bug report for your problem. If you can get apport to catch the crash, it can auto-generate a report like this one. Otherwise you can try to manually get a backtrace using the directions
here - https://wiki.ubuntu.com/DebuggingProgramCrash
and here - https://wiki.ubuntu.com/Backtrace

Thank you.

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.