This seems to be more of a Baloo issue rather than Dolphin I think. At least I think Dolphin defaults to Baloo on a default install. In the Downloads folder for example, where I can have files reside for months, I had many results missing files that should have shown up. KFind could find them. There is a way to go into the files properties dialog, permissions tab, advanced permissions, ok, ok to exit the properties dialog. The file will now get metadata updated, although nothing was done, this set of steps seems to trigger Baloo to index the file. The file will now show up in search results via Dolphin or KRunner. Not sure how to reproduce, if it's due to Baloo no longer actively indexing properly or ignoring files randomly, could be a bug in Baloo or something wrong with the system as the install had been running since Aug 2016. Reporting in case anyone else is affected, and that it was requested to make this a separate issue from a similar one I had with hidden files.
I have the same issue. After a few weeks on a fresh install of Manjaro, dolphin stopped returning *any* CTRL+F search results. Rebooting did not help. I had to disable baloo, delete the index database from ~/.local/share/baloo, kill any baloo processes, re-enable baloo again and then reindex my entire drive. After that, dolphin started returning search results. Not sure how to reproduce it either. The index was there and didn't look corrupt and I hadn't changed any of the baloo configuration settings.
This is the same for me, and has been recurrent on fresh 18.04/18.10 Kubuntu installs. Using a different file browser allows me to find files. Bug report states that I am missing Baloo and symlinks for it which I am able to see exist with `whereis`.
(In reply to Brennan Kinney from comment #0) > ... or ignoring files randomly You don't mention which distribution/filesystem so there two possible pointers. There was a post in Bug 433204 flagging that baloo can hit a 'max_user_watches' limit which in some (older) distributions can be "ridiculously low". It's worth checking with sysctl fs.inotify.max_user_watches This would mean that baloo might miss files it should be indexing as they are created/modified - but a "balooctl check" would prompt baloo to catch up with what it has missed. Secondly, there's Bug 431664. It refers to a collection (Bug 430891, Bug 430273, Bug 430435) with somewhat overlapping symptom. The solution here was to "balooctl purge" the index - delete the old and let baloo reindex from scratch. I'll flag this as "Needs Info", if you are still encountering problems, add the details here...
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!