https://bugs.kde.org/show_bug.cgi?id=472954
--- Comment #8 from postix <pos...@posteo.eu> --- Instead of using the UI in the KCM, I've tried `balooctl suspend` in the cmd line and while the command output was > File Indexer suspended respectively with `balooctl disable` > Disabling and stopping the File Indexer however, baloo_file_extractor keeps running in the background utilizing 30% CPU and slowing down the system, making it significantly lag. After the two commands above `balooctl monitor` says > Press ctrl+c to stop monitoring > File indexer is running > Idle (like 30 seconds later at this point) but the process keeps using up to 40% CPU and 11% (3 GB) res ram, though I'm not sure what it's actually doing now, as I don't hear the HDDs rattling anymore. I had to re-open the FileSearch kcm to get an updated state. It reports now that file indexing has been disabled, but it took a few minutes from suspending / disabling until it actually stopped. -- You are receiving this mail because: You are watching all bug changes.
