If this is your first visit, be sure to
check out the FAQ. You will have to register
before you can post. To start viewing messages,
select the forum that you want to visit from the selection below.
Please do not use the CODE tag when pasting content that contains formatting (colored, bold, underline, italic, etc).
The CODE tag displays all content as plain text, including the formatting tags, making it difficult to read.
Recently I have been having trouble with baloo_file_extractor using 100% CPU on my 17.04 and 17.10 systems.
I have found the reason. It is because I have files in my home directory that are used for my home NFS network. If .kde/share/config/baloofilerc does not have these file excluded, it gets its knickers in a twist. This is because these file cannot and should not be entered particularly when not all of the NFS network is up.
I see this as a failing in the design of baloo_file_extractor as it should not get hung on a folders that cannot be entered. Once the file .kde/share/config/baloofilerc is edited to add the excluded folders the generated file .config/baloofilerc should be either deleted or renamed.
Comment