https://bugs.kde.org/show_bug.cgi?id=521140
--- Comment #2 from goo <[email protected]> --- this is a command line script i use to watch what is changing on my machine while i go about my business (mostly to find config files) find -not \( -path './snap/firefox/common' -prune \) -not \( -path './.cache' -prune \) -type f -mmin -1 -printf "%C+ %p\n" | sort -n | tail -10 notice that i put in a path statement in there because that snap dir was giving me too much noise and makes it difficult to find what i'm looking for. this would also be bad for baloo as it would constantly be trying to index those changes, just like the other path to cache On Sat, Jun 6, 2026 at 3:15 PM <[email protected]> wrote: > https://bugs.kde.org/show_bug.cgi?id=521140 > > [email protected] changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > CC| |[email protected] > > --- Comment #1 from [email protected] --- > (In reply to goo from comment #0) > > 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. > I don't have much experience with snaps. > > As far as I know, they are installed "system wide" under the /snap > directory. > That won't be indexed. What you have under ~/snap is local (config?) data. > > What do you see being indexed? You can run "balooctl6 monitor" to see what > Baloo is content indexing. You'd see files being bundled up into batches > of 40 > and given to the extractor. If you have a particular snap that causes > churn, I > can have a look... > > Note, there's some very recent work on improving the "balooctl6 monitor" > information. It you get something pretty minimal you've not got the patched > version. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
