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: | stefan.bruens |
Priority: | NOR | ||
Version: | 5.111.0 | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
See Also: | https://bugs.kde.org/show_bug.cgi?id=477068 | ||
Latest Commit: | Version Fixed In: |
Description
tagwerk19
2023-10-21 10:36:55 UTC
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 |