strigidaemon doesn't start when "Nepomuk Semantic Desktop" is enabled in KDE4.1Beta1

Does the PPA archive include a more up-to-date version of Strigi, or some parts of Strigi?

I can confirm this bug with PPA packages.

The following works for me:

1) Create the above link:
ln -s /usr/lib/kde4/lib/strigi/strigiindex_sopranobackend.so /usr/lib/strigi/strigiindex_sopranobackend.so
2) kill all nepomuk and strigi processes:
pgrep nepomuk|xargs kill -9
pgrep strigi|xargs kill -9
3) remove the ~/.strigi folder
4) restart nepomukserver

It doesn't help here, I get the same results as written above.

I've encountered another problem:

If I delete ~/.strigi and start the daemon, strigi indexes and I can query it by strigiclient or strigicmd. When I then enable strigi desktop search in the KDE4-Settings, the strigidaemon crashes.

I was able to start the nepomuk daemon but the nepomuk process is taking a 100% of one of my CPU to index my home which does not contains a huge quantity of file.
A quick look in kde bug tracker show that the backend is not the good one (http://bugs.kde.org/show_bug.cgi?id=161380) : we use redland instead of sesame2 (sopranocmd --help does not contain sesame2). So maybe we miss some compilation options here.

I can confirm that what Yannig has said is correct. It seems that the Ubuntu packages for strigi have not been compiled with 'sesame2' support. This is a far quicker indexer for KDE4 than 'redland'.

Running strigidaemon from command line it uses clucene backend ( look ~/.strigi/daemon.conf ).
When called by nepomuk it tries to use sopranobackend and crashes.

I can confirm this bug for the 4.1 release PPA.

The last update of strigi is correcting the problem but you need to delete ~/.strigi. If you don't do this, you will receive this message :
yannig@yannig-desktop:/usr/lib/kde4/lib$ strigidaemon
WARNING: field 'http://strigi.sf.net/ontologies/0.9#debugParseError' is not defined in any rdfs ontology database.
Unknown backend type: sopranobackend

yannig@yannig-desktop:/usr/lib/kde4/lib$ rm /home/yannig/.strigi/ -rf
yannig@yannig-desktop:/usr/lib/kde4/lib$ strigidaemon
DaemonConfigurator: created default config for indexed dirs
WARNING: field 'http://strigi.sf.net/ontologies/0.9#debugParseError' is not defined in any rdfs ontology database.
stop
DBusHandler::stop
stop
DBusHandler::stop
stopping

Then the index start and I get a fully fonctionnal index of my documents (see screenshot).

I can confirm the original bug reported by Thomas.

The way Luis Silva describes doesn't work for me.

Yes, setting the links as described in my initial posting works here now, too. I've installed KDE4 on FreeBSD the last days and found out, that the problem exists there, too and I was able to solve it on the same way, so it may be an upstream problem. Anyway, it seems, that there will be another solution soon: http://www.kdedevelopers.org/node/3573 .

Not going to be fixed for hardy because:
a) Strigi-daemon is not installed by default
b) Nepomuk doesn't use it by default
c) there is no reasonable GUI
d) the one that is existing is not very usable and off by default

Maintaining a solution would be too much work considering these facts. It works properly in Intrepid/8.10.

