On Thu, Apr 17, 2014 at 8:33 PM, Genes Lists <lists@xxxxxxxxxxxx> wrote: > On 04/17/2014 10:37 AM, Lukas Jirkovsky wrote: > >> >> Is it with KDE PIM? I remember a discussion in the release ML that >> baloo was somewhat broken in PIM. I dunno if that was fixed or not. >> >> No not using PIM. I killed off all the baloo processes - short term > fix.There really should be an off button on this kind of thing. > What I found is after runing the current pacman update, then I did the following. Logout and back in to kde. Then once logged back in went to the kde system settings and into Desktop Search, and simply add the user home directory to the list not to search. Apply the changed setting, and then logout and back in (there was a slight delay to the logout process at this point due to the initial baloo processes running but I just waited out the half minute or so till it logged out). There was be a baloo file cleaner process running when I logged back in, which on my machines seemed to run for a few minutes only, and then stop. At that point if I checked the file: $ cat .kde4/share/config/baloofilerc and found that at the top that there were already the lines: [Basic Settings] Indexing-Enabled=false [General] several other lines after this..... At that point baloo quietened down and there were no further issues with baloo but I guess you need to have a little patience during the initial running of the processes mentioned above, so it is a short term issue only. I have seen a gentoo thread which suggests that allowing baloo to index email does give a very efficient search even for tens of thousands of mails, but of course the initial indexing process does take a little time and CPU cycles for several minutes depending on how many directories and files are in the mail area - but once that is complete then it is suggested that it works extremely well. -- mike c
