https://bugs.kde.org/show_bug.cgi?id=400704
--- Comment #8 from Jack <ostrof...@users.sourceforge.net> --- After several reboots, I finally had systemsettings5 show me file search, and turning that off, and another reboot, seems to have stopped the indexer from running. The odd thing was that despite earlier doing balooctl suspend, balooctl stop, and balooctl disable, and balooctl showing disabled, it was still running. Not really sure what finally stopped it. Hopefully it wont just start up again by itself. -- You are receiving this mail because: You are watching all bug changes.
