Hello everybody,

Yesterday I installed KDE SC 4.4 RC1 via kubuntu-beta-ppa. I now run into a number of bugs already being known and worked on, but another one where I could not find any information for and which turns my laptop into a continous room heater and noise producer: strigi is in a kind of an infinite loop.
Scenario is as follows: I installed the virtuoso-backend, had the files converted, activated strigi. From that time on, it would index the files in the given directory rather continuosly. Once it has finished, the daemon goes idle - according to the tray icon - and then, merely ten to fifteen minutes later starts all over again. Which means: He reindexes my whole $HOME - which takes awhile, at least 30 minutes, since my music is in there. And it keeps the CPU high in the meantime. Hitting pause on the tray menu seems to stop the daemon albeit not the CPU usage which stays just as high - over 50% at the very least for nepomukservicestub and virtuoso together, according to htop. While reindexing, there is not the faintest change in database size or number of files indexed. So I don't really see why it is doing that. Any hint in which log I can take a look at or at least if this bug is known or an error in some of my configs?

Thanks a lot!

Can you please check the logs which are likely in ~/.xsession-errors to see if Strigi is crashing or Nepomuk is having issues writing to its database?

There seems nothing indicating a crash or write failure whatsoever. However, there's quite some interaction with Soprano. Is that normal?

I mean like:

Code: Select all

[/usr/bin/nepomukservicestub] void Soprano::Server::ServerCore::serverConnectionFinished()

All I can see is the line when strigi restarts but it's normal too:
Code: Select all
[/usr/bin/nepomukservicestub] nepomukstrigiservice(5617)/nepomuk (strigi service) FileSystemWatcher::Private::run: woke up


Don't know, might it have to do with the fact that I have deleted .kde a few weeks ago - i.e. before 4.4? Is it possible that there's some harm?

That shouldn't cause the problem. Does it always restart as its handling the same file?

Not quite sure. It starts indexing my "Dokumente" folder, then sits inactive for another few minutes and then restarts with the music folder - not sure if it's always the same file though. How could I find out?

It should mention in the logs what file it is indexing.

Another place to check to see if it is crashing is dmesg, which will have a message output on to it if an application crashes.

.xsession-errors tells me nothing about specific files, sorry...Where else would I check?

Edit: new strigi and libclucene have been updated and now it seems to be working. all works as should