Bug 360523 - Baloo crashes on system boot
Summary: Baloo crashes on system boot
Status: RESOLVED DUPLICATE of bug 367480
Alias: None
Product: frameworks-baloo
Classification: Frameworks and Libraries
Component: Baloo File Daemon (show other bugs)
Version: 5.19.0
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Pinak Ahuja
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2016-03-14 15:35 UTC by Jonathan Ryshpan
Modified: 2016-09-11 13:41 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 Jonathan Ryshpan 2016-03-14 15:35:13 UTC
Application: baloo_file_extractor (5.19.0)

Qt Version: 5.5.1
Operating System: Linux 4.4.4-301.fc23.x86_64 x86_64
Distribution: "Fedora release 23 (Twenty Three)"

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

I had just rebooted the computer.  To repeat, this happens every time the system is booted.

The crash can be reproduced every time.

-- Backtrace:
Application: Baloo File Extractor (baloo_file_extractor), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7eff1184b8c0 (LWP 2405))]

Thread 2 (Thread 0x7efefa64f700 (LWP 2406)):
#0  0x00007eff0ddf4fdd in poll () at /lib64/libc.so.6
#1  0x00007eff084a9272 in _xcb_conn_wait () at /lib64/libxcb.so.1
#2  0x00007eff084aaee7 in xcb_wait_for_event () at /lib64/libxcb.so.1
#3  0x00007efefd9c1da9 in QXcbEventReader::run() () at /lib64/libQt5XcbQpa.so.5
#4  0x00007eff0e9fd3de in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5
#5  0x00007eff0cf0660a in start_thread () at /lib64/libpthread.so.0
#6  0x00007eff0de00a4d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7eff1184b8c0 (LWP 2405)):
[KCrash Handler]
#5  0x00007eff0de46af7 in __memcpy_avx_unaligned () at /lib64/libc.so.6
#6  0x00007eff10b67ca2 in Baloo::PostingCodec::decode(QByteArray const&) () at /lib64/libKF5BalooEngine.so.5
#7  0x00007eff10b50224 in Baloo::PostingDB::get(QByteArray const&) () at /lib64/libKF5BalooEngine.so.5
#8  0x00007eff10b6407d in Baloo::WriteTransaction::commit() () at /lib64/libKF5BalooEngine.so.5
#9  0x00007eff10b5a4c2 in Baloo::Transaction::commit() () at /lib64/libKF5BalooEngine.so.5
#10 0x000055b48b7360dc in Baloo::App::processNextFile() ()
#11 0x00007eff0ec19888 in QSingleShotTimer::timerEvent(QTimerEvent*) () at /lib64/libQt5Core.so.5
#12 0x00007eff0ec0e113 in QObject::event(QEvent*) () at /lib64/libQt5Core.so.5
#13 0x00007eff0f8c341c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5
#14 0x00007eff0f8c88e6 in QApplication::notify(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5
#15 0x00007eff0ebde73b in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /lib64/libQt5Core.so.5
#16 0x00007eff0ec33ccd in QTimerInfoList::activateTimers() () at /lib64/libQt5Core.so.5
#17 0x00007eff0ec34209 in idleTimerSourceDispatch(_GSource*, int (*)(void*), void*) () at /lib64/libQt5Core.so.5
#18 0x00007eff0c76de3a in g_main_context_dispatch () at /lib64/libglib-2.0.so.0
#19 0x00007eff0c76e1d0 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0
#20 0x00007eff0c76e27c in g_main_context_iteration () at /lib64/libglib-2.0.so.0
#21 0x00007eff0ec34eaf in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQt5Core.so.5
#22 0x00007eff0ebdbeca in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQt5Core.so.5
#23 0x00007eff0ebe3fac in QCoreApplication::exec() () at /lib64/libQt5Core.so.5
#24 0x000055b48b7349d5 in main ()

Reported using DrKonqi
Comment 1 Pinak Ahuja 2016-03-15 16:31:00 UTC
could you run 
'balooctl checkDb'
and get back with the results.
Comment 2 Christoph Cullmann 2016-09-11 13:41:28 UTC

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