Bug 372328 - baloo
Summary: baloo
Status: RESOLVED DUPLICATE of bug 352984
Alias: None
Product: frameworks-baloo
Classification: Frameworks and Libraries
Component: Baloo File Daemon (show other bugs)
Version: 5.21.0
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Pinak Ahuja
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2016-11-11 07:46 UTC by AlexURS
Modified: 2017-03-24 22:25 UTC (History)
0 users

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 AlexURS 2016-11-11 07:46:52 UTC
Application: baloo_file (5.21.0)

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

-- Information about the crash:
- What I was doing when the application crashed:
after restart system and start this
я просто перезагружаю систему и это появляется

-- 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 0x7f5b695c5780 (LWP 2149))]

Thread 2 (Thread 0x7f5a1e5c5700 (LWP 2436)):
#0  0x00007f5b670e1bfd in poll () at /lib64/libc.so.6
#1  0x00007f5b63b22e64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x00007f5b63b22f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0
#3  0x00007f5b67d0fd8b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#4  0x00007f5b67cb6d53 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#5  0x000000000041531b in  ()
#6  0x00007f5b67ada382 in  () at /usr/lib64/libQt5Core.so.5
#7  0x00007f5b67add32f in  () at /usr/lib64/libQt5Core.so.5
#8  0x00007f5b6611e0a4 in start_thread () at /lib64/libpthread.so.0
#9  0x00007f5b670ea02d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f5b695c5780 (LWP 2149)):
[KCrash Handler]
#6  0x00007f5b64e0e25c in mdb_get () at /usr/lib64/liblmdb-0.9.14.so
#7  0x00007f5b683ab4cd in Baloo::IdTreeDB::get(unsigned long long) () at /usr/lib64/libKF5BalooEngine.so.5
#8  0x00007f5b683a8dc0 in Baloo::DocumentUrlDB::getId(unsigned long long, QByteArray const&) const () at /usr/lib64/libKF5BalooEngine.so.5
#9  0x00007f5b683ba949 in Baloo::Transaction::documentId(QByteArray const&) const () at /usr/lib64/libKF5BalooEngine.so.5
#10 0x000000000041d453 in  ()
#11 0x000000000041d50d in  ()
#12 0x00007f5b67ce873f in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib64/libQt5Core.so.5
#13 0x0000000000427145 in  ()
#14 0x000000000041b6f6 in  ()
#15 0x00007f5b67ce873f in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib64/libQt5Core.so.5
#16 0x00007f5b67cf5f22 in QTimer::timerEvent(QTimerEvent*) () at /usr/lib64/libQt5Core.so.5
#17 0x00007f5b67ce98bc in QObject::event(QEvent*) () at /usr/lib64/libQt5Core.so.5
#18 0x00007f5b67cb918d in QCoreApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5
#19 0x00007f5b67cb8e95 in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5
#20 0x00007f5b67d0f77d in QTimerInfoList::activateTimers() () at /usr/lib64/libQt5Core.so.5
#21 0x00007f5b67d0fad9 in  () at /usr/lib64/libQt5Core.so.5
#22 0x00007f5b63b22c84 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0
#23 0x00007f5b63b22ed8 in  () at /usr/lib64/libglib-2.0.so.0
#24 0x00007f5b63b22f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0
#25 0x00007f5b67d0fd6c in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#26 0x00007f5b67cb6d53 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#27 0x00007f5b67cbe8f6 in QCoreApplication::exec() () at /usr/lib64/libQt5Core.so.5
#28 0x000000000040a832 in  ()
#29 0x00007f5b67026b25 in __libc_start_main () at /lib64/libc.so.6
#30 0x000000000040a9a8 in _start ()

Possible duplicates by query: bug 359672, bug 355210.

Reported using DrKonqi
Comment 1 Christoph Feck 2017-03-24 22:25:24 UTC

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