Bug 361422 - baloo crashing then QTCreator Run
Summary: baloo crashing then QTCreator Run
Status: RESOLVED DUPLICATE of bug 352984
Alias: None
Product: frameworks-baloo
Classification: Frameworks and Libraries
Component: Engine (show other bugs)
Version: 5.16.0
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Pinak Ahuja
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2016-04-05 19:11 UTC by Alexander K
Modified: 2016-09-11 19:23 UTC (History)
3 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 Alexander K 2016-04-05 19:11:53 UTC
Application: baloo_file (5.16.0)

Qt Version: 5.5.1
Operating System: Linux 4.3.3-1-default x86_64
Distribution: "openSUSE Tumbleweed (20151201) (x86_64)"

-- Information about the crash:
- baloo crash then I make new project for Window aplication in QTCreator5

-- 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 0x7ff1d15d38c0 (LWP 2034))]

Thread 2 (Thread 0x7ff0852e4700 (LWP 2470)):
#0  0x00007ff1cf11e20d in poll () at /lib64/libc.so.6
#1  0x00007ff1cba89264 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x00007ff1cba8936c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0
#3  0x00007ff1cfd3b52b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#4  0x00007ff1cfce563a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#5  0x00000000004216b0 in Baloo::FileContentIndexer::run() ()
#6  0x00007ff1cfb13533 in  () at /usr/lib64/libQt5Core.so.5
#7  0x00007ff1cfb1694f in  () at /usr/lib64/libQt5Core.so.5
#8  0x00007ff1ce14c4a4 in start_thread () at /lib64/libpthread.so.0
#9  0x00007ff1cf126b9d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7ff1d15d38c0 (LWP 2034)):
[KCrash Handler]
#6  0x00007ff1cce1c418 in mdb_get () at /usr/lib64/liblmdb-0.9.16.so
#7  0x00007ff1d03ce39d in Baloo::IdTreeDB::get(unsigned long long) () at /usr/lib64/libKF5BalooEngine.so.5
#8  0x00007ff1d03cb080 in Baloo::DocumentUrlDB::getId(unsigned long long, QByteArray const&) const () at /usr/lib64/libKF5BalooEngine.so.5
#9  0x00007ff1d03ddc71 in Baloo::Transaction::documentId(QByteArray const&) const () at /usr/lib64/libKF5BalooEngine.so.5
#10 0x0000000000429860 in Baloo::MetadataMover::removeMetadata(Baloo::Transaction*, QString const&) ()
#11 0x000000000042a202 in Baloo::MetadataMover::moveFileMetadata(QString const&, QString const&) ()
#12 0x00007ff1cfd14e17 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib64/libQt5Core.so.5
#13 0x000000000042ab4a in KInotify::moved(QString const&, QString const&) ()
#14 0x000000000042cb54 in KInotify::slotEvent(int) ()
#15 0x00007ff1cfd14e17 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib64/libQt5Core.so.5
#16 0x00007ff1cfd9039e in QSocketNotifier::activated(int, QSocketNotifier::QPrivateSignal) () at /usr/lib64/libQt5Core.so.5
#17 0x00007ff1cfd20d0b in QSocketNotifier::event(QEvent*) () at /usr/lib64/libQt5Core.so.5
#18 0x00007ff1cfce7ccc in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5
#19 0x00007ff1cfd3b9bd in  () at /usr/lib64/libQt5Core.so.5
#20 0x00007ff1cba89097 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0
#21 0x00007ff1cba892c8 in  () at /usr/lib64/libglib-2.0.so.0
#22 0x00007ff1cba8936c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0
#23 0x00007ff1cfd3b50f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#24 0x00007ff1cfce563a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#25 0x00007ff1cfced2fd in QCoreApplication::exec() () at /usr/lib64/libQt5Core.so.5
#26 0x0000000000417906 in main ()

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

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

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