Qt Version: 5.14.2 Frameworks Version: 5.69.0 Operating System: Linux 5.6.5-1-MANJARO x86_64 Windowing system: Wayland Distribution: Manjaro Linux -- Information about the crash: I start the system, login and DrKonqi tells me that baloo_file has crashed. The crash can be reproduced every time. -- Backtrace: Application: Baloo File Indexing Daemon (baloo_file), signal: Aborted Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7ffb01a27240 (LWP 4102))] Thread 3 (Thread 0x7ffb00c39700 (LWP 4259)): [KCrash Handler] #6 0x00007ffb0562dce5 in raise () from /usr/lib/libc.so.6 #7 0x00007ffb05617857 in abort () from /usr/lib/libc.so.6 #8 0x00007ffb04bcb753 in ?? () from /usr/lib/liblmdb.so #9 0x00007ffb04bc0435 in ?? () from /usr/lib/liblmdb.so #10 0x00007ffb04bc1676 in ?? () from /usr/lib/liblmdb.so #11 0x00007ffb04bc18b3 in ?? () from /usr/lib/liblmdb.so #12 0x00007ffb04bc34ec in ?? () from /usr/lib/liblmdb.so #13 0x00007ffb04bc6619 in mdb_cursor_put () from /usr/lib/liblmdb.so #14 0x00007ffb04bc94ab in mdb_put () from /usr/lib/liblmdb.so #15 0x00007ffb0613bb8a in Baloo::DocumentTimeDB::put(unsigned long long, Baloo::DocumentTimeDB::TimeInfo const&) () from /usr/lib/libKF5BalooEngine.so.5 #16 0x00007ffb06163a25 in Baloo::WriteTransaction::replaceDocument(Baloo::Document const&, QFlags<Baloo::DocumentOperation>) () from /usr/lib/libKF5BalooEngine.so.5 #17 0x00007ffb06154cb5 in Baloo::Transaction::replaceDocument(Baloo::Document const&, QFlags<Baloo::DocumentOperation>) () from /usr/lib/libKF5BalooEngine.so.5 #18 0x0000556c245f21c6 in ?? () #19 0x00007ffb05bb4002 in ?? () from /usr/lib/libQt5Core.so.5 #20 0x00007ffb05bb0dd6 in ?? () from /usr/lib/libQt5Core.so.5 #21 0x00007ffb04c2646f in start_thread () from /usr/lib/libpthread.so.0 #22 0x00007ffb056f13d3 in clone () from /usr/lib/libc.so.6 Thread 2 (Thread 0x7ffb0173c700 (LWP 4112)): #0 0x00007ffb056e6abf in poll () from /usr/lib/libc.so.6 #1 0x00007ffb043fb4a0 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x00007ffb043fb571 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x00007ffb05de48ac in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5 #4 0x00007ffb05d8b05c in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5 #5 0x00007ffb05bafc62 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #6 0x00007ffb06186b28 in ?? () from /usr/lib/libQt5DBus.so.5 #7 0x00007ffb05bb0dd6 in ?? () from /usr/lib/libQt5Core.so.5 #8 0x00007ffb04c2646f in start_thread () from /usr/lib/libpthread.so.0 #9 0x00007ffb056f13d3 in clone () from /usr/lib/libc.so.6 Thread 1 (Thread 0x7ffb01a27240 (LWP 4102)): #0 0x00007ffb056e6abf in poll () from /usr/lib/libc.so.6 #1 0x00007ffb043fb4a0 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x00007ffb043fb571 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x00007ffb05de48ac in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5 #4 0x00007ffb05d8b05c in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5 #5 0x00007ffb05d93066 in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5 #6 0x0000556c245df3ea in ?? () #7 0x00007ffb05619023 in __libc_start_main () from /usr/lib/libc.so.6 #8 0x0000556c245df59e in ?? () [Inferior 1 (process 4102) detached]
If I try to start it again from command line with 'balooctl enable': Enabling and starting the File Indexer replace called with invalid arguments, docId: 1103806595128 url: "/home/cubanpit/" mdb.c:2127: Assertion 'rc == 0' failed in mdb_page_dirty() KCrash: Attempting to start /usr/bin/baloo_file from kdeinit sock_file=/run/user/1000/kdeinit5__1 KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = baloo_file path = /usr/bin pid = 5313 KCrash: Arguments: /usr/bin/baloo_file KCrash: Attempting to start /usr/lib/drkonqi from kdeinit sock_file=/run/user/1000/kdeinit5__1 I purged the index database and restarted Baloo, now it works again. This means that I will not be able to reproduce the issue anymore, sorry.
*** This bug has been marked as a duplicate of bug 389848 ***