Bug 333743 - With whitelisted folders in baloofilerc, $HOME is shown as blacklisted
Summary: With whitelisted folders in baloofilerc, $HOME is shown as blacklisted
Status: RESOLVED DUPLICATE of bug 352487
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_baloo (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR minor
Target Milestone: ---
Assignee: Pinak Ahuja
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-04-22 23:48 UTC by Hrvoje Senjan
Modified: 2019-11-12 20:04 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
baloofilerc (1.08 KB, text/plain)
2014-06-03 23:33 UTC, Hrvoje Senjan 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
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 ***