Version: (using Devel) OS: Linux Installed from: Compiled sources In System Settings -> Advanced -> Desktop Search, I turn on "Enable Strigi Desktop File Indexer" and hit "Apply". In response, I get the error message (displayed below the check box): "Strigi service failed to initialize, most likely due to an installation problem." This error message is useless to me -- it does not provide any information on what is wrong or how I might go about diagnosing or fixing the problem. Please include more information with this error message.
Reassigning.
Marking as duplicate of bug 186910. Thanks *** This bug has been marked as a duplicate of bug 186910 ***
Sorry, but this is not a duplicate. Bug 186910 (marked as FIXED, which this is not) was concerned with how long the message was being displayed. This bug is concerned with the content of the message itself.
i see the problem. I made the message this cryptic to indicate that this is actually an installation issue, not something a "normal" user would solve. It is rather something for the creator of the packages to solve.
I gathered as much from "this is an installation problem", but just a pointer to a log file or similar would be very helpful. :) I'm building from trunk, and I'm not specifically familiar with Strigi, so I wouldn't even know where to go to begin diagnosing. I'm sure there are others in a similar situation.
well, it is really an installation problem. The strigi plugin cannot be loaded. This either happens if kdebase is not properly installed or if your installation directory is not correct or not in LD_LIBRARY_PATH (in case it is a custom one). AFAIK strigi searches for plugins there, too.
I now added a handbook to the KCM module. It explains the different states the strigi service can be in as well as the error states. Does this solve the problem for you?
Yes, this is somewhat more helpful. It at least gives me a place to start looking. (I'm not sure how Strigi plugins are handled, or anything like that, but now that I know what I need to research, I can start figuring it out for myself.) Given that end users are never supposed to see that error, it seems reasonable -- more information than that probably wouldn't be appropriate for the handbook anyway.
This solves the problem: sudo ln -s /usr/lib/jvm/java-6-sun/jre/lib/i386/server/libjvm.so /usr/lib/libjvm.so
Thanks for the tip Minza, in my case I had to do: sudo ln -s /usr/lib/jvm/java-6-openjdk/jre/lib/amd64/server/libjvm.so /usr/lib/libjvm.so So you need to look for the java vm you are using and your architecture.
This seems fixed.