417717 2020-02-15 19:43:29 +0000 Baloo crashes on loin 2020-02-16 21:11:57 +0000 1 1 3 Frameworks and Libraries frameworks-baloo Baloo File Daemon unspecified Fedora RPMs Linux RESOLVED DUPLICATE 389848 drkonqi NOR crash --- 0 brpia stefan.bruens nate 0 oldest_to_newest 1910412 0 brpia 2020-02-15 19:43:29 +0000 Application: baloo_file (5.66.0) Qt Version: 5.13.2 Frameworks Version: 5.66.0 Operating System: Linux 5.4.18-200.fc31.x86_64 x86_64 Distribution: Fedora 31 (Workstation Edition) -- Information about the crash: - What I was doing when the application crashed: Logging in to any user space on KDE Fedora 31 or earlier version from Fedora 28. The crash can be reproduced every time. -- Backtrace: Application: Baloo File Indexing Daemon (baloo_file), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f533e69c800 (LWP 19525))] Thread 3 (Thread 0x7f5330bb3700 (LWP 20029)): [KCrash Handler] #6 0x00007f5341dc0625 in raise () from /lib64/libc.so.6 #7 0x00007f5341da98d9 in abort () from /lib64/libc.so.6 #8 0x00007f53414addb3 in mdb_assert_fail.constprop () from /lib64/liblmdb.so.0.0.0 #9 0x00007f53414a29c5 in mdb_page_dirty () from /lib64/liblmdb.so.0.0.0 #10 0x00007f53414a3c56 in mdb_page_alloc.isra () from /lib64/liblmdb.so.0.0.0 #11 0x00007f53414a3e93 in mdb_page_touch () from /lib64/liblmdb.so.0.0.0 #12 0x00007f53414a5aec in mdb_cursor_touch () from /lib64/liblmdb.so.0.0.0 #13 0x00007f53414a8bfd in mdb_cursor_put () from /lib64/liblmdb.so.0.0.0 #14 0x00007f53414aba9b in mdb_put () from /lib64/liblmdb.so.0.0.0 #15 0x00007f53428f5582 in Baloo::PostingDB::put(QByteArray const&, QVector<unsigned long long> const&) () from /lib64/libKF5BalooEngine.so.5 #16 0x00007f534290d458 in Baloo::WriteTransaction::commit() () from /lib64/libKF5BalooEngine.so.5 #17 0x00007f53428fd743 in Baloo::Transaction::commit() () from /lib64/libKF5BalooEngine.so.5 #18 0x000055f33be4547c in Baloo::UnindexedFileIndexer::run() () #19 0x00007f534235141b in QThreadPoolThread::run() () from /lib64/libQt5Core.so.5 #20 0x00007f534234dd96 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #21 0x00007f53415144e2 in start_thread () from /lib64/libpthread.so.0 #22 0x00007f5341e856d3 in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f53316b6700 (LWP 19536)): #0 0x00007f5341e7aa6f in poll () from /lib64/libc.so.6 #1 0x00007f5340d9980e in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #2 0x00007f5340d99943 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x00007f5342552843 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5 #4 0x00007f53424fc1db in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5 #5 0x00007f534234cc45 in QThread::exec() () from /lib64/libQt5Core.so.5 #6 0x00007f5342930f6a in QDBusConnectionManager::run() () from /lib64/libQt5DBus.so.5 #7 0x00007f534234dd96 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #8 0x00007f53415144e2 in start_thread () from /lib64/libpthread.so.0 #9 0x00007f5341e856d3 in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f533e69c800 (LWP 19525)): #0 0x00007f5341e7aa6f in poll () from /lib64/libc.so.6 #1 0x00007f5340d9980e in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #2 0x00007f5340d99943 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x00007f5342552843 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5 #4 0x00007f53424fc1db in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5 #5 0x00007f53425040b6 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #6 0x000055f33be32fe9 in main () [Inferior 1 (process 19525) detached] The reporter indicates this bug may be a duplicate of or related to bug 411139. Possible duplicates by query: bug 415416, bug 414397, bug 413797, bug 413773, bug 413558. Reported using DrKonqi 1910671 1 nate 2020-02-16 21:11:57 +0000 *** This bug has been marked as a duplicate of bug 389848 ***