Application: baloo_file (0.1) KDE Platform Version: 4.14.3 Qt Version: 4.8.6 Operating System: Linux 3.16.7-7-desktop x86_64 Distribution: "openSUSE 13.2 (Harlequin) (x86_64)" -- Information about the crash: - What I was doing when the application crashed: just starting opensuse 13.2 pablo@casa:~> baloo_file baloo_file(10893): Database Corrupted - What did you do? baloo_file(10893): baloo_file(10893): Serious Error: baloo_file(10893): The revision being read has been discarded - you should call Xapian::Database::reopen() and retry the operation DatabaseModifiedError: The revision being read has been discarded - you should call Xapian::Database::reopen() and retry the operation KCrash: Attempting to start /usr/bin/baloo_file from kdeinit KCrash: Connect sock_file=/home/pablo/.kde4/socket-casa/kdeinit4__0 KCrash: Application 'baloo_file' crashing... KCrash: Attempting to start /usr/lib64/kde4/libexec/drkonqi from kdeinit KCrash: Connect sock_file=/home/pablo/.kde4/socket-casa/kdeinit4__0 baloo_file(10890): Communication problem with "baloo_file" , it probably crashed. Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Message did not receive a reply (timeout by message bus)" " The crash can be reproduced every time. -- Backtrace: Application: Archivo Baloo (baloo_file), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [KCrash Handler] #5 0x00007fbeecd48e2a in () at /usr/lib64/libxapian.so.22 #6 0x00007fbeecd47edc in Xapian::Database::Database(Xapian::Database const&) () at /usr/lib64/libxapian.so.22 #7 0x00007fbeecd5205a in Xapian::Enquire::Internal::Internal(Xapian::Database const&, Xapian::ErrorHandler*) () at /usr/lib64/libxapian.so.22 #8 0x00007fbeecd5220e in Xapian::Enquire::Enquire(Xapian::Database const&, Xapian::ErrorHandler*) () at /usr/lib64/libxapian.so.22 #9 0x0000000000417ea3 in _start () Reported using DrKonqi
*** This bug has been marked as a duplicate of bug 333772 ***
It seems like the database has been corrupted. Please run - $ balooctl disable $ balooctl enable This will reset your index and restart indexing. I realize this isn't a proper fix. We're working on ways to automatically recover from corrupted databases.
Thanks Vishesh Handa, it worked for me