https://bugs.kde.org/show_bug.cgi?id=402154
Pierre Baldensperger <pierre.baldensper...@numericable.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDSINFO |CONFIRMED
Resolution|WAITINGFORINFO |---
Ever confirmed|0 |1
--- Comment #4 from Pierre Baldensperger <pierre.baldensper...@numericable.fr>
---
(In reply to Stefan Brüns from comment #3)
> KF 5.53 and even 5.57 is way too old. Update to a current version.
Thanks a lot for following up on this.
I haven't been stuck on 5.57 : I regularly update my system, currently I am
running KDE Frameworks 5.68.0 with Plasma 5.18.3 (under OpenSuSE Leap 15.1 if
that matters).
The situation with baloo re-indexing is still *exactly* the same as last year,
and it has been the same with (almost) every single KF release in the interval
(not sure I tested with all of them but pretty close). No need to go into
details again : they are still exactly the same as in my earlier post and the
bug title summarizes it in a self-explanatory fashion. First indexing run seems
to go all right, then _after_reboot_ it does apparently think that all files
are new and re-indexes everything, not realizing they are exactly the same
files. Reboot after reboot, this ends up with ever increasing index size and
multiplying the number of indexed files vs the number of actual files.
As I said in the previous post, I suspect that this may be due to some
specificity of the BTRFS file system I use, but I have no way to test that
hypothesis. Something with the BTRFS operation (system reboot related) may
induce baloo into thinking that the files are new / not already indexed...? At
least I don't see any other peculiarity of my system so, BTRFS aside, this
problem would likely affect many users and wouldn't have gone almost unnoticed
with so few reports : there would be tons of bug reports about the same thing.
HOWEVER, regarding the second part of my previous comment, I noticed that the
command "balooctl suspend" now behaves as expected : it stops the frantic
indexer, but I am still able to use the search function. So that's at least
some substantial recovered functionality that makes baloo much much better than
the dead weight it was before for me ! Thanks a lot to whoever improved this
behavior !
--
You are receiving this mail because:
You are watching all bug changes.
