https://bugs.kde.org/show_bug.cgi?id=509009
[email protected] changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #3 from [email protected] --- (In reply to Michael from comment #0) > 2. **Stuck Process:** An attempt to purge the index with `balooctl6 purge` > failed with the message "failed to stop!", indicating the `baloo_file` > process was stuck and unresponsive. Can happen if in baloo_file_extractor and it is too busy to listen... seen it with some scientific plots in a PDF (which needed hours to extract the "plain text"). Not particularly good, but.... > 5. **Critical Failure on Resume:** `balooctl6 resume` was executed. The > command itself returned "File Indexer resumed", but this is where the > critical failure began. I've not followed your steps (step by step) but I would think a "balooctl6 stop" and a "balooctl6 start" would be better then a "resume". You "resume" after a "pause"? A start is more of a cold start with all the needed checks. Does it fail when you log out and back in again? maybe remove the baloo folder completely, log out and back in again? Another hint, when killing Baloo, try a "systemctl stop --user kde-baloo" as this kills the tree of processes. "systemctl status --user kde-baloo" can give a filtered extract from the journal, *if* if has been started through the systemd unit file. It is worth a very basic "ps ax|grep baloo" to see if your system has started another copy. -- You are receiving this mail because: You are watching all bug changes.
