strigidaemon fails to start

i can confirm this bug, same environment, same output

i tried to do what Sebastian Trüg (nepomuk boss) suggested here=http://lists.kde.org/?l=kde-devel&m=121665945516434&w=4

stop nepomukserver and run another instance to get output.

Here's what i got:

$ nepomukserver 2> nepomuk.out
$ cat nepomuk.out
NepomukServer(10801) Nepomuk::ServiceManager::Private::startService: Queueing "nepomukontologyloader" due to dependency "nepomukstorage"
NepomukServer(10801) Nepomuk::ServiceController::start: Attaching to already running service "nepomukstorage"
NepomukServer(10801) Nepomuk::ServiceController::slotServiceInitialized: Service "nepomukstorage" initialized
NepomukServer(10801) Nepomuk::ServiceManager::Private::_k_serviceInitialized: Service initialized: "nepomukstorage"
NepomukServer(10801) Nepomuk::ServiceController::start: Attaching to already running service "nepomukontologyloader"
NepomukServer(10801) Nepomuk::ServiceController::slotServiceInitialized: Service "nepomukontologyloader" initialized
NepomukServer(10801) Nepomuk::ServiceManager::Private::_k_serviceInitialized: Service initialized: "nepomukontologyloader"
NepomukServer(10801) Nepomuk::ServiceController::start: Attaching to already running service "nepomukqueryservice"
NepomukServer(10801) Nepomuk::ServiceController::slotServiceInitialized: Service "nepomukqueryservice" initialized
NepomukServer(10801) Nepomuk::ServiceManager::Private::_k_serviceInitialized: Service initialized: "nepomukqueryservice"
NepomukServer(10801) Nepomuk::ServiceController::start: Attaching to already running service "nepomukfilewatch"
NepomukServer(10801) Nepomuk::ServiceController::slotServiceInitialized: Service "nepomukfilewatch" initialized
NepomukServer(10801) Nepomuk::ServiceManager::Private::_k_serviceInitialized: Service initialized: "nepomukfilewatch"
(Soprano::PluginManager) loading all plugins
(Soprano::PluginManager) searching plugin file from "/usr/share/soprano/plugins"
(Soprano::PluginManager) found plugin file "/usr/share/soprano/plugins/nquadparser.desktop"
(Soprano::PluginManager) plugin has proper version.
(Soprano::PluginManager) found parser plugin "nquadparser"
(Soprano::PluginManager) found plugin file "/usr/share/soprano/plugins/nquadserializer.desktop"
(Soprano::PluginManager) plugin has proper version.
(Soprano::PluginManager) found serial...

I also have this bug with same environment.

Same to me KDE 4.2 RC, Kubuntu 8.10 on x86 machine
It doesn't matter if I checkbox in systemsettings in "Desktop Search" module under "Enable Strigi Desktop File Indexer"
I always get:
WARNING: field 'http://strigi.sf.net/ontologies/0.9#debugParseError' is not defined in any rdfs ontology database.
ASSERT: "d" in file /build/buildd/kde4libs-4.1.96/kdecore/kernel/kcomponentdata.cpp, line 191
Aborted

I get the same masseage also and no strigi. I upgraded Kubuntu 8.10 to KDE4.1.2, KDE4.2 beta 2, and KDE4.2 RC. Using the kubuntu-experimental repo.

Same here.

Got the same error, fedora 10, kde4.2 rc. strigidaemon does not start up on login either. i have to start it manually, AND EVEN SO, the error message in systemsettings remains.

After upgrading to kde 4.2 the problem still persists.

I've discovered the problem. Strigi and nepomuk require the Sesame backend to work and the kubuntu packagers refuse to package it because it requires "sort-of unfree" binary packages.

It's a crap!

Further to my last comment. Soprano seems to be the package that has some proprietary code - and this is the one that they don't compile with the needed support.

Are you sure that is the cause of this error? Strigi never required soprano. Nepomuk needs the soprano sesame2 backend, but strigi should work regardless. This is a crash anyway, and not strigidaemon refusing to run.

Oh, the initial report is about a crash, but from the 2nd comment on people have been discussing a different issue.

same problem here.

Related - bug #237336

You will get the strigi working when you install Sun's Java 6 version. The Strigi needs Java to work.

Maybe it's also necessary to change backend from redland to sesame2 in ~/.kde/share/config/nepomukservicerc

I have made a mistake in my previous message: the correct file to edit is ~/.kde/share/config/nepomukserverrc

The same for me at Kubuntu 9.04: "Strigi service failed to initialize, most likely due to an installation problem".

To enable sesame2, you may need to help it find the Sun java libraries. You can check if sesame2 works by running sopranocmd: it lists the available backends. Add the line

/usr/lib/jvm/java-6-sun/jre/lib/i386/server

to /etc/ld.so.conf and run 'sudo ldconfig'. After that sesame2 should be listed in addition to redland. Now you can edit ~/.kde/share/config/nepomukserverrc as jiveaxe suggests.

I read somewhere that if you use openjdk, installing the whole sdk package may help to get sesame working.

Thanks Tuukka Verho, your solution works perfectly. How will this be fixed?

I would also like to thank Tuukka Verho, everything seems to be working fine now. The only difference I had was to change /usr/lib/jvm/java-6-sun/jre/lib/i386/server TO /usr/lib/jvm/java-6-sun/jre/lib/amd64/server

I wonder if in the next release this will be configured correctly when installing Kubuntu?
It would be great if they could provide the details of how to correct this error in the help files, rather than just listing an error that is currently used (that is pretty much useless to most users, as most of use didn't know what was missing and how to fix it).

Thanks

On a kubuntu 9.10 amd64 (I know it is an alpha4) I had the same problem.
following #21 comment I fixed the problem
Tnx to all

The same issue is happening in Fedora 11, x86_64. You need to install the soprano-backend-sesame2 source packages, and then fallow the instructions available in comment #20, but adding the line

include /usr/lib/jvm/java/jre/lib/amd64/server/

instead. Anyway, thx for the help and suggestion in this bug report, I have been looking for a solution for over a month.
Thx.

thanks to Tuukka Verho for i386 solution and thanks dtr for amd64 solution.
Now things seam to work.

solution also works for me in Kubuntu 9.10 but wish we did not have to go through this hack route

Any news? Will this be fixed in Kubuntu Karmic?

I have this problem on Jaunty -- tried a few things to fix it, but no luck yet. It seems there's a number of things that will cause Strigi to fail.

Confirmed #19 works for me on Karmic. 32bit

Changed:
* updated ~/.kde/share/config/nepomukserverrc to say sesame2 instead of redland
* sudo vim /etc/ld.so.conf.d/strigi-jdk.conf
* contents:

# from https://bugs.launchpad.net/ubuntu/+source/strigi/+bug/309626
/usr/lib/jvm/java-6-sun/jre/lib/i386/server

sopranocmd doesn't show errors. Enabling Strigi in System Settings -> Advanced -> Desktop Search now works and strigi starts indexing.

make sure you have "openjdk-6-jdk" installed.

Would be nice if this worked from packages rather than futzing around on the command line.

PS. You don't have to use vim ;)