Bug 365231 - Application 'baloo_file' crashing
Summary: Application 'baloo_file' crashing
Status: RESOLVED DUPLICATE of bug 367480
Alias: None
Product: frameworks-baloo
Classification: Frameworks and Libraries
Component: Engine (show other bugs)
Version: 5.23.0
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Pinak Ahuja
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2016-07-08 10:37 UTC by Yaroslav Sidlovsky
Modified: 2016-09-11 13:20 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Yaroslav Sidlovsky 2016-07-08 10:37:46 UTC
Application: baloo_file (5.23.0)

Qt Version: 5.6.0
Frameworks Version: 5.23.0
Operating System: Linux 4.6.2-1800.pf1.fc23.x86_64 x86_64
Distribution: "Fedora release 23 (Twenty Three)"

-- Information about the crash:
baloo_file crashing every time after logging in to the KDE session or after running 'balooctl start' from the console.

The crash can be reproduced every time.

-- Backtrace:
Application: Baloo File Indexing Daemon (baloo_file), signal: Bus error
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f86b9dc58c0 (LWP 6653))]

Thread 3 (Thread 0x7f86a7143700 (LWP 6668)):
#0  0x00007f86b7a9d70d in read () at /lib64/libc.so.6
#1  0x00007f86b32473f0 in g_wakeup_acknowledge () at /lib64/libglib-2.0.so.0
#2  0x00007f86b3203c84 in g_main_context_check () at /lib64/libglib-2.0.so.0
#3  0x00007f86b3204130 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0
#4  0x00007f86b320429c in g_main_context_iteration () at /lib64/libglib-2.0.so.0
#5  0x00007f86b8af1a4b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQt5Core.so.5
#6  0x00007f86b8a9a4ca in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQt5Core.so.5
#7  0x00007f86b88c3f34 in QThread::exec() () at /lib64/libQt5Core.so.5
#8  0x00007f86b9ee64b5 in QDBusConnectionManager::run() () at /lib64/libQt5DBus.so.5
#9  0x00007f86b88c8d48 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5
#10 0x00007f86b6b8761a in start_thread () at /lib64/libpthread.so.0
#11 0x00007f86b7aad59d in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f86a6600700 (LWP 6669)):
[KCrash Handler]
#6  0x00007f86b7a49910 in __memcpy_sse2_unaligned () at /lib64/libc.so.6
#7  0x00007f86b8fb8103 in Baloo::PostingCodec::decode(QByteArray const&) () at /lib64/libKF5BalooEngine.so.5
#8  0x00007f86b8fa34b4 in Baloo::PostingDB::get(QByteArray const&) () at /lib64/libKF5BalooEngine.so.5
#9  0x00007f86b8fb523d in Baloo::WriteTransaction::commit() () at /lib64/libKF5BalooEngine.so.5
#10 0x00007f86b8fac3b2 in Baloo::Transaction::commit() () at /lib64/libKF5BalooEngine.so.5
#11 0x0000556378cbac65 in Baloo::FirstRunIndexer::run() ()
#12 0x00007f86b88c5153 in QThreadPoolThread::run() () at /lib64/libQt5Core.so.5
#13 0x00007f86b88c8d48 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5
#14 0x00007f86b6b8761a in start_thread () at /lib64/libpthread.so.0
#15 0x00007f86b7aad59d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f86b9dc58c0 (LWP 6653)):
#0  0x00007f86b7a9d70d in read () at /lib64/libc.so.6
#1  0x00007f86b32473f0 in g_wakeup_acknowledge () at /lib64/libglib-2.0.so.0
#2  0x00007f86b3203c84 in g_main_context_check () at /lib64/libglib-2.0.so.0
#3  0x00007f86b3204130 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0
#4  0x00007f86b320429c in g_main_context_iteration () at /lib64/libglib-2.0.so.0
#5  0x00007f86b8af1a2f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQt5Core.so.5
#6  0x00007f86b8a9a4ca in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQt5Core.so.5
#7  0x00007f86b8aa2b8c in QCoreApplication::exec() () at /lib64/libQt5Core.so.5
#8  0x0000556378cb5a7c in main ()

Possible duplicates by query: bug 356445.

Reported using DrKonqi
Comment 1 Marcelo A. Caputo 2016-07-19 23:40:42 UTC
This fact occurs every time I switches on my notebook.
Comment 2 Pinak Ahuja 2016-07-20 07:38:03 UTC
Could you give me some information about your hardware? Specially the CPU.
Comment 3 Christoph Cullmann 2016-09-11 13:20:06 UTC

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