Bug 361009 - Baloo indexing crash
Summary: Baloo indexing crash
Status: RESOLVED DUPLICATE of bug 354342
Alias: None
Product: frameworks-baloo
Classification: Frameworks and Libraries
Component: Baloo File Daemon (show other bugs)
Version: 5.19.0
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Pinak Ahuja
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2016-03-26 11:38 UTC by Ralf Luhrmann
Modified: 2018-04-14 01:45 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ralf Luhrmann 2016-03-26 11:38:48 UTC
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:
Atfter start up. openSUSE 42.1 Leap, 64 bit, KDE5. 
Also Kontakt opens directly after starup

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".
[KCrash Handler]
#6  0x00007fb97c0d8161 in mdb_txn_begin () at /usr/lib64/liblmdb-0.9.14.so
#7  0x0000000000415853 in  ()
#8  0x000000000040e969 in  ()
#9  0x00007fb97efb473f in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib64/libQt5Core.so.5
#10 0x00007fb97efb473f in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib64/libQt5Core.so.5
#11 0x0000000000421323 in  ()
#12 0x00000000004219ba in  ()
#13 0x000000000041aa35 in  ()
#14 0x000000000041aab0 in  ()
#15 0x00007fb97efc1c48 in  () at /usr/lib64/libQt5Core.so.5
#16 0x00007fb97efb58bc in QObject::event(QEvent*) () at /usr/lib64/libQt5Core.so.5
#17 0x00007fb97ef8518d in QCoreApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5
#18 0x00007fb97ef84e95 in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5
#19 0x00007fb97efdb77d in QTimerInfoList::activateTimers() () at /usr/lib64/libQt5Core.so.5
#20 0x00007fb97efdbaa1 in  () at /usr/lib64/libQt5Core.so.5
#21 0x00007fb97adeec84 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0
#22 0x00007fb97adeeed8 in  () at /usr/lib64/libglib-2.0.so.0
#23 0x00007fb97adeef7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0
#24 0x00007fb97efdbd6c in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#25 0x00007fb97ef82d53 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#26 0x00007fb97ef8a8f6 in QCoreApplication::exec() () at /usr/lib64/libQt5Core.so.5
#27 0x000000000040a832 in  ()
#28 0x00007fb97e2f4b05 in __libc_start_main () at /lib64/libc.so.6
#29 0x000000000040a9a8 in _start ()

Reported using DrKonqi
Comment 1 Dominik Haumann 2018-04-14 01:45:54 UTC

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