Created attachment 120146 [details] The image shows the null result of search SUMMARY Suddenly when you boot first time the system, the search of dolphin and krunner fail. In dolphin it happens when you search everything. In krunner it happens when you search files, it does not occour whith apps. Probably (I think about), its a problem with any packs of snap, beacause I discovered the problem after of install firefox snap, but I am not sure. STEPS TO REPRODUCE 1. Impredectible, normally in the first boot. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kde NEON 15.5 (available in About System) KDE Plasma Version: 15.5 KDE Frameworks Version: 5.58 Qt Version: 5.12 ADDITIONAL INFORMATION
Lately, I often get no results in dolphin when doing a search. I don't have file contents indexing enabled. When this happens, I have to disable baloo and reenable it to get Dolphin to return results. I have just had to do this probably the fifth time in the last few weeks. I'm on Manjaro.
When Dolphin fails to find a file, please do the following: - Run `balooshow [path to file you expect Dolphin to find]` That will show you whether or not it's indexed. - Run `baloosearch [filename]` to See if Baloo itself can find it.
Just happened again today for the second time that dolphin fails to return search results. Also, tag categories appear in tags:/ but they're all empty. [michael@michael-pc ~]$ balooshow ~/Dropbox/Articles/ 11823740023275008 65024 2752929 /home/michael/Dropbox/Articles/ Mtime: 1559727833 2019-06-05T11:43:53 Ctime: 1559727833 2019-06-05T11:43:53 [michael@michael-pc Articles]$ baloosearch lewis\ -\ finkish\ dispositions\ \(1997\).pdf Elapsed: 0.129715 msecs [michael@michael-pc Articles]$ balooctl status Baloo File Indexer is running Indexer state: Idle Indexed 31274 / 31274 files Current size of index is 25.93 MiB
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!
New information was added with comment #3; changing status for inspection.
There was a post in Bug 433204 flagging that baloo can hit a 'max_user_watches' limit. It can be "ridiculously low"... It's worth checking with sysctl fs.inotify.max_user_watches Contributing factors may be that snaps create some/many more folders that might need watching and that baloo and dropbox are both asking to use these notifications
(In reply to Michael D from comment #3) > [michael@michael-pc Articles]$ baloosearch lewis\ -\ finkish\ dispositions\ > \(1997\).pdf > Elapsed: 0.129715 msecs This particular example matches up with Bug 438850 and you are being caught by the hyphen in the filename - the issue is the search for a single character.
(In reply to Michael D from comment #3) > [michael@michael-pc Articles]$ baloosearch lewis\ -\ finkish\ dispositions\ \(1997\).pdf > Elapsed: 0.129715 msecs This is likely to be far too old to be useful but I missed somethign important in my previous reply. I think you'll find that balooshow -x lewis\ -\ finkish\ dispositions\ \(1997\).pdf gives you details of the file - as appears in the index A baloosearch lewis\ -\ finkish\ dispositions\ \(1997\).pdf Does searches for "lewis", "finkish", "dispostions" etc and gives you results where they _all_ appear. The problem is the single character "-", baloosearch doesn't return hits for one or two character searches. That means that the search including the "-" will give no results. You can try simpler: baloosearch lewis baloosearch lewis finkish searches and they'll probably work.
A possibly relevant merge request was started @ https://invent.kde.org/frameworks/baloo/-/merge_requests/165
Git commit c8d1b7cabcc810867f400e5ccfb96e41b03e0635 by Stefan Brüns. Committed on 10/07/2023 at 15:22. Pushed by bruns into branch 'master'. [QueryTest] Add test case for terms folded to empty strings The termgenerator removes leading, trailing and isolated punctuation characters. While this is no problem for leading or trailing punctuation as the normalized term is still non-empty, isolated punctuation ends up as an empty string. The matcher then tries to find e.g. "(content:'' OR filename:'')", which returns not results, instead of the exptedted "everything". Unfortunately it is non-trivial to remove such Terms. For the prase test, this is not at problem, as it always sees the whole phrase and can just skip the problematic part. M +15 -0 autotests/integration/querytest.cpp https://invent.kde.org/frameworks/baloo/-/commit/c8d1b7cabcc810867f400e5ccfb96e41b03e0635
(In reply to tagwerk19 from comment #7) > (In reply to Michael D from comment #3) > > [michael@michael-pc Articles]$ baloosearch lewis\ -\ finkish\ dispositions\ > > \(1997\).pdf > > Elapsed: 0.129715 msecs > This particular example matches up with Bug 438850 and you are being caught > by the hyphen in the filename - the issue is the search for a single > character. Single characters are not a problem, but isolated punctuation characters.
Git commit 6dbc3212825b2ffc360fda65f0022be224d9a5a1 by Stefan Brüns. Committed on 13/11/2023 at 21:41. Pushed by bruns into branch 'kf5'. [QueryTest] Add test case for terms folded to empty strings The termgenerator removes leading, trailing and isolated punctuation characters. While this is no problem for leading or trailing punctuation as the normalized term is still non-empty, isolated punctuation ends up as an empty string. The matcher then tries to find e.g. "(content:'' OR filename:'')", which returns not results, instead of the exptedted "everything". Unfortunately it is non-trivial to remove such Terms. For the prase test, this is not at problem, as it always sees the whole phrase and can just skip the problematic part. (cherry picked from commit c8d1b7cabcc810867f400e5ccfb96e41b03e0635) M +15 -0 autotests/integration/querytest.cpp https://invent.kde.org/frameworks/baloo/-/commit/6dbc3212825b2ffc360fda65f0022be224d9a5a1
A possibly relevant merge request was started @ https://invent.kde.org/frameworks/baloo/-/merge_requests/210