Bug 226549

Summary: nepomuk/strigi search dolphin bar not working
Product: [Applications] dolphin Reporter: Leonardo M <lrm.regs-15.07>
Component: generalAssignee: Peter Penz <peter.penz19>
Status: RESOLVED DUPLICATE    
Severity: normal CC: andresbajotierra, sebastian, trueg
Priority: NOR    
Version: 16.12.2   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:

Description Leonardo M 2010-02-12 15:12:14 UTC
Version:            (using KDE 4.4.0)
OS:                Linux
Installed from:    Ubuntu Packages

I've updated to KDE 4.4 and gave nepomuk/strigi a try.
The indexing didn't take more than a few minutes.
I don't experience high CPU or RAM usage (as far as I know hehe).
But, searching in Dolphin gives no result (search term: "config". I have a file named config in my home folder, so...).
There's an interesting thing though. By clicking on "Query Results" you can unveil this text:

nepomuksearch:/?sparql=select distinct ?r  where { { { ?r ?v1 ?v2 . ?v2 bif:contains "'config*'" . } UNION { ?r ?v1 ?v3 . ?v3 ?v4 ?v2 . ?v4 <http://www.w3.org/2000/01/rdf-schema#subPropertyOf> <http://www.w3.org/2000/01/rdf-schema#label> . ?v2 bif:contains "'config*'" . } . { ?r a ?v5 . ?v5 <http://www.w3.org/2000/01/rdf-schema#subClassOf> <http://www.semanticdesktop.org/ontologies/2007/03/22/nfo#FileDataObject>  . } UNION { ?r a ?v6 . ?v6 <http://www.w3.org/2000/01/rdf-schema#subClassOf> <http://www.semanticdesktop.org/ontologies/2007/03/22/nfo#Folder> . } . } .  ?r <http://www.semanticdesktop.org/ontologies/2007/01/19/nie#url> ?v7 .  FILTER(REGEX(STR(?v7), "^file:///home/leo/")) .  }

If I delete all occurrences of websites and leave it as something like this:

nepomuksearch:/?sparql=select distinct ?r  where { ?r ?v1 ?v2 . ?v2 bif:contains "'config*'" }

then I do get some results.

Could those links be some trash left out from testing time?
Comment 1 Dario Andres 2010-03-20 16:01:25 UTC
This seems to be related to bug 222687...
Regards
Comment 2 Sebastian Trueg 2010-03-22 12:32:35 UTC

*** This bug has been marked as a duplicate of bug 222687 ***