https://bugs.kde.org/show_bug.cgi?id=437189
--- Comment #6 from tagwer...@innerjoin.org ---
(In reply to Munzir Taha from comment #5)
> Which is definitely a bug.
Well, unexpected :-)
> balooctl staus after balooctl check always shows:
> Files waiting for content indexing: 0
I don't think anything appears in the 'Files waiting' count if you are not
indexing content. "Basic" indexing is done immediately. Baloo queues up files
for content indexing and sends them off in batches to a separate process.
> I tried to check with balooctl monitor which used to show the files being
> indexed and it doesn't even show any result however hard I tried. Weirdness++
Balooctl monitor lists the files as the "content indexing" is done. If you have
not selected content indexing, you just get an "Indexing modified files" when
baloo is told of a change.
However, it does seem that if you manually ask for something to be indexed:
balooctl index alonglongfile
this doesn't appear in "balooctl monitor"
This doesn't answer your original question of
> But then how can a normal user show all the files in my system with duration
> > 18s?
I'm not sure there's a way without enabling content indexing as you need to
read the files to read the "embedded" tags.
--
You are receiving this mail because:
You are watching all bug changes.
