Bug 370905

Summary: Baloo crashes upon file removal
Product: [Frameworks and Libraries] frameworks-baloo Reporter: gerben.jansen
Component: Baloo File DaemonAssignee: Pinak Ahuja <pinak.ahuja>
Status: RESOLVED DUPLICATE    
Severity: crash Keywords: drkonqi
Priority: NOR    
Version: 5.21.0   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description gerben.jansen 2016-10-15 08:28:47 UTC
Application: baloo_file (5.21.0)

Qt Version: 5.5.1
Operating System: Linux 4.1.31-30-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:

Just removed a file with "rm file"

I can not reproduce this at will, but it happens on a regular basis. Also file removal with other tools (like konqueror) can lead to Baloo crashes

I'm run OpenSuSE 42.1 in x86_64

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 0x7fa3d7e65780 (LWP 1885))]

Thread 2 (Thread 0x7fa28ce66700 (LWP 2003)):
#0  0x00007fa3d5982bfd in poll () at /lib64/libc.so.6
#1  0x00007fa3d23c3e64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x00007fa3d23c3f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0
#3  0x00007fa3d65b0d8b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#4  0x00007fa3d6557d53 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#5  0x000000000041531b in  ()
#6  0x00007fa3d637b382 in  () at /usr/lib64/libQt5Core.so.5
#7  0x00007fa3d637e32f in  () at /usr/lib64/libQt5Core.so.5
#8  0x00007fa3d49bf0a4 in start_thread () at /lib64/libpthread.so.0
#9  0x00007fa3d598b02d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7fa3d7e65780 (LWP 1885)):
[KCrash Handler]
#6  0x00007fa3d36af25c in mdb_get () at /usr/lib64/liblmdb-0.9.14.so
#7  0x00007fa3d6c4c4cd in Baloo::IdTreeDB::get(unsigned long long) () at /usr/lib64/libKF5BalooEngine.so.5
#8  0x00007fa3d6c49dc0 in Baloo::DocumentUrlDB::getId(unsigned long long, QByteArray const&) const () at /usr/lib64/libKF5BalooEngine.so.5
#9  0x00007fa3d6c5b949 in Baloo::Transaction::documentId(QByteArray const&) const () at /usr/lib64/libKF5BalooEngine.so.5
#10 0x000000000041d453 in  ()
#11 0x000000000041d50d in  ()
#12 0x00007fa3d658973f in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib64/libQt5Core.so.5
#13 0x0000000000427145 in  ()
#14 0x000000000041b6f6 in  ()
#15 0x00007fa3d658973f in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib64/libQt5Core.so.5
#16 0x00007fa3d6596f22 in QTimer::timerEvent(QTimerEvent*) () at /usr/lib64/libQt5Core.so.5
#17 0x00007fa3d658a8bc in QObject::event(QEvent*) () at /usr/lib64/libQt5Core.so.5
#18 0x00007fa3d655a18d in QCoreApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5
#19 0x00007fa3d6559e95 in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5
#20 0x00007fa3d65b077d in QTimerInfoList::activateTimers() () at /usr/lib64/libQt5Core.so.5
#21 0x00007fa3d65b0aa1 in  () at /usr/lib64/libQt5Core.so.5
#22 0x00007fa3d23c3c84 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0
#23 0x00007fa3d23c3ed8 in  () at /usr/lib64/libglib-2.0.so.0
#24 0x00007fa3d23c3f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0
#25 0x00007fa3d65b0d6c in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#26 0x00007fa3d6557d53 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#27 0x00007fa3d655f8f6 in QCoreApplication::exec() () at /usr/lib64/libQt5Core.so.5
#28 0x000000000040a832 in  ()
#29 0x00007fa3d58c7b25 in __libc_start_main () at /lib64/libc.so.6
#30 0x000000000040a9a8 in _start ()

Possible duplicates by query: bug 359672, bug 355210.

Reported using DrKonqi
Comment 1 Christoph Feck 2017-03-24 22:24:36 UTC

*** This bug has been marked as a duplicate of bug 352984 ***