Bug 378582

Summary: Baloon Notification Tool crashed when finishing download
Product: [Frameworks and Libraries] frameworks-baloo Reporter: Ralf Grauer <ralf.grauer>
Component: Baloo File DaemonAssignee: Pinak Ahuja <pinak.ahuja>
Status: RESOLVED DUPLICATE    
Severity: crash Keywords: drkonqi
Priority: NOR    
Version: 5.18.0   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:

Description Ralf Grauer 2017-04-09 11:42:40 UTC
Application: baloo_file (5.18.0)

Qt Version: 5.5.1
Operating System: Linux 4.8.0-46-generic x86_64
Distribution: Ubuntu 16.04.2 LTS

-- Information about the crash:
- What I was doing when the application crashed:
My Browser has finished a download of file. 
Then opens a dialog immediatly to notificate the crash of the notification program.

The crash can be reproduced every time.

-- 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 0x7f9b4429d8c0 (LWP 1499))]

Thread 2 (Thread 0x7f99f901b700 (LWP 2762)):
[KCrash Handler]
#6  __memcpy_avx_unaligned () at ../sysdeps/x86_64/multiarch/memcpy-avx-unaligned.S:163
#7  0x00007f9b4348c8da in Baloo::PostingCodec::decode(QByteArray const&) () from /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5
#8  0x00007f9b43478814 in Baloo::PostingDB::get(QByteArray const&) () from /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5
#9  0x00007f9b434893c6 in Baloo::WriteTransaction::commit() () from /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5
#10 0x00007f9b43481032 in Baloo::Transaction::commit() () from /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5
#11 0x000000000041c8e0 in Baloo::NewFileIndexer::run() ()
#12 0x00007f9b42d9f2d3 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x00007f9b42da27be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x00007f9b41a066ba in start_thread (arg=0x7f99f901b700) at pthread_create.c:333
#15 0x00007f9b423af82d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f9b4429d8c0 (LWP 1499)):
#0  0x00007f9b4239f69d in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x00007f9b3f5b76f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f9b3f573e74 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f9b3f574330 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007f9b3f57449c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007f9b42fd97cf in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x00007f9b42f80b4a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x00007f9b42f88bec in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x000000000041698c in main ()

Reported using DrKonqi
Comment 1 Christoph Feck 2017-07-17 20:19:01 UTC

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