| Summary: | Dolphin search shows doubled results | ||
|---|---|---|---|
| Product: | [Frameworks and Libraries] frameworks-baloo | Reporter: | tagwerk19 |
| Component: | Baloo File Daemon | Assignee: | baloo-bugs-null |
| Status: | REPORTED --- | ||
| Severity: | normal | CC: | postix, stefan.bruens |
| Priority: | NOR | ||
| Version First Reported In: | 5.111.0 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| See Also: |
https://bugs.kde.org/show_bug.cgi?id=477068 https://bugs.kde.org/show_bug.cgi?id=468256 |
||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
An addendum...
On systems running systemd, Baloo runs with a cap on the memory it can use, see:
https://invent.kde.org/frameworks/baloo/-/merge_requests/124
Limiting the RAM to 512 Mbyte means that it loads the system less.
When restarting the indexing with "balooctl purge", Baloo is not limited and you may see an impact on responsiveness. Restarting the system will restart the indexing following the systemd unit limits...
Alternatively, kill the baloo_file process, purge the database and start the service with systemctl:
pkill baloo_file
balooctl purge
systemctl --user start kde-baloo.service
|
SUMMARY A search with Dolphin shows each match "twice": the "This is the file you are looking for.txt" and a "This is the file you are looking for.txt (1)" This will be most obvious for people with a simple, ext4, disc setup STEPS TO REPRODUCE: 1... Index your files with Baloo 2... Update to Frameworks 5.111 3... Wait for a while, open a "tag folder" or search for a term... OBSERVED RESULT: You may get two results: This is the file you are looking for.txt This is the file you are looking for.txt (1) EXPECTED RESULT: You get the single hit, as before: This is the file you are looking for.txt SOFTWARE/OS VERSIONS: Neon User 5.27 Plasma: 5.27.8 Frameworks: 5.111.0 Qt: 5.15.11 Filesystem: Ext4 ADDITIONAL INFORMATION: This is a side effect of: https://invent.kde.org/frameworks/baloo/-/merge_requests/169 This patch resolves the issue with files being indexed multiple times on systems with BTRFS (and multiple subvolumes). Baloo now indexes the files with a "stable" document ID whereas previously it often saw files "as new files" after a reboot. A "balooctl purge" and letting the rendexing continue will remove the doubled entries. After this has completed the problem of multiple entries for BTRFS should be solved and the "older" set of index entries on ext4 based systems should also go.