Application: baloo_file (5.18.0) Qt Version: 5.5.1 Operating System: Linux 4.4.0-109-generic x86_64 Distribution: Ubuntu 16.04.3 LTS -- Information about the crash: - What I was doing when the application crashed: Crash after I renamed a directory and created similar contents again (think redownload artifacts for compilation) -- Backtrace: Application: Baloo File Indexing Daemon (baloo_file), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f841bb7b8c0 (LWP 2759))] Thread 2 (Thread 0x7f82d0ac4700 (LWP 2912)): #0 0x00007f8419c8827d in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x00007f8416ea06f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x00007f8416e5ce74 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007f8416e5d330 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x00007f8416e5d49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x00007f841a8c27eb in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x00007f841a869b4a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x0000000000420cd8 in Baloo::FileContentIndexer::run() () #8 0x00007f841a6882d3 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x00007f841a68b7be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x00007f84192ee6ba in start_thread (arg=0x7f82d0ac4700) at pthread_create.c:333 #11 0x00007f8419c9841d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f841bb7b8c0 (LWP 2759)): [KCrash Handler] #6 __memcpy_sse2_unaligned () at ../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S:38 #7 0x00007f841ad758da in Baloo::PostingCodec::decode(QByteArray const&) () from /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5 #8 0x00007f841ad61814 in Baloo::PostingDB::get(QByteArray const&) () from /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5 #9 0x00007f841ad723c6 in Baloo::WriteTransaction::commit() () from /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5 #10 0x00007f841ad6a032 in Baloo::Transaction::commit() () from /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5 #11 0x000000000042a02b in Baloo::MetadataMover::moveFileMetadata(QString const&, QString const&) () #12 0x00007f841a89abaf in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x000000000042aaba in KInotify::moved(QString const&, QString const&) () #14 0x000000000042cbff in KInotify::slotEvent(int) () #15 0x00007f841a89abaf in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x00007f841a91a24e in QSocketNotifier::activated(int, QSocketNotifier::QPrivateSignal) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x00007f841a8a71cb in QSocketNotifier::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x00007f841a86c36c in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x00007f841a8c2c95 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x00007f8416e5d197 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #21 0x00007f8416e5d3f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #22 0x00007f8416e5d49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #23 0x00007f841a8c27cf in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x00007f841a869b4a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #25 0x00007f841a871bec in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #26 0x000000000041698c in main () Possible duplicates by query: bug 356445. Reported using DrKonqi
2 year old version of baloo. Please see https://community.kde.org/Get_Involved/Bug_Reporting#Step_2:_Make_sure_it_hasn.27t_already_been_fixed