baloo is extremely slow to complete tracker completes in 25 minutes dpkg --status baloo | egrep "^(V|Pa)" Package: baloo Version: 4:5.18.0-0ubuntu1 To restart baloo: balooctl stop balooctl enable - it is unclear what the proper command is - it will initially chew on the index for 15 minutes before any files are processed here's a bit of the documentation that is missing: To see if baloo is running: X=$(ps -C baloo_file -o pid=) && pstree -pslU $X To see what file is processed: X=$(ps -C baloo_file_extractor -o pid=) && sudo lsof -p $X | grep /home balooshow is unreliable balooctl config show includeFolders balooctl config show excludeFolders System Settings – WorkSpace/Search – File use search via Dolphin, click Find, click Content progress: command takes 30 - 50 s balooctl status Baloo File Indexer is running Indexer state: Idle Indexed 177982 / 253657 files Current size of index is 415.12 MiB Reproducible: Always Steps to Reproduce: 1. have a pdf in your home directory 2. start baloo 3. Actual Results: using the lsof command, it can be determined that baloo spends at least 1.5 h on a single file Expected Results: baloo to complete in 25 minutes
Without the document it is impossible to determine if the content extraction or the database update is responsible for the long processing time. Please provide the file, if possible.
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!