https://bugs.kde.org/show_bug.cgi?id=417127
--- Comment #10 from tagwer...@innerjoin.org --- Possible that this is related: https://old.reddit.com/r/kde/comments/f1y1g0/baloo_doesnt_resume_after_suspend/ I can corroborate this behaviour for Balooctl 5.64.0 (from Fedora 30) and Balooctl 5.68.0 (from Neon Testing) A `balooctl suspend` sets indexer suspended (seen in `balooctl status` and `balooctl monitor`) and resume does not kick it back into action. A `balooctl disable; balooctl enable` does restart the indexing. The disable and enable change the [Basic Settings] Indexing-Enabled=... setting (as might be expected) -- You are receiving this mail because: You are watching all bug changes.
