Bug 344646

Summary:	Baloo indexer scans excluded directories
Product:	[Unmaintained] Baloo	Reporter:	Lastique <andysem>
Component:	General	Assignee:	Vishesh Handa <me>
Status:	RESOLVED DUPLICATE
Severity:	normal
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Kubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	strace log from akonadi_baloo_indexer process as it scans the filesystem after boot

Description Lastique 2015-02-28 00:18:33 UTC

I'm trying to disable baloo indexer. AFAIK, the official way is to add the home directory to the excluded directories in System Settings->Desktop Search, but this no longer works. I tried adding my home directory, as well as root directory to the excluded list but after boot akonadi_baloo_indexer scans the filesystem and hogs cpu anyway.



Reproducible: Always

Steps to Reproduce:
1. Add your home directory or root directory to the excluded list.
2. Reboot.
3. See CPU usage in top or System Monitor.

Actual Results:  
aconadi_baloo_indexer uses a CPU core and filesystem is accessed.

Expected Results:  
akonadi_baloo_indexer should be idle.

Kubuntu 14.10 x86_64, KDE 4.14.1.

Comment 1 Lastique 2015-02-28 00:21:27 UTC

Created attachment 91338 [details]
strace log from akonadi_baloo_indexer process as it scans the filesystem after boot

I've attaches an exerpt of strace output from the akonadi_baloo_indexer process as it was scanning the filesystem. It seems, the output repeats over time, so there seems to be some unterminated loop.

Comment 2 Vishesh Handa 2015-02-28 11:23:46 UTC

The Akonadi part is completely independent of the main Baloo file stuff, and the KCM. I think you can disable it by removing the indexer via akonadi console.

*** This bug has been marked as a duplicate of bug 332195 ***

Comment 3 Lastique 2015-02-28 11:48:04 UTC

You cannot disable it in the console, the indexer will start again after reboot.

I don't think this is a duplicate. My intention is similar to the bug 332195, but the actual problem is different. Either the indexer process does not respect the excluded directories list, or there is some other problem that results in the filesystem accessing loop.

Comment 4 Vishesh Handa 2015-02-28 12:28:16 UTC

There is no excluded directory list for Akonadi. It stores the emails in its own custom way. The Desktop Search KCM is only for files. If the `akonadi_baloo_indexer` process is using too much CPU, then it's a problem with Akonadi or its indexer. Nothing to do with files.

The Akonadi part is completely independent. If you want I can leave this bug open for a while, but nothing is going to change. Specially since we aren't making any more Baloo-4 releases.

Comment 5 Vishesh Handa 2015-03-17 12:56:10 UTC


*** This bug has been marked as a duplicate of bug 332195 ***