Search from app menu (kicker), kfind or krunner doesn't work at all. Balooctl status reports being running, and home folder is included both in ~/config/baloofilerc file and also in search plasma settings, but searching for files on desktop doesn't work. I tried to disable then purge then re-enable baloo without success. Operating System: Manjaro Linux KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 Kernel Version: 5.4.89-1-MANJARO OS Type: 64-bit
Run 'balooctl purge' once.
It doesn't work at all. See attached video.
Created attachment 135092 [details] Baloo broken
Requested info not provided. Won't invest any time here. Works on openSUSE Tumbleweed.
(In reply to Stefan Brüns from comment #4) > Requested info not provided. Won't invest any time here. > > Works on openSUSE Tumbleweed. What info you need ?
I run coredumpctl and found many crashes related to baloo that happen everyday and sometimes many times at one day, they are similar and have a very big backtrace with one line recursively repeated : [Thread debugging using libthread_db enabled] Using host libthread_db library "/usr/lib/libthread_db.so.1". Core was generated by `/usr/bin/baloo_file'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x00007fd8d2658396 in ?? () from /usr/lib/liblmdb.so [Current thread is 1 (Thread 0x7fd8cd9af640 (LWP 1380))] (gdb) bt #0 0x00007fd8d2658396 in ?? () from /usr/lib/liblmdb.so #1 0x00007fd8d265aefe in ?? () from /usr/lib/liblmdb.so #2 0x00007fd8d265b644 in ?? () from /usr/lib/liblmdb.so #3 0x00007fd8d265bc50 in mdb_get () from /usr/lib/liblmdb.so #4 0x00007fd8d3b32355 in Baloo::IdFilenameDB::get(unsigned long long) () from /usr/lib/libKF5BalooEngine.so.5 #5 0x00007fd8d3b2c3ac in Baloo::DocumentUrlDB::get(unsigned long long) const () from /usr/lib/libKF5BalooEngine.so.5 #6 0x00007fd8d3b3d135 in Baloo::Transaction::documentUrl(unsigned long long) const () from /usr/lib/libKF5BalooEngine.so.5 #7 0x00005578ac848e94 in ?? () #8 0x00007fd8d3b445af in Baloo::WriteTransaction::removeRecursively(unsigned long long, std::function<bool (unsigned long long)> const&) () from /usr/lib/libKF5BalooEngine.so.5 #9 0x00007fd8d3b44607 in Baloo::WriteTransaction::removeRecursively(unsigned long long, std::function<bool (unsigned long long)> const&) () from /usr/lib/libKF5BalooEngine.so.5 #10 0x00007fd8d3b44607 in Baloo::WriteTransaction::removeRecursively(unsigned long long, std::function<bool (unsigned long long)> const&) () from /usr/lib/libKF5BalooEngine.so.5 . . . #65478 0x00007fd8d3b44607 in Baloo::WriteTransaction::removeRecursively(unsigned long long, std::function<bool (unsigned long long)> const&) () from /usr/lib/libKF5BalooEngine.so.5 #65479 0x00007fd8d3b44607 in Baloo::WriteTransaction::removeRecursively(unsigned long long, std::function<bool (unsigned long long)> const&) () from /usr/lib/libKF5BalooEngine.so.5 #65480 0x00007fd8d3b44607 in Baloo::WriteTransaction::removeRecursively(unsigned long long, std::function<bool (unsigned long long)> const&) () from /usr/lib/libKF5BalooEngine.so.5 #65481 0x00007fd8d3b44607 in Baloo::WriteTransaction::removeRecursively(unsigned long long, std::function<bool (unsigned long long)> const&) () from /usr/lib/libKF5BalooEngine.so.5 #65482 0x00005578ac849437 in ?? () #65483 0x00007fd8d3697302 in ?? () from /usr/lib/libQt5Core.so.5 #65484 0x00007fd8d3693f0f in ?? () from /usr/lib/libQt5Core.so.5 #65485 0x00007fd8d26ca3e9 in start_thread () from /usr/lib/libpthread.so.0 #65486 0x00007fd8d31da293 in clone () from /usr/lib/libc.so.6
Did you run `balooctl purge` on the command line as Stefan requested?
(In reply to Nate Graham from comment #7) > Did you run `balooctl purge` on the command line as Stefan requested? I run the command many times, the problem is still persistent, but when I create a new user the problem is gone. I think consecutive upgrades corrupted my user config installation.
What about when you manually delete the Baloo index at /home/nate/.local/share/baloo/index?
I got it to work like you said, after deleting ~/.local/share/baloo and running "balooctl purge" and rebooting for two times (first doesn't work). Thanks that really helped me :)
I had a feeling. That means it's effectively yet another duplicate of Bug 431664. *** This bug has been marked as a duplicate of bug 431664 ***