Bug 362226

Summary:	Baloo index keeps entries in directories marked as "should be excluded"
Product:	[Frameworks and Libraries] frameworks-baloo	Reporter:	Marco Leise <Marco.Leise>
Component:	general	Assignee:	Pinak Ahuja <pinak.ahuja>
Status:	RESOLVED FIXED
Severity:	normal	CC:	abulak, johann.hoechtl, kdeu, nate, pinak.ahuja, rulatir, simgunz, smithjd15
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Gentoo Packages
OS:	Linux
Latest Commit:		Version Fixed In:	5.43
Sentry Crash Report:

Description Marco Leise 2016-04-25 10:16:23 UTC

It seems there is no way to remove a directory or directory tree from Baloo's index.

Reproducible: Always

Steps to Reproduce:
I feel too lazy to give exact instructions, but neither adding a path to the excluded paths, listing its name in the excluded file names, nor using balooctl clear will remove it from the index. The latter will typically say that the directory is not indexed yet, although balooshow lists it.

Actual Results:  
balooshow Entwicklung/D/test/oprofile_data:
13018574155155458 2050 3031123 /home/marco/Entwicklung/D/test/oprofile_data

Expected Results:  
I'd like to rely on Baloo cleaning old (deleted or now-excluded files/directories) out automatically without manual interaction. I'd also expect that adding a directory to the excludes will recursively remove its information.

Comment 1 Simone Gaiarin 2016-10-29 08:58:38 UTC

I second this. My index is 8 GB, because any time I add some temporary folder this is indexed and then never forgotten.

Comment 2 Lukas Ba. 2017-01-08 11:23:52 UTC

Searching for the term indexcleaner in the repo, i noticed that there are only definitions for the index-cleaning class, but no code calls the method
IndexCleaner::run() ?

https://github.com/KDE/baloo/search?utf8=%E2%9C%93&q=indexcleaner

Could this be the reason that baloo fails to remove deleted files from the database?

The database should be cleaned of deleted files at least once after baloo is started, since it can not know about files removed in its absence.
Also, it should clean its database after the include/exclude configuration was changed.

> balooctl clear
I also made a bugreport about this, since its an error in balooctl.
https://bugs.kde.org/show_bug.cgi?id=374736

Comment 3 Nate Graham 2017-10-27 20:07:43 UTC


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

Comment 4 Nate Graham 2017-10-27 20:09:48 UTC

*** Bug 370429 has been marked as a duplicate of this bug. ***

Comment 5 Nate Graham 2017-10-27 20:09:53 UTC

*** Bug 373430 has been marked as a duplicate of this bug. ***

Comment 6 Nate Graham 2017-10-27 20:21:13 UTC

*** Bug 362622 has been marked as a duplicate of this bug. ***

Comment 7 Jamie Smith 2018-01-19 23:04:05 UTC

This issue was fixed by this commit: https://phabricator.kde.org/R293:2f899073ab3cc735e0c78790c4f62af6d8e6669c

Comment 8 Marco Leise 2018-01-22 00:53:33 UTC

Thanks alot!