In regards to the process using 100% of your CPU - can you please provide the full name and path of the process? My guess is that this is the index cleaner, dropping all the entries it did index (and it has known bugs in this regard - which are fixed in 4.13.1).

Ask your distro to include https://gitorious.org/baloo-kcmadv - it's an alternative config GUI which exposes many config details.

Having installed Kubuntu 14.04 this morning, and having encountered Baloo spiking my computer CPU to 100% usage (and mangling network access, too), and then finding out that to supposedly turn it off one must "exclude" directories -- which, by the way, DOES NOT work -- I'm seriously considering finding a different UI. KDE is no longer acceptable when the developers ignore major chunks of the community. To turn the fool thing off, I had to edit a text file.

So, when the brand new user with a somewhat older machine loads 14.04 and encounters this issue, that their brand new Linux install CRAWLS (which is what happens), is going to say, "Linux sucks." I think someone should seriously have thought more about the decision to FORCE this on us by default.

Unfortunately, Baloo is pretty strongly coupled with several important appplications.

The principle of least surprise has been seriously violated, and I find this reprehensible on the part of KDE devs.

It should be EASY to disable this app.

In 4.13.1 there's an explicitly switch off checkbox (it had to go through the internationalization teams' approval, because it added a new string to translate during string freeze).

For problems like "mangling network access" this does not look at all like a Baloo problem. Please open a separate thread about this issue if required.

jansmeral's tone might not be the best, but I must agree with him here. Thankfully I didn't go through KDE 4.12 myself... I had 4.11 and went straight to 4.13 from it. But if I did, I would have probably been quite upset at Desktop Search being impossible to disable. And overall I'm disappointed that KDE made such a mistake in an official release.

The problem is that Desktop Search (both Akonadi and Baloo) uses a lot of resources... typically CPU. I even read articles about it crashing some people's computers. After a google search I preformed out of curiosity, I found a lot of (more or less) rage comments about this, talking about how slow and bad KDE is again. I saddens me because I think KDE is great, yet things like this only add to its reputation of being "slow and bloated" and only suited for the fastest computers out there.

Separately, I don't believe that a component which isn't crucial should be enabled forcefully. Even if Desktop Search barely used any resources, I agree it should be the choice of users whether to enable it or not. It's on by default either way, so people will only be inclined to turn it off if they personally experience performance problems or issues of any other nature. I believe that is the perfect approach to take personally.

I believe you are mixing pieces of software. Akonadi has nothing to do with desktop search. It is a framework for Personal Information Management (PIM). The fact that it uses the Desktop Search libraries to do its searching does not mean it is an infrastructure for searching.

einar wrote:I believe you are mixing pieces of software. Akonadi has nothing to do with desktop search. It is a framework for Personal Information Management (PIM). The fact that it uses the Desktop Search libraries to do its searching does not mean it is an infrastructure for searching.

Ah... my mistake there sorry. I wanted to say Nepomuk but confused the names.