https://bugs.kde.org/show_bug.cgi?id=373626
--- Comment #6 from Bob Miller <rmiller...@gmail.com> --- Did a web search on the topic and one suggestion was to delete ~/.local/share/baloo. I renamed the current file to baloo.sav, then did a complete reboot. Upon login, the baloo_file_extractor did NOT crash. It ran for a while, and I could watch the index file in ~/.local/share/baloo grow. No large CPU or memory usage. After maybe a couple of minutes, index stopped growing and a check of the process table showed no instance of baloo_file_extractor. The process baloo_file did continue to run. The new ../share/baloo file only has two files: index and index.lock The saved baloo file had drwxrwxr-x. 2 bob bob 4096 May 22 15:14 calendars drwxrwxr-x. 2 bob bob 4096 Nov 30 2017 contacts drwxrwxr-x. 2 bob bob 4096 Jun 2 17:10 email drwxrwxr-x. 2 bob bob 4096 Jun 2 17:10 emailContacts -rw-r--r--. 1 bob bob 76341248 May 20 21:57 index -rw-rw-r--. 1 bob bob 8192 Jun 2 17:38 index-lock drwxrwxr-x. 2 bob bob 4096 Oct 8 2016 notes So far it does not appear that I'm missing any data. Calendars and contacts show the same data as before. -- You are receiving this mail because: You are watching all bug changes.
