https://bugs.kde.org/show_bug.cgi?id=409257
--- Comment #15 from Gerson <gersonfjun...@yahoo.com.br> --- Exactly. I couldn't find any corrupted files and the workaround of re-indexing a single file is not sufficient. I've left my computer running for a few days with terminal open after running balooctl disable + enable. There was no error messages. Baloosearch on terminal was working fine, and on Dolphi it was ok as well. But the destkop search on application menu still fails. After rebooting the system... it happens again. The database breaks somehow and baloosearch on terminal shows blank lines. So, here are a new test to try to find something: 1) baloosearch is currently broken. It returns blank lines, while the number of lines actually match the number of expected search results. 2) I'll make a copy of the index file on ~/.local/share/baloo: cp index index.bak 3) re-indexing a folder: balooctl clear ~/Downloads && balooctl index ~/Downloads/. Note: the file I'm searching for is not on this folder. 4) baloosearch still broken. 5) Reindexing the Dropbox folder: 'balooctl clear ~/Dropbox' gives errors: Database has corrupted entries baloo may misbehave, please recreate the DB by running $ balooctl disable && balooctl enable 6) balooctl index ~/Dropbox/ : no new error messages 7) baloosearch still broken. But 'balooctl clear ~/Dropbox' does not show errors anymore. 8) 'balooctl clear ~/inSync/' return errors: Database has corrupted entries baloo may misbehave, please recreate the DB by running $ balooctl disable && balooctl enable 9) 'balooctl index ~/inSync/' : no new error messages 10) baloosearch still broken, but 'balooctl clear ~/inSync' does not show errors anymore. 11) I've try to clear/index other folders as well (~/tmp, ~/Documents, ~/Videos, ...). Most clear commands return the database corrupted error. Simply try to clear and reindex does not work. After all that, the md5sum and file sizes of the original index.bak and "new one" after all the clear and index commands are md5 file size 7205c24bc98368025847ddc2322637f8 index 44376064 602565b117986424cb4c0b39036889f2 index.bak 44376064 Even after I clear all folders, the file size won't change. The command 'balooctl indexSize' shows that the used space is much smaller. But it seems that it remains something broken within the index file. I can only recover baloosearch after running disable + enable, actually deletes the index file in the process. Another curious thing. I'm indexing only the file names, and not the content. Nonetheless, the process feels a bit too fast. Disabling and re-enabling baloo, the re-indexing process is almost instantaneous. Is it actually running the file name indexing from scratch? Or using some backup of the index file stored in a cache somewhere? BTW, my baloo version is 5.59.0-1 on Manjaro stable. -- You are receiving this mail because: You are watching all bug changes.
