Application: baloo_file_extractor (5.68.0) Qt Version: 5.12.8 Frameworks Version: 5.68.0 Operating System: Linux 5.11.0-27-generic x86_64 Windowing system: X11 Distribution: Ubuntu 20.04.3 LTS -- Information about the crash: Already tried disabling, purging and reenabling, to no avail. Not sure if I need sudo to purge (which supposedly worked, but didn't fix anything), but additionaly when I try just `balooctl purge` it stays "Stopping the File Indexer" until it fails to stop. - What I was doing when the application crashed: Logged in after boot. Also, periodically while using the system afterwards, it crashes again and asks for error reports, it's always the same. The crash can be reproduced every time. -- Backtrace: Application: Extrator de arquivos do Baloo (baloo_file_extractor), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fd90051bf80 (LWP 2188))] Thread 3 (Thread 0x7fd8fe582700 (LWP 2199)): #0 __GI___libc_read (nbytes=16, buf=0x7fd8fe581b60, fd=8) at ../sysdeps/unix/sysv/linux/read.c:26 #1 __GI___libc_read (fd=8, buf=0x7fd8fe581b60, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x00007fd90256bb2f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007fd902522ebe in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x00007fd902523312 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x00007fd9025234a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x00007fd903908583 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x00007fd9038af4db in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x00007fd9036e7785 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x00007fd904912efa in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5 #10 0x00007fd9036e89d2 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x00007fd902de2609 in start_thread (arg=<optimized out>) at pthread_create.c:477 #12 0x00007fd903376293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7fd8fedfc700 (LWP 2194)): #0 0x00007fd903369aff in __GI___poll (fds=0x7fd8fedfbca8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x00007fd9024b0c1a in ?? () from /lib/x86_64-linux-gnu/libxcb.so.1 #2 0x00007fd9024b290a in xcb_wait_for_event () from /lib/x86_64-linux-gnu/libxcb.so.1 #3 0x00007fd8ff5fb298 in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x00007fd9036e89d2 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x00007fd902de2609 in start_thread (arg=<optimized out>) at pthread_create.c:477 #6 0x00007fd903376293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7fd90051bf80 (LWP 2188)): [KCrash Handler] #6 0x00007fd902fa22bc in mdb_midl_xmerge () from /lib/x86_64-linux-gnu/liblmdb.so.0 #7 0x00007fd902f9971c in ?? () from /lib/x86_64-linux-gnu/liblmdb.so.0 #8 0x00007fd902f9b844 in ?? () from /lib/x86_64-linux-gnu/liblmdb.so.0 #9 0x00007fd902f9bc28 in ?? () from /lib/x86_64-linux-gnu/liblmdb.so.0 #10 0x00007fd902f9f021 in mdb_cursor_put () from /lib/x86_64-linux-gnu/liblmdb.so.0 #11 0x00007fd902fa176b in mdb_put () from /lib/x86_64-linux-gnu/liblmdb.so.0 #12 0x00007fd9049dc842 in Baloo::PositionDB::put(QByteArray const&, QVector<Baloo::PositionInfo> const&) () from /lib/x86_64-linux-gnu/libKF5BalooEngine.so.5 #13 0x00007fd9049f7ccf in Baloo::WriteTransaction::commit() () from /lib/x86_64-linux-gnu/libKF5BalooEngine.so.5 #14 0x00007fd9049e7c63 in Baloo::Transaction::commit() () from /lib/x86_64-linux-gnu/libKF5BalooEngine.so.5 #15 0x00005617f2c5062c in ?? () #16 0x00007fd9038e95b6 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x00007fd9038dccf5 in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x00007fd9042c8a66 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #19 0x00007fd9042d20f0 in QApplication::notify(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #20 0x00007fd9038b093a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x00007fd9039078b0 in QTimerInfoList::activateTimers() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x00007fd90390819c in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #23 0x00007fd90252317d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #24 0x00007fd902523400 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #25 0x00007fd9025234a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #26 0x00007fd903908565 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #27 0x00007fd9038af4db in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #28 0x00007fd9038b7246 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #29 0x00005617f2c4e7d4 in ?? () #30 0x00007fd90327b0b3 in __libc_start_main (main=0x5617f2c4e580, argc=1, argv=0x7fff4c450b88, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff4c450b78) at ../csu/libc-start.c:308 #31 0x00005617f2c4e88e in ?? () [Inferior 1 (process 2188) detached] Possible duplicates by query: bug 441780, bug 430455, bug 428123, bug 426195, bug 422483. Reported using DrKonqi
"balooctl disable" or "balooctl purge" can get stuck if the indexer is not listening to commands... You can be impolite, kill the process with "pkill baloo_file" and remove the (probably corrupt) index with "rm ~/.local/share/baloo/index I think though, reading Bug 431664, it might be worth trying to move to a newer release.
*** Bug 445773 has been marked as a duplicate of this bug. ***
Thank you for reporting this issue in KDE software. As it was reported on an older version, can we please ask you to see if you can reproduce the issue with a more recent software version? If you can confirm this issue still exists in a recent version, please change the version field and the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!