https://bugs.kde.org/show_bug.cgi?id=506516
[email protected] changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #1 from [email protected] --- (In reply to [email protected] from comment #0) > #15 0x00007b337bb100d1 in qt_assert (assertion=assertion@entry=0x7b337c6eb263 > "!term.isEmpty()", file=file@entry=0x7b337c6eb231 > "./src/engine/document.cpp", line=line@entry=23) at > /usr/src/qt6-base-6.9.0-0zneon+24.04+noble+release+build112/src/corelib/global/qassert.cpp:105 > #16 0x00007b337c6c15e2 in Baloo::Document::addPositionTerm (this=<optimized > out>, term=..., position=<optimized out>) at > /usr/src/kf6-baloo-6.15.0-0zneon+24.04+noble+release+build39/src/engine/document.cpp:21 > #17 Baloo::Document::addPositionTerm (this=<optimized out>, term=..., > position=<optimized out>) at > /usr/src/kf6-baloo-6.15.0-0zneon+24.04+noble+release+build39/src/engine/document.cpp:21 > #18 0x00007b337c6d75e6 in Baloo::TermGenerator::indexText > (this=0x7ffe33f3c808, text=..., prefix=...) at > /usr/src/kf6-baloo-6.15.0-0zneon+24.04+noble+release+build39/src/engine/termgenerator.cpp:110 > #19 0x00007b337c6d76d4 in Baloo::TermGenerator::indexText (this=<optimized > out>, text=...) at > /usr/src/kf6-baloo-6.15.0-0zneon+24.04+noble+release+build39/src/engine/termgenerator.cpp:51 > #20 0x00007b33761ea1f9 in KFileMetaData::PlainTextExtractor::extract > (this=<optimized out>, result=0x7ffe33f3c780) at > /usr/src/kf6-kfilemetadata-6.15.0-0zneon+24.04+noble+release+build23/src/extractors/plaintextextractor.cpp:119 I think it's worth adding a cross reference to Bug 506187 here but to be on firmer ground need to find out which file is causing trouble. In 506187 a UTF-16 file was the cause (a UTF-16 file that contained Chinese/Japanese scripts but that may not be a "necessary condition"). You should be able to follow what's being indexed by running "balooctl6 monitor" or by enabling logging and following the journal. You can set up logging by creating a "~/.config/QtProject/qtlogging.ini" file containing: [rules] kf.baloo=true kf.baloo.*=true kf.kfilemetadata=true and then restart Baloo, you might need: $ pkill baloo_file $ systemctl start --user kde-baloo If you are seeing the same issue, the good news is that it's not there in Neon Testing or Unstable. -- You are receiving this mail because: You are watching all bug changes.