With KDE 4.2 packages (deb http://ppa.launchpad.net/kubuntu-experimental/ubuntu intrepid main), using intrepid, this still does not work for me.

After killing all nepomuk processes and removing ~/.strigi, then restarting nepomukserver, I get this message on the systemsettings configuration page, under 'Enable Strigi Desktop File Indexer'

Failed to contact Strigi Indexer (No such method 'currentFolder' in interface 'org.kde..nepomuk.Strigi' at object path '/nepomukstrigiservice' (signature ''))

I'm still getting this basic problem with Jaunty. The error message has changed now - instead it flashes up this:

Failed to contact Strigi indexer (Could not get owner of name 'org.kde.nepomuk.services.nepomukstrigiservice': no such name)

...before returning to "Strigi service not running"

I do have soprano-backend-sesame installed.

In my ~/.xsession-errors I've found:

[/usr/bin/nepomukservicestub] nepomukstrigiservice(6705) Nepomuk::StrigiService::StrigiService: Will not start when using redland Soprano backend due to horrible performance.

And in/home/luke/.kde/share/config/nepomukserverrc I found this line:

Used Soprano Backend=redland

However, I never put that there, I don't know why it's there, and the GUI should sort this out. If I manually change it or remove it, then restart nepomukserver in a terminal, the output includes this:

(Soprano::PluginManager) loaded plugin from "/usr/lib/soprano/libsoprano_redlandbackend.so"
(Soprano::PluginManager) found no soprano plugin at "/usr/lib/soprano/libsoprano_sesame2backend.so"
(Soprano::PluginManager) found no soprano plugin at "/usr/lib/soprano/libsoprano_sesame2backend.so"

However, that file does exist:

$ ls -1 /usr/lib/soprano/
libsoprano_nquadparser.so
libsoprano_nquadserializer.so
libsoprano_raptorparser.so
libsoprano_raptorserializer.so
libsoprano_redlandbackend.so
libsoprano_sesame2backend.so

Also, after restarting, nepomukserverrc has "Used Soprano Backend=redland" again.

I re-opened the bug since the reason for the WONTFIX was that it was fixed in Intrepid (though it never was for me, and is still present in Jaunty).

I've got the same error message in Jaunty when I try to start Strigi. I also have the problem with Nepomuk interminably maxing out one CPU core. This is a real shame -- I remember using strigi back before KDE4 and it was nice. It's been no dice ever since.

Same bug in Kubuntu 64bit 9.04
first I had this problem
https://bugs.launchpad.net/ubuntu/+source/soprano-backend-sesame/+bug/334186
that is a missing symlink from
libjvm.so
to
/usr/lib/jvm/java-6-openjdk/jre/lib/amd64/server/libjvm.so

i solved the bug strigi is always inactive
in addiction to all the reports sended here i must say that in dmesg there are these lines

[ 184.199693] nepomukservices[3292]: segfault at 48 ip 00007f0d7938bcfe sp 00007fff8198ebf0 error 4 in libQtCore.so.4.5.0[7f0d79322000+240000]
[ 895.034598] nepomukservices[3738]: segfault at 48 ip 00007f9b51320cfe sp 00007fff59922c80 error 4 in libQtCore.so.4.5.0[7f9b512b7000+240000]

Thanks, that fixed it for me, though I had to use:

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

The proper method of creating these symlinks needs to be sorted out, I imagine - it seems to depend on what java packages you have installed.

I'm changing the status to 'New', because the reason for WONTFIX was not correct - the bug is still definitely present in Jaunty.

Luke,

the problem you are referring to has a dedicated bug report: https://bugs.launchpad.net/ubuntu/+source/soprano-backend-sesame/+bug/334186.

nulll,
could you please confirm that the segfaults still occur? I saw them on my system as well but they disappeared once I had symlinked libjvm.so.

@Niels Ganser
now if i
dmesg | grep nepomukservices
is empty

so maybe that was linked with the libjvm.so problem
but strigi is always inactive, if i try to turn it on i get the error
"Could not get owner of name 'org.kde.nepomuk.services.nepomukstrigiservice': no such name"

nulll,

presumably you have the same problam as other's reporting the same error: namely nepomuk falsely tries to use the redland storage backend instead of sesame. Could you please attach your ~/.xsession-errors, if present?

I am stabbing in the dark a little here but try the following to make strigi work for you:
sudo aptitude reinstall soprano-backend-sesame && sudo dpkg-reconfigure soprano-backend-sesame

If this does not help, please also paste the output of
cat .kde/share/config/nepomukserverrc

Thank you!

hi Niels,
after this
sudo aptitude reinstall soprano-backend-sesame && sudo dpkg-reconfigure soprano-backend-sesame
the problem is still there

in attached you can see my .xsession-errors
and here's my .kde/share/config/nepomukserverrc

[Basic Settings]
Configured repositories=main
Start Nepomuk=true

[Service-nepomukmigration1]
autostart=false

[Service-nepomukstrigiservice]
autostart=true

[main Settings]
Storage Dir[$e]=$HOME/.kde/share/apps/nepomuk/repository/main/
Used Soprano Backend=sesame2
rebuilt index for type indexing=true

A lot of time (months!) are passed but the problem is still there... why?

Hi Niels, as you asked me again in attached you have my last xsession-errors

and again this is the
.kde/share/config/nepomukserverrc

[Basic Settings]
Configured repositories=main
Start Nepomuk=true

[Service-nepomukmigration1]
autostart=false

[Service-nepomukstrigiservice]
autostart=true

[main Settings]
Storage Dir[$e]=$HOME/.kde/share/apps/nepomuk/repository/main/
Used Soprano Backend=sesame2
rebuilt index for type indexing=true

and I reconfirm that after doing
sudo aptitude reinstall soprano-backend-sesame && sudo dpkg-reconfigure soprano-backend-sesame
the problem is still there

See the solution here:

https://bugs.launchpad.net/ubuntu/+source/strigi/+bug/309626

comments 19.

thanks so much humufr!
yes the instructions in the link solved the problem

This bug should be closed since the new backend is virtuoso.