https://bugs.kde.org/show_bug.cgi?id=522364
--- Comment #12 from Alfeno Rodrigues <[email protected]> --- (In reply to tagwerk19 from comment #11) > (In reply to Alfeno Rodrigues from comment #10) > > Claude AI suggested that the root is: > > > > Root cause: at searchstore.cpp:224, Q_ASSERT(!res.filePath.isEmpty()) > > fails for documentId 1801491829628827, which apparently exists in the > > posting index but has no corresponding resolvable file path — likely > > a stale index entry left over from a deleted/moved/renamed file. > To me that seems strange... > > It's not unknown that a file "vanishes" without Baloo knowing. In normal > operation Baloo gets iNotify messages when files are deleted, sometimes the > records are ophaned (if Baloo is killed before the cleanup completes, at > least that happened a while back, I'd need to check is the same happens now) > or if you've deleted a large number of files and the iNotify queue > overflows, Baloo does not then see the delete. In general Baloo copes with > this... > > It seems strange that there is an assert if sortResults is false, but not in > the equivalent code if sortResults is true... > > You've tried "$ baloosearch6 casa de" and that's worked, see what happens > with "$ baloosearch6 -s none casa de" Whould it help if I shared the KDE Balloo Database? -- You are receiving this mail because: You are watching all bug changes.
