nepomuk strigi desktop indexer fails to initialize

Bug #479021 reported by juulpasgaard
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kdebase-runtime (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: kdebase-runtime

My nepomuk strigi desktop indexer failed to start with the following message:

service failed to initialize, most likely due to an installation problem

When I then disabled the indexer, I got the following message:

The name org.kde.nepomuk.services.nepomukstrigiservice was not provided by any .service

According to http://aldeby.org/blog/index.php/nepomuck-and-stringi-kubuntu-910-strigi-service-failed-to-initialize.html
this is due to a missing symbolic link. The instructions found there are as follows:
"If you use the free and libre OpenJDK (32 bit)

 sudo ln -s /usr/lib/jvm/java-6-openjdk/jre/lib/i386/server/libjvm.so /usr/lib/libjvm.so

(64 bit)

sudo ln -s /usr/lib/jvm/java-6-openjdk/jre/lib/amd64/server/libjvm.so /usr/lib/libjvm.so

If you use Sun Java 6 type: (32bit)

sudo ln -s /usr/lib/jvm/java-6-sun/jre/lib/i386/server/libjvm.so /usr/lib/libjvm.so

(64bit)

sudo ln -s /usr/lib/jvm/java-6-sun/jre/lib/amd64/server/libjvm.so /usr/lib/libjvm.so

"

Once I tried the above fix, the nepomuk strigi desktop indexer successfully initialized.

According to http://forum.kde.org/viewtopic.php?f=15&t=62458&start=20 :

"That is a fault of your distribution's packages, for not setting up /etc/ld.so.conf correctly, or placing files in one of the directories mentioned in there."

I'm therefore reporting the problem with Ubuntu.

ProblemType: Bug
Architecture: i386
Date: Mon Nov 9 10:37:03 2009
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: nvidia
Package: kdebase-runtime 4:4.3.2-0ubuntu4
ProcEnviron:
 LANGUAGE=
 PATH=(custom, user)
 LANG=en_DK.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: kdebase-runtime
Uname: Linux 2.6.31-14-generic i686
XsessionErrors: (polkit-gnome-authentication-agent-1:2074): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

Revision history for this message
juulpasgaard (bjuulpas) wrote :
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.