Bug 459205

SUMMARY
When Baloo finished file content indexing there were some files reported as failed to index using 'balooctl status'.
Some of them got indexed using 'balooctl index' FILE but some not.
Balooshow knew the file but complained about old data about the file.

Tried to do the 'balooctl clear' on that files, then balooshow to see they are gone followed by 'balooctl index' FILE.
All files become indexed, checked by 'balooshow -x' FILE but the same files were still reported as failed to index.

Did mdb_copy -n -c on the index file (no error reported, file went down in size by around 10 GiB), left KDE session (logged of), entered KDE session, tried 'balooctl check' what not helped. Tried to clear the files and index them again, got them indexed again but the same set of "failed" files was reported.

Found workaround, using KDE Settings GUI I set folders with those files to not be indexed, waited for file count downsized (balooctl status) and then allowed their indexing again one by one.
After that no failed files are being reported now.

Can this be done more elegant way please?



SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.25.5
KDE Frameworks Version: 5.98.0
Qt Version: 5.15.5

ADDITIONAL INFORMATION
balooctl status
Baloo File Indexer is running
Indexer state: Idle
Total files indexed: 386,606
Files waiting for content indexing: 0
Files failed to index: 0
Current size of index is 27.77 GiB

balooctl indexSize
File Size: 27,77 GiB
Used:      2,34 GiB

PostingDB:     684,04 MiB    28.579 %
PositionDB:       2,22 GiB    95.046 %
DocTerms:       3,34 GiB   143.018 %
DocFilenameTerms:      26,52 MiB     1.108 %
DocXattrTerms:       4,00 KiB     0.000 %
IdTree:       5,30 MiB     0.221 %
IdFileName:      28,42 MiB     1.187 %
DocTime:      15,38 MiB     0.642 %
DocData:      25,97 MiB     1.085 %
ContentIndexingDB:            0 B     0.000 %
FailedIdsDB:            0 B     0.000 %
MTimeDB:       5,80 MiB     0.242 %