SUMMARY: Dolphin falls back to its internal filenamesearch when Baloo is disabled. Searches for multiple terms that work with Baloo fail when Baloo is disabled STEPS TO REPRODUCE: 1... Create a test file $ echo "Hello Mary" > letter-to-mary.txt 2... If you have Baloo running and doing content indexing, search for "Hello Mary" or "Letter Mary" in Dolphin 3... Disable Baloo with $ balooctl disable (as seems to be the case, you might need to type "balooctl" or "balooctl6") 4... Repeat the tests OBSERVED RESULT: The initial searches for "Hello Mary" and "Letter Mary" work. If you fall back to Dolphin's internal filenamesearch, the content search for "Hello Mary" (with two spaces) fails. A search for "Hello Ma" works. A search for "He Mary" fails. The filename search is similar, a filename search for "letter-to-mary" works, searches for "letter to mary" or "letter mary" fails EXPECTED RESULT: There's too many ways a search query can slip through the cracks and not give you files you "know" that are there. SOFTWARE/OS VERSIONS: Neon Unstable Dolphin: 24.11.70 Plasma: 6.1.90 Frameworks: 6.7.0 Qt: 6.7.2 ADDITIONAL INFORMATION: There will be a new release of filenamesearch that uses "ripgrep" and "ripgrep-all" ("rg" and "rga"), see merge request: https://invent.kde.org/network/kio-extras/-/merge_requests/374 This bug report focuses on the original filenamesearch behaviour, if differences appear between the original and the new rg/rga searches, they'll be noted here. If there are regressions or behaviours diverge significantly, separate issues will be logged.
Also discussed here... https://old.reddit.com/r/kde/comments/1e7am1k/help_issues_with_dolphin/ deep link: https://old.reddit.com/r/kde/comments/1e7am1k/comment/le3fdgq/ I think that's sufficient to mark this as "confirmed"
Looks more nuanced... I've gone back to some old installation .iso's, with Baloo disabled a search for letter mary does not find files "Letter to Mary.txt" or "Letter-to-Mary.txt". I've tried a sample of old .iso's, going back to neon-testing-20201020-1821.iso which is as far back as I've got... So the bug has been there for a while... However it is more nuanced because, if I enable Baloo, index the test folder and do the exactly same test on a current system Chose "Filename" rather than "Content" search and look for letter mary This also fails (as discussed in the Reddit post). It works if you chose "Content". So the behaviour (now) is the same, independent of whether you are using Baloo or not. No, if I go back to my old .iso's, the letter mary search *worked* with neon-testing-20231031-0251.iso and before. It *failed* with neon-testing-20231212-0250.iso This is bad... There's a regression ported across from the common or filenamesearch code to the baloosearch code between 2023/10/31 and 2023/12/12. If there are other explanations, I'd be very interested... That is about as far as I can take this, I have to leave it to someone else to confirm,look at the code and do proper bisection...