https://bugs.kde.org/show_bug.cgi?id=506608
[email protected] changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #2 from [email protected] --- (In reply to NitramO from comment #0) > #15 0x00007ae8927100d1 in qt_assert (assertion=assertion@entry=0x7ae8932b1263 > "!term.isEmpty()", file=file@entry=0x7ae8932b1231 > "./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 0x00007ae8932875e2 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 0x00007ae89329d5e6 in Baloo::TermGenerator::indexText > (this=0x7fff83ce8528, text=..., prefix=...) at > /usr/src/kf6-baloo-6.15.0-0zneon+24.04+noble+release+build39/src/engine/termgenerator.cpp:110 We do seem to have a rush of these at the moment... Seems to be happening just on Neon User at the moment. It is triggered by files encoded with UTF-16 (Bug 506187 / Bug 506516) but there was also a binary file that "looked like" UTF-32 (Bug 506570) It would be interesting if you are also dealing with a UTF-16 file You should be able to follow what's being indexed by running "balooctl6 monitor" or by enabling logging and following the journal. With "balooctl6 monitor" you'll see the files successfully indexed by Baloo shown by lines with "Indexing: .... : Ok", when the extractor crashes you'll get the "Indexing: ..." and the Dr Konqi pop-up, without the "Ok". It's possible that "balooctl6 status" and "balooctl6 failed" will give the name of the failing file(s). You can find out whether the file is UTF-16 with: $ file the-file--that-causes-the-crash.txt You can set up logging if you wish 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 -- You are receiving this mail because: You are watching all bug changes.
