https://bugs.kde.org/show_bug.cgi?id=391258
--- Comment #2 from Erik Dal <kiwim...@runbox.com> --- Saw another user having the same problem on reddit https://www.reddit.com/r/kde/comments/82ozwh/baloorunner_takes_up_25_cpu_usage/ Tried what was proposed here. > § balooctl status > § balooctl stop > Confirm it's no longer using crazy amounts of CPU. If it still is (after a > minute), kill the process. Baloorunner did not stop using high CPU. Killed the process via KSysGuard. > § balooctl monitor > in a seperate terminal. Opened a new terminal window, and ran balooctl monitor. Following output: balooctl monitor Baloo is not running Press ctrl+c to exit monitor _ (blinking cursor here, as in 'working on it') I then opened a new tab in the new CLI window and ran: > § balooctl start Ran balooctl status a few times to check for any action. Output: Baloo File Indexer is not running Indexed 22061 / 22061 files Current size of index is 18,38 GiB I then let the CLI window sit in the background, hoping for output. Everything was quiet for about 8 hours, when I noticed temps rising, and found baloorunner back at 25% CPU. Ran qdbus org.kde.baloo /fileindexer org.kde.baloo.fileindexer.currentFile and found it working on a file I've recently opened (a .jpg). I proceeded to delete (shift+del) the file, and running currentFile. Found it still at the deleted file. No output in the terminal runnint balooctl monitor. Will try the process anew with this currenc spike. -- You are receiving this mail because: You are watching all bug changes.
