KDE and Nepomuk

[Sfiet_Konstantin]

I don't know where to post, so I post this here.

There is a strange behaviour with nepomuk. I choose to index many files. In the first time, it takes much time to index it all. After this, each time I start a KDE session, it rescans all the folder again. I'm quite afraid of my disk usage, and also that nepomuk takes much CPU during sometimes. Is that normal, because, when the data is indexed, it's OK, no need to rescan it again ...

Did you encontered this "bug" too ? Did this problem reported upstream to KDE ?

[mikala]

I don't know where to post, so I post this here.

There is a strange behaviour with nepomuk. I choose to index many files. In the first time, it takes much time to index it all. After this, each time I start a KDE session, it rescans all the folder again. I'm quite afraid of my
disk usage,

There's an upstream bug about that if i'm not wrong.
Also i think i saw an patch for nepomuk in master so it's going to rescan a folder only if there's a file change.
I need to check again & if it's possible to backport it to our 4.6.x

[Sfiet_Konstantin]

There's an upstream bug about that if i'm not wrong.
Also i think i saw an patch for nepomuk in master so it's going to rescan a folder only if there's a file change.
I need to check again & if it's possible to backport it to our 4.6.x

Thanks

[mikala]

This thread is interresting : http://mail.kde.org/pipermail/nepomuk/2 ... 00339.html
& seems more related to strigi in fact.

[mareklaane]

In time the thread was started I did not have working Nepomuk/Strigi (in Mageia Cauldron) but now U've experienced the same nasty behaviour: after every log in I can see an icon on the system tray which has when right-clicking checked the option "File indexing is stopped" and when I remove the check it seems just start over all indexing... and so every time, like it doesn't remember the previous indexing. Such behaviour did appear since 4.7 (as I said before indexing didn't work at all).

[Sfiet_Konstantin]

Now it is even worse : Nepomuk reindex all the data again, and pops up a notification (as if it was the first time that it indexes the data ...)
Note, I use latest cauldron.