https://bugs.kde.org/show_bug.cgi?id=521140
Bug ID: 521140
Summary: Default excluded snap directory from indexing
Classification: Frameworks and Libraries
Product: frameworks-baloo
Version First unspecified
Reported In:
Platform: Other
OS: Linux
Status: REPORTED
Severity: wishlist
Priority: NOR
Component: balooctl
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
DESCRIPTION
The current default when file indexing is activated is for baloo to index all
of the $HOME directory and exclude hidden folders and content (metadata),
unless those are also activated.
The issue is that snap currently sits in the $HOME dir rather than in a hidden
directory as a flatpak would do and there is a lot of file turnover inside
these directories that trigger baloo to index them.
Until snap fully implements the move from ~/snap to ~/.snap/data (experimental
at the moment), users with snap installed have to manually add the exclusion of
the ~/snap directory to avoid issues with baloo consuming too many resources
trying to keep up with what's going in in snap.
STEPS TO REPRODUCE
1. go to setting > file index
2. activate file indexing, but leave hidden files unchecked
3. use any snap (firefox usually)
OBSERVED RESULT
baloo churns and consumes system resources trying to keep up with the file
changes within the ~/snap directory as it serves up the snap application.
EXPECTED RESULT
baloo should not index such container folders in $HOME as there is too much
activity inside and there is no real benefits to having those files indexed
(wine might also be an issue).
ADDITIONAL INFORMATION
adding a default exclusion for the ~/snap directory would prevent this unwanted
activity
--
You are receiving this mail because:
You are watching all bug changes.
