Bug 366547 - baloo crashes under Awesome WM
Summary: baloo crashes under Awesome WM
Status: RESOLVED DUPLICATE of bug 352984
Alias: None
Product: frameworks-baloo
Classification: Frameworks and Libraries
Component: Engine (show other bugs)
Version: 5.21.0
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Pinak Ahuja
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2016-08-09 12:58 UTC by enno
Modified: 2016-09-11 19:22 UTC (History)
2 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 enno 2016-08-09 12:58:32 UTC
Application: baloo_file (5.21.0)

Qt Version: 5.5.1
Operating System: Linux 4.1.27-27-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed: After any kind of file change, rename, deletion, baloo crashes.

-- 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 0x7f6f51f2e780 (LWP 8331))]

Thread 2 (Thread 0x7f6e06f00700 (LWP 8334)):
#0  0x00007f6f4fa4ebfd in poll () at /lib64/libc.so.6
#1  0x00007f6f4c48fe64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x00007f6f4c48ff7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0
#3  0x00007f6f5067cd8b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#4  0x00007f6f50623d53 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#5  0x000000000041531b in  ()
#6  0x00007f6f50447382 in  () at /usr/lib64/libQt5Core.so.5
#7  0x00007f6f5044a32f in  () at /usr/lib64/libQt5Core.so.5
#8  0x00007f6f4ea8b0a4 in start_thread () at /lib64/libpthread.so.0
#9  0x00007f6f4fa5702d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f6f51f2e780 (LWP 8331)):
[KCrash Handler]
#6  0x00007f6f4d77b25c in mdb_get () at /usr/lib64/liblmdb-0.9.14.so
#7  0x00007f6f50d184cd in Baloo::IdTreeDB::get(unsigned long long) () at /usr/lib64/libKF5BalooEngine.so.5
#8  0x00007f6f50d15dc0 in Baloo::DocumentUrlDB::getId(unsigned long long, QByteArray const&) const () at /usr/lib64/libKF5BalooEngine.so.5
#9  0x00007f6f50d27949 in Baloo::Transaction::documentId(QByteArray const&) const () at /usr/lib64/libKF5BalooEngine.so.5
#10 0x000000000041d453 in  ()
#11 0x000000000041de02 in  ()
#12 0x00007f6f5065573f in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib64/libQt5Core.so.5
#13 0x000000000041e75a in  ()
#14 0x00000000004228f9 in  ()
#15 0x00007f6f5065573f in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib64/libQt5Core.so.5
#16 0x00007f6f506d78ee in QSocketNotifier::activated(int, QSocketNotifier::QPrivateSignal) () at /usr/lib64/libQt5Core.so.5
#17 0x00007f6f50662a89 in QSocketNotifier::event(QEvent*) () at /usr/lib64/libQt5Core.so.5
#18 0x00007f6f5062618d in QCoreApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5
#19 0x00007f6f50625e95 in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5
#20 0x00007f6f5067dca5 in  () at /usr/lib64/libQt5Core.so.5
#21 0x00007f6f4c48fc84 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0
#22 0x00007f6f4c48fed8 in  () at /usr/lib64/libglib-2.0.so.0
#23 0x00007f6f4c48ff7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0
#24 0x00007f6f5067cd6c in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#25 0x00007f6f50623d53 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#26 0x00007f6f5062b8f6 in QCoreApplication::exec() () at /usr/lib64/libQt5Core.so.5
#27 0x000000000040a832 in  ()
#28 0x00007f6f4f993b25 in __libc_start_main () at /lib64/libc.so.6
#29 0x000000000040a9a8 in _start ()

Possible duplicates by query: bug 359672, bug 355210, bug 353223.

Reported using DrKonqi
Comment 1 Christoph Cullmann 2016-09-11 19:22:25 UTC

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