I have Kubuntu 14.04 and just installed the newest updates. Looking at the process list I see baloo indexer running.
I could not find a checkbox in Baloo settings to turn off the indexing.
|
|
You can make your file manager display hidden files, after which go to
to (or add if there is not such option)
to disable baloo. I know it is way too easy but it did work for me and also for the guy who posted this simple solution on this page. Disabling Akonadi server and Nepomuk search plugin can greatly increase performance in a KDE environment. |
|||||||||||||
|
|
Baloo is responsible for desktop search. Quoting one of the Baloo authors:
|
|||||||||||||||||||||
|
|
From the Gentoo forum: http://forums.gentoo.org/viewtopic-p-7522240.html As of KDE 4.13.0 (Kubuntu Trusty) it is no longer possible to disable Semantic Desktop in the GUI. Though there is a "Desktop Search" applet in the System Settings, and you should be able to blacklist your home dir there, doing so has no effect and Baloo (who has taken over from Nepomuk/Strigi) keeps doing its stuff with 100% load and multi-Gigabyte memory use on the CPU core it runs in. You may check the CPU load on your system using 'top':
Check the I/O load on your system with 'iotop':
To permanently disable baloo, symlink it to /bin/true:
and
This will prevent it from ever running again. Doing so will lose search functionality of course, but does not seem to have any adverse effects beyond that. |
|||||||||||||||||||||
|
|
To avoid manually editing
|
||||
|
|
|
I haven't tried it yet, but apparently, you can also do
(I had my home folder in the "don't search" section, probably from nepomuk, and |
|||||||||||||||||||||
|
|
Adding $HOME to the list of excluded paths did stop the baloo_file_extractor, which was using 100% CPU. However it then started baloo_file_cleaner which was trashing my harddisk. Making sure that it does not autostart, seemed to fix the problems:
|
|||||||||||||
|
|
Though there are a few ways to prevent Baloo from indexing, my intention is to prevent Baloo from even running. As per The KDE docs there is no User-accessible way to do that, so I've combined a solution found on the KDE forums with user 's solution to disable the executables:
I then go a step further and ensure that
For additional insurance, if the
|
||||
|
|
|
A post in KDE forums by Aaron Seigo suggests:
The post is located here: https://forum.kde.org/viewtopic.php?f=154&t=120047#p304335 Use the following to resume:
Use the following to check is baloo is suspended or not:
TIP: When I type |
|||||||||
|
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?