Application: baloo_file (5.15.0) Qt Version: 5.5.1 Operating System: Linux 4.3.0-1-default x86_64 Distribution: "openSUSE Tumbleweed (20151106) (x86_64)" -- Information about the crash: I started KDE. I didn't do anything elese before Baloo crashed. The crash can be reproduced sometimes. -- Backtrace: Application: Baloo File Indexing Daemon (baloo_file), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fe9e4be1840 (LWP 1793))] Thread 2 (Thread 0x7fe8993da700 (LWP 1956)): #0 0x00007fe9df1454b9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0 #1 0x00007fe9df10224a in () at /usr/lib64/libglib-2.0.so.0 #2 0x00007fe9df10236c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x00007fe9e337a52b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5 #4 0x00007fe9e332463a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5 #5 0x0000000000420cb8 in Baloo::FileContentIndexer::run() (this=0x165eae0) at /usr/src/debug/baloo-5.15.0/src/file/filecontentindexer.cpp:70 #6 0x00007fe9e3152533 in () at /usr/lib64/libQt5Core.so.5 #7 0x00007fe9e315594f in () at /usr/lib64/libQt5Core.so.5 #8 0x00007fe9e17a44a4 in start_thread () at /lib64/libpthread.so.0 #9 0x00007fe9e276eb5d in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7fe9e4be1840 (LWP 1793)): [KCrash Handler] #6 0x00007fe9e27174c9 in __memcpy_sse2_unaligned () at /lib64/libc.so.6 #7 0x00007fe9e3a034a5 in Baloo::IdTreeDB::get(unsigned long long) () at /usr/lib64/libKF5BalooEngine.so.5 #8 0x00007fe9e3a00120 in Baloo::DocumentUrlDB::getId(unsigned long long, QByteArray const&) const () at /usr/lib64/libKF5BalooEngine.so.5 #9 0x00007fe9e3a13361 in Baloo::Transaction::documentId(QByteArray const&) const () at /usr/lib64/libKF5BalooEngine.so.5 #10 0x0000000000428bc0 in Baloo::MetadataMover::removeMetadata(Baloo::Transaction*, QString const&) (this=this@entry=0x1619450, tr=tr@entry=0x7ffd843bea40, url=...) at /usr/src/debug/baloo-5.15.0/src/file/metadatamover.cpp:74 #11 0x0000000000428c7d in Baloo::MetadataMover::removeFileMetadata(QString const&) (this=0x1619450, file=...) at /usr/src/debug/baloo-5.15.0/src/file/metadatamover.cpp:66 #12 0x00007fe9e3353e17 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib64/libQt5Core.so.5 #13 0x0000000000431fa5 in Baloo::PendingFileQueue::removeFileIndex(QString const&) (this=this@entry=0x165f580, _t1=...) at /usr/src/debug/baloo-5.15.0/build/src/file/moc_pendingfilequeue.cpp:217 #14 0x0000000000426e96 in Baloo::PendingFileQueue::processCache() (this=0x165f580) at /usr/src/debug/baloo-5.15.0/src/file/pendingfilequeue.cpp:89 #15 0x00007fe9e3353e17 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib64/libQt5Core.so.5 #16 0x00007fe9e33600e8 in QTimer::timerEvent(QTimerEvent*) () at /usr/lib64/libQt5Core.so.5 #17 0x00007fe9e3354d2b in QObject::event(QEvent*) () at /usr/lib64/libQt5Core.so.5 #18 0x00007fe9e3326ccc in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #19 0x00007fe9e33793bd in QTimerInfoList::activateTimers() () at /usr/lib64/libQt5Core.so.5 #20 0x00007fe9e3379909 in () at /usr/lib64/libQt5Core.so.5 #21 0x00007fe9df102097 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0 #22 0x00007fe9df1022c8 in () at /usr/lib64/libglib-2.0.so.0 #23 0x00007fe9df10236c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #24 0x00007fe9e337a50f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5 #25 0x00007fe9e332463a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5 #26 0x00007fe9e332c2fd in QCoreApplication::exec() () at /usr/lib64/libQt5Core.so.5 #27 0x0000000000417036 in main(int, char**) (argc=1, argv=<optimized out>) at /usr/src/debug/baloo-5.15.0/src/file/main.cpp:88 Possible duplicates by query: bug 355371. Reported using DrKonqi
*** Bug 355371 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of bug 355881 ***