https://bugs.kde.org/show_bug.cgi?id=360623
Bug ID: 360623
Summary: baloo daemon crashes every time while kontact ist
started
Product: Baloo
Version: unspecified
Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: General
Assignee: m...@vhanda.in
Reporter: bugtrac...@losch-spandau.de
CC: pinak.ah...@gmail.com
Application: baloo_file (5.19.0)
Qt Version: 5.5.1
Operating System: Linux 4.1.15-8-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"
-- Information about the crash:
- What I was doing when the application crashed:
I started kontact, firefox and konsole.
Guess kontact (kmail) causes baloo to crash with segmentation fault.
The crash can be reproduced every time.
-- Backtrace:
Application: Baloo File Indexing Daemon (baloo_file), signal: Segmentation
fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7ff2b51d1780 (LWP 1610))]
Thread 2 (Thread 0x7ff16a0ce700 (LWP 2281)):
#0 0x00007ff2b2cc7c8d in read () at /lib64/libc.so.6
#1 0x00007ff2af71bb60 in () at /usr/lib64/libglib-2.0.so.0
#2 0x00007ff2af6da999 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#3 0x00007ff2af6dadf8 in () at /usr/lib64/libglib-2.0.so.0
#4 0x00007ff2af6daf7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#5 0x00007ff2b3904d8b in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
at /usr/lib64/libQt5Core.so.5
#6 0x00007ff2b38abd53 in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at
/usr/lib64/libQt5Core.so.5
#7 0x00000000004152cd in ()
#8 0x00007ff2b36cf382 in () at /usr/lib64/libQt5Core.so.5
#9 0x00007ff2b36d232f in () at /usr/lib64/libQt5Core.so.5
#10 0x00007ff2b1cf70a4 in start_thread () at /lib64/libpthread.so.0
#11 0x00007ff2b2cd3fed in clone () at /lib64/libc.so.6
Thread 1 (Thread 0x7ff2b51d1780 (LWP 1610)):
[KCrash Handler]
#6 0x00007ff2b09d625c in mdb_get () at /usr/lib64/liblmdb-0.9.14.so
#7 0x00007ff2b3fa74cd in Baloo::IdTreeDB::get(unsigned long long) () at
/usr/lib64/libKF5BalooEngine.so.5
#8 0x00007ff2b3fa4dc0 in Baloo::DocumentUrlDB::getId(unsigned long long,
QByteArray const&) const () at /usr/lib64/libKF5BalooEngine.so.5
#9 0x00007ff2b3fb6949 in Baloo::Transaction::documentId(QByteArray const&)
const () at /usr/lib64/libKF5BalooEngine.so.5
#10 0x000000000041d3e3 in ()
#11 0x000000000041d49d in ()
#12 0x00007ff2b38dd73f in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib64/libQt5Core.so.5
#13 0x00000000004270d5 in ()
#14 0x000000000041b686 in ()
#15 0x00007ff2b38dd73f in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib64/libQt5Core.so.5
#16 0x00007ff2b38eaf22 in QTimer::timerEvent(QTimerEvent*) () at
/usr/lib64/libQt5Core.so.5
#17 0x00007ff2b38de8bc in QObject::event(QEvent*) () at
/usr/lib64/libQt5Core.so.5
#18 0x00007ff2b38ae18d in QCoreApplication::notify(QObject*, QEvent*) () at
/usr/lib64/libQt5Core.so.5
#19 0x00007ff2b38ade95 in QCoreApplication::notifyInternal(QObject*, QEvent*)
() at /usr/lib64/libQt5Core.so.5
#20 0x00007ff2b390477d in QTimerInfoList::activateTimers() () at
/usr/lib64/libQt5Core.so.5
#21 0x00007ff2b3904ad9 in () at /usr/lib64/libQt5Core.so.5
#22 0x00007ff2af6dac84 in g_main_context_dispatch () at
/usr/lib64/libglib-2.0.so.0
#23 0x00007ff2af6daed8 in () at /usr/lib64/libglib-2.0.so.0
#24 0x00007ff2af6daf7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#25 0x00007ff2b3904d6c in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
at /usr/lib64/libQt5Core.so.5
#26 0x00007ff2b38abd53 in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at
/usr/lib64/libQt5Core.so.5
#27 0x00007ff2b38b38f6 in QCoreApplication::exec() () at
/usr/lib64/libQt5Core.so.5
#28 0x000000000040a832 in ()
#29 0x00007ff2b2c10b05 in __libc_start_main () at /lib64/libc.so.6
#30 0x000000000040a9a8 in _start ()
Possible duplicates by query: bug 359672, bug 355210, bug 353223.
Reported using DrKonqi
--
You are receiving this mail because:
You are watching all bug changes.
