The disk of the machine remains active continuously after start or hibernation. Ending the baloo_file_extractor process rectifies the condition Reproducible: Always Steps to Reproduce: 1. Start machine 2. observe disk activity Actual Results: The disk is continuously running Expected Results: Disk activity should not continue without end.
indexing the files under your $HOME will take at least some time initially to complete, that is expected (depends on how many files you have). Instead of killing baloo_file_extractor , you can just disable file indexing, if you don't want that behavior, systemsettings5 -> search -> file search -> (UNCHECK) enable file search
But disabling search does not solve the problem. It takes away the search function which I need. I ran the find utility from root and outputted the listing to a text file. It took 7 minutes. Therefor I propose the indexer utility cannot or should not index files longer than 10 minutes.
(In reply to Leon from comment #2) > But disabling search does not solve the problem. It takes away the search > function which I need. > > I ran the find utility from root and outputted the listing to a text file. > It took 7 minutes. Therefor I propose the indexer utility cannot or should > not index files longer than 10 minutes. Baloo also indexes file contents, find does not read file contents. If you don't want baloo to index contents, add only basic indexing=true into [General] section of Your ~/.config/baloofilerc Off topic: If you already know how to use find, check out mlocate and see how long it takes to build an index. Maybe it's faster.
As mentioned, disk activity is expected until indexing is complete. If it's slowing down your system, that's tracked with Bug 400704.