http://bugzilla.opensuse.org/show_bug.cgi?id=1157380
http://bugzilla.opensuse.org/show_bug.cgi?id=1157380#c6
--- Comment #6 from Wolfgang Bauer
After install and restart (init 3, init 5), I get:
<1.4> 2020-01-13 11:22:49 Telcontar baloo_file 14328 - - Failed to create database, removing corrupted database. <1.4> 2020-01-13 11:22:49 Telcontar baloo_file 14328 - - Failed to create database after deleting corrupted one. But it doesn't crash anymore, right?
The crash was due to database corruption, the patch should (hopefully) fix the crash. (although, AIUI it might also help to avoid the database getting corrupted in the first place) I have no idea at the moment why it complains that it "Failed to create database after deleting corrupted one" though... But that's rather a secondary problem, I'd say.
I started nautilus, then search. I don't know if this uses baloo or something else, it does not say. Did a search, worked. No, GNOME (and nautilus therefore) uses tracker for file indexing/searching.
baloo is KDE's file indexer and would e.g. be used by dolphin (or the Plasma desktop). "balooctl status" should show the current status of the file index.
I do not see how to restart baloo indexing. On the start menu I type "baloo", get no related command "balooctl purge" should delete the database and force a reindexing, or "balooctl disable" followed by "balooctl enable".
Or delete ~/.local/share/baloo/, that should also have fixed the crash in the first place (but I wanted to know if the patch helps...). -- You are receiving this mail because: You are on the CC list for the bug.