I upgraded my KDE 4.9.5 to 4.10 and I had my old nepomuk database with a little bit over 65000 indexed files but I couldn't see any file indexer activity.
So I decided to remove the old database and settings because I read that nepomuk got some significant improvements and I actually read from forum posts and blogs that the indexing speed has been improved a lot.

The problem still exists though.
The file indexer for me is idle except if I call the nepomukindexer command from the console.

If I use a command like:

Code: Select all

cd ~/Desktop
find . -exec nepomukindexer {} \;

Then all of my files under the Desktop directory will get indexed.

I even left my computer alone without any activity for a few hours because I read that nepomuk will only work when the system resources are idle (I guess due to the fact that it's running with "nice 19"), but still when I checked it, there was nothing more indexed.

Files/Folder I removed and restarted nepomuk:
~/.kde/share/config/nepomukstrigirc
~/.kde/share/config/nepomukbackuprc
~/.kde/share/config/nepomukserverrc
~/.kde/share/apps/nepomuk

Any suggestions on what else to check?

Same problem here.

nepomuk indexer is always idle and "nepomuk repository details" is stuck on "Calculating..." without any file being actually calculated.

A great relief to see I'm not the only one here.
The renewed nepomuk is the reason why I went to 4.10.
Only it does nothing. Too bad...
I checked if dependencies were missing... But I can't see that.
P.

I have a similar problem with KDE 4.10.

The configuration seems correct : index documents, audio, images, etc. in my home directory.
But the Nepomuk Indexer stays inactive all the time.
I have only « 9 files indexed » in the Nepomuk controller details.

I use Arch Linux testing packages.

And then there is this bug filed: https://bugs.kde.org/show_bug.cgi?id=314559
This is in Arch. But it looks familiar.

Considering that this bug supposedly affects many users and that this is a major level bug related to a major feature of a major KDE release, I really hope that quality assurance methods will be taken more seriously in the near future.

I downgraded the nepomuk-core package in my Arch installation to 4.9.98 (the last rc version) and int work again. Someone did a unfortunate last commit

I too downgraded to the rc version (kubuntu quantal). Nepomuk started but never came out of "stage one". It kept on indexing as fast as lightning. It did so for much to long a time. And while it was doing this the cpu was at 100% continu and the fan went like crazy.

I must have a little patience I guess. Or someone must know where to find a good version.

A patch has now been sent to the distributions to include in their KDE 4.10 packages, and a bug fix will be shipped in KDE 4.10.1.

@Begonia: I suggest opening a new topic for that issue so we can debug it properly, as it is different to the one seen here.

bcooksley wrote:A patch has now been sent to the distributions to include in their KDE 4.10 packages, and a bug fix will be shipped in KDE 4.10.1.

@Begonia: I suggest opening a new topic for that issue so we can debug it properly, as it is different to the one seen here.

Kubuntu has updated their nepomuk-core package and this issue is solved for me.

Thanks!

And after this got fixed, now I face another bug:
https://bugs.kde.org/show_bug.cgi?id=314986

On my machine I have the same issue. Nepomuk keeps crashing all the time. When I was filing this bug I discovered that I was not the only one. Perhaps it has to do with the upgrading.
Anyway it doesn't work! Perhaps with the daily build of raring ringtail it will go properly. I'll let you know.

I just downloaded the daily build and installed it on a small partition. Nepomuk did not work at all.
In a few days I'll try again.

On Raring Nepomuk now worked (after an update)! It took quite some time to index the folders it was supposed to index (23.000 files) and Nepomuk used a lot of resources.

After it was done I tested the results.
When I e.g. looked for files that would contain the word "gulden", Nepomuk discovered two files.
In KDE 4.7 Nepomuk discovered six.

Windows "search and index" discovers eight (in completely identical folders).
When I restart Nepomuk again is working for ever to see if anything has changed. This again takes a lot of resources.
But I'm confident that it will be good. Nepomuk is heading in the right direction on my machine!

Interesting behaviour. Are you able to determine which process is using large amount of resources when logging into a new session?