https://bugs.kde.org/show_bug.cgi?id=413694
Joachim Wagner <jwag...@computing.dcu.ie> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jwag...@computing.dcu.ie
--- Comment #7 from Joachim Wagner <jwag...@computing.dcu.ie> ---
I observe the same / similar issue with btrfs for /home. I've about 20k files,
mostly PDFs, to be indexed and when all files are indexed baloo starts over
again in an endless loop.
In /var/log/messages, I see lots of baloo_file_extractor / kf.baloo messages
"id seems to have changed. Perhaps baloo was not running, and this file was
deleted + re-created" messages as reported in
https://github.com/NixOS/nixpkgs/issues/63489#issuecomment-563007599
@Stefan: Is /var/log/messages the "journal" you are referring to?
I am using the default KDE of openSUSE Leap 15.3. According to Kontact > Help >
About Kontact > Libraries, it uses "KDE Frameworks 5.76.0" and "Qt 5.12.7
(built against 5.12.7)".
I did not have this problem using XFS for /home on the same OS, so I concur
with comment 4 that this may be specific to using btrfs.
I am not too worried about the CPU usage but the index growing by a few GB in
every round is a problem for me.
If the issue cannot easily be fixed I'd therefore welcome a partial solution at
least avoiding large index updates. This could for example be implemented by
recording the sha256 fingerprint of every indexed file and only indexing the
contents of files with a new sha256 fingerprint and linking files with the same
content in the baloo database.
--
You are receiving this mail because:
You are watching all bug changes.
