Bug 399851

Summary:	Baloo crashes after downloading a file with Firefox
Product:	[Frameworks and Libraries] frameworks-baloo	Reporter:	Matej Mrenica <matejm98mthw>
Component:	Baloo File Daemon	Assignee:	baloo-bugs-null
Status:	RESOLVED DUPLICATE
Severity:	crash	CC:	matejm98mthw, nate
Priority:	NOR
Version:	5.51.0
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Matej Mrenica 2018-10-15 18:33:19 UTC

SUMMARY


STEPS TO REPRODUCE
1. Download a file with Firefox
2. 
3. 

OBSERVED RESULT
Baloo crashes

EXPECTED RESULT
Baloo shouldn't crash

SOFTWARE VERSIONS
(available in About System)
KDE Plasma Version: 5.14.0
KDE Frameworks Version: 5.51
Qt Version: 5.12-beta1

ADDITIONAL INFORMATION
Very likely a duplicate

Comment 1 Matej Mrenica 2018-10-15 18:33:55 UTC

Application: Baloo File Indexing Daemon (baloo_file), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f87fd787800 (LWP 7763))]

Thread 3 (Thread 0x7f87fc98e700 (LWP 8655)):
[KCrash Handler]
#6  0x00007f88012095f4 in mdb_midl_xmerge () from /usr/lib/liblmdb.so
#7  0x00007f8801200c8f in ?? () from /usr/lib/liblmdb.so
#8  0x00007f8801201129 in ?? () from /usr/lib/liblmdb.so
#9  0x00007f8801202d54 in ?? () from /usr/lib/liblmdb.so
#10 0x00007f8801205f0e in mdb_cursor_put () from /usr/lib/liblmdb.so
#11 0x00007f8801208adb in mdb_put () from /usr/lib/liblmdb.so
#12 0x00007f880309cb53 in Baloo::DocumentDB::put(unsigned long long, QVector<QByteArray> const&) () from /usr/lib/libKF5BalooEngine.so.5
#13 0x00007f88030c13c8 in Baloo::WriteTransaction::addDocument(Baloo::Document const&) () from /usr/lib/libKF5BalooEngine.so.5
#14 0x0000555778274c5a in ?? ()
#15 0x00007f8802b37961 in ?? () from /usr/lib/libQt5Core.so.5
#16 0x00007f8802b3398c in ?? () from /usr/lib/libQt5Core.so.5
#17 0x00007f8801eb8a9d in start_thread () from /usr/lib/libpthread.so.0
#18 0x00007f8802698a43 in clone () from /usr/lib/libc.so.6

Thread 2 (Thread 0x7f87fd4a1700 (LWP 7774)):
#0  0x00007f880090b699 in g_private_get () from /usr/lib/libglib-2.0.so.0
#1  0x00007f880092bb11 in g_thread_self () from /usr/lib/libglib-2.0.so.0
#2  0x00007f880095cfbf in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#3  0x00007f8802d453c4 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5
#4  0x00007f8802cee3fc in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5
#5  0x00007f8802b32589 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#6  0x00007f880317bba6 in ?? () from /usr/lib/libQt5DBus.so.5
#7  0x00007f8802b3398c in ?? () from /usr/lib/libQt5Core.so.5
#8  0x00007f8801eb8a9d in start_thread () from /usr/lib/libpthread.so.0
#9  0x00007f8802698a43 in clone () from /usr/lib/libc.so.6

Thread 1 (Thread 0x7f87fd787800 (LWP 7763)):
#0  0x00007f880268dbb1 in poll () from /usr/lib/libc.so.6
#1  0x00007f880095cee0 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x00007f880095cfce in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#3  0x00007f8802d453c4 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5
#4  0x00007f8802cee3fc in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5
#5  0x00007f8802cf6706 in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5
#6  0x000055577826c3f4 in ?? ()
#7  0x00007f88025c1223 in __libc_start_main () from /usr/lib/libc.so.6
#8  0x000055577826c59e in _start ()
[Inferior 1 (process 7763) detached]

Comment 2 Matej Mrenica 2018-10-15 18:41:40 UTC

Also happens with Chromium but not with Falkon, so maybe we can generalize it to gtk apps?

Comment 3 Nate Graham 2018-10-17 14:40:26 UTC

Sadly Arch does not provide symbols and the backtrace is useless without symbols. Can you get symbols, reproduce the crash, and attach a symbolicated backtrace? See https://wiki.archlinux.org/index.php/Debug_-_Getting_Traces

Comment 4 Matej Mrenica 2018-10-17 15:52:11 UTC

(In reply to Nate Graham from comment #3)
> Sadly Arch does not provide symbols and the backtrace is useless without
> symbols. Can you get symbols, reproduce the crash, and attach a symbolicated
> backtrace? See https://wiki.archlinux.org/index.php/Debug_-_Getting_Traces

I will try to rebuild. What packages exactly do I need to rebuild? I would guess baloo, but what else?

Comment 5 Nate Graham 2018-10-17 15:53:32 UTC

The crash is somewhere in liblmdb.so, so also whatever package provides the LMDB library.

Comment 6 Nate Graham 2018-10-17 15:55:01 UTC

Never mind, found the original.

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

Comment 7 Matej Mrenica 2018-10-17 16:11:12 UTC

(In reply to Nate Graham from comment #6)
> Never mind, found the original.
> 
> *** This bug has been marked as a duplicate of bug 353483 ***

I have a new log, should I post there?

Comment 8 Nate Graham 2018-10-17 16:15:08 UTC

Sure, go ahead!

Comment 9 Nate Graham 2018-10-17 16:15:27 UTC


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

Comment 10 Nate Graham 2018-11-26 18:13:17 UTC


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