Bug 333743

Summary:	With whitelisted folders in baloofilerc, $HOME is shown as blacklisted
Product:	[Applications] systemsettings	Reporter:	Hrvoje Senjan <hrvoje.senjan>
Component:	kcm_baloo	Assignee:	Pinak Ahuja <pinak.ahuja>
Status:	RESOLVED DUPLICATE
Severity:	minor	CC:	aspotashev, nate, pinak.ahuja, plasma-bugs
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:
Attachments:	baloofilerc

Description Hrvoje Senjan 2014-04-22 23:48:52 UTC

e.g i have:
folders=/home/hrvoje/Videos,/home/hrvoje/Pictures,/home/hrvoje/Music,/home/hrvoje/Documents/despot in baloofilerc

(probably from pre-beta stages), entire $HOME is shown as blacklisted. i realize these don't have sense with entire $HOME being indexed, but still ;-)

Reproducible: Always

Comment 1 Vishesh Handa 2014-05-12 10:28:07 UTC

Could you please paste your entire baloofilerc file?

Comment 2 Christoph Feck 2014-06-03 23:22:32 UTC

If this is still reproducible, please add the information requested in comment #1.

Comment 3 Hrvoje Senjan 2014-06-03 23:33:06 UTC

Created attachment 87001 [details]
baloofilerc

sorry, somehow i missed comment 1

Comment 4 Hrvoje Senjan 2014-11-25 22:57:36 UTC

observation:
also valid with 5.x

Comment 5 Vishesh Handa 2014-11-26 15:00:55 UTC

Marking as CONFIRMED.

I'm not too sure how to solve this. We can obviously just not show HOME as blacklisted, but the internal configuration can clearly not be represented.

Comment 6 Nate Graham 2019-11-12 20:04:18 UTC

Will be fixed automatically once the KCM explicitly exposes the whitelist functionality. As such, marking this bug as a duplicate of the one tracking that: Bug 352487.

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