| Summary: | Dolphin Internal File-Content Search Broken | ||
|---|---|---|---|
| Product: | [Applications] dolphin | Reporter: | 0e8h <default> |
| Component: | general | Assignee: | Peter Penz <peter.penz19> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | mail, sebastian, trueg |
| Priority: | NOR | ||
| Version: | 16.12.2 | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
|
Description
0e8h
2010-03-03 05:17:29 UTC
Thanks for the report, this might be a Kubuntu specific issue. Could you please check whether you have enabled Nepomuk and Strigi in the system settings? Yes both (Nepomuk and Strigi) are enabled, but I did not have the ('Use files index') checkbox ticked anyway, when searching. I tried it on after it didn't work, and still did not produce results that I knew the search string was in the file contents.
Hm, I've added Sebastian (= Nepomuk maintainer) to CC. I'll upgrade to 4.4.1 on Kubuntu during the next days and will check whether it works in my environment. Ok peter. please first check if you did not select "file name" in the search bar. In 4.4.1 that actually works. :) "please first check if you did not select "file name" in the search bar. In 4.4.1 that actually works. :)" In the file name I only had a '*'. Can you reproduce this behavior with the newest version of Dolphin (17.12.3)? Baloo (the new file indexer) should work (if not, you should file a bug against it). No response -> closing. Please reopen if you can still reproduce this behavior with the newest version of Dolphin. |