Hi there,

here I come with another problem related to nepomuk searching via dolphin's search bar, but different from the ones I saw in the forum.

So my situation is the following: I have kde 4.4.0 (kubuntu packages), nepomuk is apparantly working, at least it crawled through all my files and finally finished.

Now I entered a search term in dolphin's search bar, namely "Claudio". First thing I noticed it takes very long, namely about a minute, to return results. Then the results are not quite what I expected. Among the returned files were some accurate hits, containing "Claudio" in text, or vcards, but also other, completely unrelated files, like image files with no "Claudio" in their file names, tags, comments, etc.

Moreover, when I select in dolphin's search bar to search "what: filenames", this setting is apparantly simply ignored, since precisely the same results are returned, and not only the ones matching "Claudio" in their filenames.

I would like to ask if also other people experience this buggy behaviour, or if it is maybe a problem with kubuntu packages only. Also any hints as how to actually use the data gathered by nepomuk (since via dolphin it's problematic) would be highly appreciated.

Best regards,
Zsaja

Same problem here.

The search results tend to be very confusing.
Sometimes seemingly unrelated files are displayed in the results, whereas sometimes files that should obviously match the entered search terms are not found.

And, for me, it also takes a very long time until results are displayed.

Are you both running openSUSE? I opened a bug report about this (https://bugs.kde.org/show_bug.cgi?id=227151), which could be closed today:

After digging into this issue with Sebastian Trueg on IRC, it turned out that
this issue was related to the openSUSE kdebase4-runtime packages: The sources
of tag 4.4.0 were changed by the KDE team (Virtuoso related fix) after openSUSE already had fetched and packaged them.

New packages are about to appear in the openSUSE build service soon.

No, I'm on Kubuntu. Apparantly the situation is similar on both distros.

I'm on Arch Linux. Is this really a distro-specific problem?

We notified the KDE-maintainers of your distros, seems that the did like openSUSE and packaged kdebase4-runtime before Sebastian Trueg added a quickfix.