Bug 364765

Summary: Baloo indexing daemon crashes at start-up
Product: [Frameworks and Libraries] frameworks-baloo Reporter: Steve <steverav>
Component: EngineAssignee: Pinak Ahuja <pinak.ahuja>
Status: RESOLVED DUPLICATE    
Severity: crash CC: aspotashev, christoph, pinak.ahuja
Priority: NOR Keywords: drkonqi
Version: 5.22.0   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:

Description Steve 2016-06-26 06:03:16 UTC
Application: baloo_file (5.22.0)

Qt Version: 5.6.0
Frameworks Version: 5.22.0
Operating System: Linux 4.6.2-1-pae i686
Distribution: "openSUSE Tumbleweed (20160623) (i586)"

-- Information about the crash:
- What I was doing when the application crashed:
It always occurs at boot.
No special setup, it simply crashes.

The crash can be reproduced every time.

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

Thread 2 (Thread 0xb35a4b40 (LWP 2448)):
#0  0xffffffff in QMutex::lock() () at /usr/lib/sse2/libQt5Core.so.5
#1  0xffffffff in  () at /usr/lib/sse2/libQt5Core.so.5
#2  0xffffffff in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0
#3  0xffffffff in  () at /usr/lib/libglib-2.0.so.0
#4  0xffffffff in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0
#5  0xffffffff in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/sse2/libQt5Core.so.5
#6  0xffffffff in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/sse2/libQt5Core.so.5
#7  0xffffffff in QThread::exec() () at /usr/lib/sse2/libQt5Core.so.5
#8  0xffffffff in  () at /usr/lib/libQt5DBus.so.5
#9  0xffffffff in  () at /usr/lib/sse2/libQt5Core.so.5
#10 0xffffffff in start_thread () at /lib/libpthread.so.0
#11 0xffffffff in clone () at /lib/libc.so.6

Thread 1 (Thread 0xb4f9f800 (LWP 2441)):
[KCrash Handler]
#7  0xffffffff in mdb_txn_begin () at /usr/lib/liblmdb.so
#8  0xffffffff in Baloo::Transaction::Transaction(Baloo::Database const&, Baloo::Transaction::TransactionType) () at /usr/lib/libKF5BalooEngine.so.5
#9  0xffffffff in Baloo::Transaction::Transaction(Baloo::Database*, Baloo::Transaction::TransactionType) () at /usr/lib/libKF5BalooEngine.so.5
#10 0x08069535 in  ()
#11 0xffffffff in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/sse2/libQt5Core.so.5
#12 0xffffffff in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () at /usr/lib/sse2/libQt5Core.so.5
#13 0x080733d2 in  ()
#14 0x080677ce in  ()
#15 0xffffffff in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/sse2/libQt5Core.so.5
#16 0xffffffff in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () at /usr/lib/sse2/libQt5Core.so.5
#17 0xffffffff in QTimer::timeout(QTimer::QPrivateSignal) () at /usr/lib/sse2/libQt5Core.so.5
#18 0xffffffff in QTimer::timerEvent(QTimerEvent*) () at /usr/lib/sse2/libQt5Core.so.5
#19 0xffffffff in QObject::event(QEvent*) () at /usr/lib/sse2/libQt5Core.so.5
#20 0xffffffff in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/sse2/libQt5Core.so.5
#21 0xffffffff in QTimerInfoList::activateTimers() () at /usr/lib/sse2/libQt5Core.so.5
#22 0xffffffff in  () at /usr/lib/sse2/libQt5Core.so.5
#23 0xffffffff in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0
#24 0xffffffff in  () at /usr/lib/libglib-2.0.so.0
#25 0xffffffff in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0
#26 0xffffffff in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/sse2/libQt5Core.so.5
#27 0xffffffff in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/sse2/libQt5Core.so.5
#28 0xffffffff in QCoreApplication::exec() () at /usr/lib/sse2/libQt5Core.so.5
#29 0x08050690 in  ()
#30 0xffffffff in __libc_start_main () at /lib/libc.so.6
#31 0x0805086c in _start ()

Reported using DrKonqi
Comment 1 Christoph Cullmann 2016-09-08 22:17:17 UTC

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