Created attachment 113057 [details] screencast Dolphin fails to find some files even after baloo indexing is done! And there is no fallback to disable baloo engine and seach every subfolder
that is why I suggested to dump current FIND stuff for good and replace it with KFIND. see: https://bugs.kde.org/show_bug.cgi?id=395255
Using arch with latest versions, expirience the same. Would do you think if I introduce a patch that will create a tick in dolphin settings that disables using baloo index and uses directory traversing? Baloo bug: https://bugs.kde.org/show_bug.cgi?id=400932
I would very much welcome an option to use FIND as the search backend over baloo.
Some ideas: - Can you run `balooshow [path to file]`? Is that file in the index? If it is, does `baloosearch [filename]` find it? - Is the file located on an NTFS disk? Those don't get indexed. - Is the file inside a folder in the excluded folders list?
- balooshow shows the file in the index. - EXT4 partition - not inside excluded folder list I often don't get any search results Dolphin. I literally just now had to disable and reenable baloo to get results again in Dolphin. (I've tried restarting dolphin first which does nothing.)
Very strange. :/ Sounds like Baloo is doing its part, so maybe Dolphin is to blame...
If Dolphin is to blame why does search work after disbaling and reenabling baloo? Strange indeed!
Oh, that was an important piece of information! :) Disabling and re-enabling Baloo deletes and recreates the index. So it seems like the old index had problems, and re-indexing fixed them. This is not entirely unexpected since there have been a lot of fixes and improvements to indexing recently.
Well, I've had to rebuild the index in a single day without having updated my system, so the database seems to somehow corrupt on its own.