Find in Dolphin is almost completely useless. This is has been filed many times here, and a simple Google search returns many similar complaints. There are some workaround proposed, but they don't work. Bug 356737 says it's FIXED in 15.2 (back in December 2015) baloosearch status returns "Baloo File Indexer is running Indexer state: Idle Indexed 37207 / 37209 files Current size of index is 217.45 MiB" However, / has 337657 files. Searching for files even if they're in the same dir the Find is opened in doesn't return results (or turns less than it should), even without complex terms (like a filename that's one word) Reproducible: Always
15.12.3 search doesn't find ANY files at all. I know that the Windows 7 search is a massive downgrade from the 2k/XP one, but not finding ANYTHING for ANY search term in ANY directory is just ridiculously broken.
(In reply to Bzzz from comment #1) > 15.12.3 search doesn't find ANY files at all. I know that the Windows 7 > search is a massive downgrade from the 2k/XP one, but not finding ANYTHING > for ANY search term in ANY directory is just ridiculously broken. Baloo only indexes files in your home directory by default, you can list included directories with: balooctl config list includeFolders You can query baloo for specific information about a file with: balooshow -x <absolute or relative path>
balooctl config list includeFolders lists my home dir, nothing else. How to get rid of baloo and get a proper oldschool on-demand search that also finds stuff that has just been dropped into some dir? Or on network shares? Or on removable media?
Baloo immediately adds files to its index when they are added to the filesystem. You can configure baloo to add other directories to its index.
I can clearly see that it doesn't find anything, so something's completely broken. Moreover, an index-based search tool is already available, it's called locate and it has been working fine for the past two decades. There's no need for a replacement that's actually worse than the original. Furthermore, either baloo it is working "immediately" so it decreases performance on every file system operation (I don't want that), or it is delayed (as locate), so that it cannot give accurate results shortly after copying and moving stuff (I don't want that as well). I'm especially opposed to huge collections of metadata that are useless when searching for file contents, or use as much space as the source files and take as long to search as well. Just because disk space and CPU time is cheap nowadays it doesn't mean we have to waste it. I've been a full-time Linux user for only 7 years now. If I'm unable to use this fine piece of software, how on earth can you sell this to a newbie? A basic search function in the default file manager that needs configuration to work? That's as absurd as the already mentioned search tool in Windows 7. The Linux community may copy stuff that works well on other OSes, but nothing that is broken by design...and baloo is just that, I suspect. But please, prove me wrong, tell me how to configure and use a search box that works as reliable as the dolphin search before the "can't find stuff in hidden folders anymore" bug 269367, which is only 5 years old and still unresolved. Basically when we had this Nepomuk crap that was relatively easy to disable, offering a pure and working search function from dolphin instead.
Something has changed when upgrading to Plasma 5.6.5 - file names and extensions can be searched again, search point is still often set to "From Here (/)" when one is not in the root of the file system.
Having had numerous issues with Dolphin I now find that after upgrading the libkf5plasma5 package to 5.23 as a fix to other desktop issues, Dolphin has started working for me again...... Admittedly it is dog-slow, but it seems to work for searches in mounted volumes and user accounts. I started a search in root and will probably need another shave by the time it returns, assuming it ever does.
I don't get it. Why was this baloo stuff introduced in the first place? What is the expected benefit? Wouldn't it be way simpler (and more stable) to implement the dolphin search as a fontend for the "find" command? Something like "find . -iname *mysearchterm*" and the result is just displayed by dolphin.
(In reply to stu109382 from comment #8) > I don't get it. Why was this baloo stuff introduced in the first place? > What is the expected benefit? > Wouldn't it be way simpler (and more stable) to implement the dolphin search > as a fontend for the "find" command? > Something like "find . -iname *mysearchterm*" and the result is just > displayed by dolphin. One might look into this post: http://www.ryananddebi.com/2015/07/13/linux-getting-find-working-in-dolphin-on-kde-linux-mint-and-kubuntu/ It works much better for me now.
Looks like this actually works for folks now. It works for me, too. Baloo is fast and stable for me in Kubuntu 17.04.