Bug 386074

Summary:	Register vaults locations with the plain-text-search engine.
Product:	[Frameworks and Libraries] frameworks-baloo	Reporter:	cryptodude
Component:	general	Assignee:	Stefan Brüns <stefan.bruens>
Status:	ASSIGNED ---
Severity:	normal	CC:	ivan.cukic, tagwerk19
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description cryptodude 2017-10-22 15:34:25 UTC

We have two dirs (and lots of potential subdirs) that should be excluded from the text-search engine (Baloo).
The default dir a new backend-storage is created and the actual mount-point for the unencrypted files.

Both dirs should be excluded from the search / indexing capabilities from Baloo, I hope its obvious why.

I don't know how to do cross-services calls like this, but my guess is an dbus call would be easiest.

Comment 1 Ivan Čukić 2017-10-23 22:13:53 UTC

I agree. 

This has two potential approaches: 
 - Baloo should skip filesystems like these regardless of whether they are from Vault or not
 - Vault can notify Baloo and a few other things that these dirs should be ignored

I'll see about it.

Comment 2 Ivan Čukić 2019-03-23 13:35:22 UTC

Assigning this to Baloo.

Ballo should ignore all encrypted mount points while indexing.

Now, for FUSE encrypted mounts, it is easy to check the file type - fuse.cryfs, fuse.encfs.

For block-encrypted drives, it is a more difficult problem because they report normal filesystems since the device is encrypted - it is not a special FS.

Comment 3 Ivan Čukić 2019-03-23 13:35:59 UTC

> Ballo should ignore all encrypted mount points while indexing.

p.s. regardless of whether they are vaults or not.

Comment 4 tagwerk19 2025-01-20 12:00:19 UTC

(In reply to Ivan Čukić from comment #2)
> Ballo should ignore all encrypted mount points while indexing.
I notice that vaults appear in the System Settings > File Indexing exclude list when they are opened.

It might be prudent to add a Baloo exclusion for the parent folder, ~/Vaults, so it does not react to vaults being opened or not.  The Vaults folder is just a default but it would be a low hanging fruit...

A revisit may be worthwhile as there's been the low level change of Baloo using FSID/inode for tracking file IDs, this was done because of the BTRFS wobbliness when mounting subvolumes. Maybe worth checking if there's an impact on mounted vaults.