Application: baloo_file (5.18.0) Qt Version: 5.5.1 Operating System: Linux 4.4.0-53-generic i686 Distribution: Ubuntu 16.04.1 LTS -- Information about the crash: - What I was doing when the application crashed: I reloaded the computer No other app is running now ( even not konsole ) The crash can be reproduced every time. -- Backtrace: Application: Baloo File Indexing Daemon (baloo_file), signal: Segmentation fault Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1". [KCrash Handler] #7 0xb5c591fa in mdb_txn_begin () from /usr/lib/i386-linux-gnu/liblmdb.so.0 #8 0xb74c92e9 in Baloo::Transaction::Transaction (this=0xbf9dc65c, db=..., type=Baloo::Transaction::ReadOnly) at /build/baloo-kf5-MMhumr/baloo-kf5-5.18.0/src/engine/transaction.cpp:53 #9 0xb74c93e0 in Baloo::Transaction::Transaction (this=0xbf9dc65c, db=0xb74e5240 <(anonymous namespace)::Q_QGS_s_db::innerFunction()::holder>, type=Baloo::Transaction::ReadOnly) at /build/baloo-kf5-MMhumr/baloo-kf5-5.18.0/src/engine/transaction.cpp:62 #10 0x0806551f in Baloo::FileContentIndexerProvider::size (this=0xbf9dcf7c) at /build/baloo-kf5-MMhumr/baloo-kf5-5.18.0/src/file/filecontentindexerprovider.cpp:40 #11 0x0805ed54 in Baloo::FileIndexScheduler::scheduleIndexing (this=0xbf9dcf58) at /build/baloo-kf5-MMhumr/baloo-kf5-5.18.0/src/file/fileindexscheduler.cpp:121 #12 0x0805ef75 in Baloo::FileIndexScheduler::powerManagementStatusChanged (this=0xbf9dcf58, isOnBattery=false) at /build/baloo-kf5-MMhumr/baloo-kf5-5.18.0/src/file/fileindexscheduler.cpp:177 #13 0x0805f7b6 in QtPrivate::FunctorCall<QtPrivate::IndexesList<0>, QtPrivate::List<bool>, void, void (Baloo::FileIndexScheduler::*)(bool)>::call (arg=0xbf9dc8a4, o=0xbf9dcf58, f=<optimized out>) at /usr/include/i386-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:501 #14 QtPrivate::FunctionPointer<void (Baloo::FileIndexScheduler::*)(bool)>::call<QtPrivate::List<bool>, void> (arg=0xbf9dc8a4, o=0xbf9dcf58, f=<optimized out>) at /usr/include/i386-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:520 #15 QtPrivate::QSlotObject<void (Baloo::FileIndexScheduler::*)(bool), QtPrivate::List<bool>, void>::impl (which=1, this_=0x8eba188, r=0xbf9dcf58, a=0xbf9dc8a4, ret=0x0) at /usr/include/i386-linux-gnu/qt5/QtCore/qobject_impl.h:143 #16 0xb71df080 in QtPrivate::QSlotObjectBase::call (a=0xbf9dc8a4, r=0xbf9dcf58, this=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124 #17 QMetaObject::activate (sender=0xbf9dcf84, signalOffset=3, local_signal_index=0, argv=0xbf9dc8a4) at kernel/qobject.cpp:3698 #18 0xb71df95d in QMetaObject::activate (sender=0xbf9dcf84, m=0x8094c70 <Baloo::PowerStateMonitor::staticMetaObject>, local_signal_index=0, argv=0xbf9dc8a4) at kernel/qobject.cpp:3578 #19 0x08077fd9 in Baloo::PowerStateMonitor::powerManagementStatusChanged (this=0xbf9dcf84, _t1=false) at /build/baloo-kf5-MMhumr/baloo-kf5-5.18.0/obj-i686-linux-gnu/src/file/moc_powerstatemonitor.cpp:135 #20 0x0807d964 in Baloo::PowerStateMonitor::slotPowerManagementStatusChanged (this=0xbf9dcf84, conserveResources=false) at /build/baloo-kf5-MMhumr/baloo-kf5-5.18.0/src/file/powerstatemonitor.cpp:63 #21 0x0807daf0 in Baloo::PowerStateMonitor::<lambda(QDBusPendingCallWatcher*)>::operator() (watch=0x8edfb20, __closure=<synthetic pointer>) at /build/baloo-kf5-MMhumr/baloo-kf5-5.18.0/src/file/powerstatemonitor.cpp:53 #22 QtPrivate::FunctorCall<QtPrivate::IndexesList<0>, QtPrivate::List<QDBusPendingCallWatcher*>, void, Baloo::PowerStateMonitor::PowerStateMonitor(QObject*)::<lambda(QDBusPendingCallWatcher*)> >::call (arg=0xbf9dca44, f=...) at /usr/include/i386-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:495 #23 QtPrivate::Functor<Baloo::PowerStateMonitor::PowerStateMonitor(QObject*)::<lambda(QDBusPendingCallWatcher*)>, 1>::call<QtPrivate::List<QDBusPendingCallWatcher*>, void> (arg=0xbf9dca44, f=...) at /usr/include/i386-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:552 #24 QtPrivate::QFunctorSlotObject<Baloo::PowerStateMonitor::PowerStateMonitor(QObject*)::<lambda(QDBusPendingCallWatcher*)>, 1, QtPrivate::List<QDBusPendingCallWatcher*>, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=1, this_=0x8eba258, r=0x8edfb20, a=0xbf9dca44, ret=0x0) at /usr/include/i386-linux-gnu/qt5/QtCore/qobject_impl.h:192 #25 0xb71df080 in QtPrivate::QSlotObjectBase::call (a=0xbf9dca44, r=0x8edfb20, this=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124 #26 QMetaObject::activate (sender=0x8edfb20, signalOffset=3, local_signal_index=0, argv=0xbf9dca44) at kernel/qobject.cpp:3698 #27 0xb71df95d in QMetaObject::activate (sender=0x8edfb20, m=0xb765ab7c <QDBusPendingCallWatcher::staticMetaObject>, local_signal_index=0, argv=0xbf9dca44) at kernel/qobject.cpp:3578 #28 0xb7627ac9 in QDBusPendingCallWatcher::finished (this=0x8edfb20, _t1=0x8edfb20) at .moc/moc_qdbuspendingcall.cpp:148 #29 0xb76292de in QDBusPendingCallWatcherPrivate::_q_finished (this=<optimized out>) at qdbuspendingcall.cpp:488 #30 QDBusPendingCallWatcher::qt_static_metacall (_o=0x8edfb20, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x8f57c38) at .moc/moc_qdbuspendingcall.cpp:80 #31 0xb71dc270 in QMetaCallEvent::placeMetaCall (this=0x8edfb88, object=0x8edfb20) at kernel/qobject.cpp:486 #32 0xb71e0093 in QObject::event (this=0x8edfb20, e=0x8edfb88) at kernel/qobject.cpp:1239 #33 0xb71af4ac in QCoreApplicationPrivate::notify_helper (this=0x8e42f58, receiver=0x8edfb20, event=0x8edfb88) at kernel/qcoreapplication.cpp:1093 #34 0xb71af64d in QCoreApplication::notify (event=0x8edfb88, receiver=0x8edfb20, this=0xbf9dceec) at kernel/qcoreapplication.cpp:1038 #35 QCoreApplication::notifyInternal (this=0xbf9dceec, receiver=0x8edfb20, event=0x8edfb88) at kernel/qcoreapplication.cpp:965 #36 0xb71b1d4f in QCoreApplication::sendEvent (event=0x8edfb88, receiver=<optimized out>) at kernel/qcoreapplication.h:224 #37 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x8e42fc0) at kernel/qcoreapplication.cpp:1593 #38 0xb71b2237 in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1451 #39 0xb7207553 in postEventSourceDispatch (s=0x8e43a40) at kernel/qeventdispatcher_glib.cpp:271 #40 0xb56d5ed9 in g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0 #41 0xb56d6179 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #42 0xb56d6244 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #43 0xb7207943 in QEventDispatcherGlib::processEvents (this=0x8e42e38, flags=...) at kernel/qeventdispatcher_glib.cpp:418 #44 0xb71ac7a3 in QEventLoop::processEvents (this=0xbf9dce68, flags=...) at kernel/qeventloop.cpp:128 #45 0xb71acbfa in QEventLoop::exec (this=0xbf9dce68, flags=...) at kernel/qeventloop.cpp:204 #46 0xb71b51d5 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1229 #47 0x0805aa60 in main (argc=1, argv=0xbf9dd084) at /build/baloo-kf5-MMhumr/baloo-kf5-5.18.0/src/file/main.cpp:88 Reported using DrKonqi
Application: baloo_file (5.21.0) KDE-Plasma-Version: 5.5.5 Qt Version: 5.5.1 Kernel-version: Linux 4.1.36-41-default 64-bit Distribution: openSUSE Leap 42.1 -- Information about the crash: - What I was doing when the application crashed: I reloaded the computer No other app is running now ( even not konsole ) 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 0x7fc62b403780 (LWP 2191))] Thread 2 (Thread 0x7fc4e03e7700 (LWP 2217)): #0 0x00007fc628f1abfd in poll () at /lib64/libc.so.6 #1 0x00007fc625952e64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x00007fc625952f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x00007fc629b48d8b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5 #4 0x00007fc629aefd53 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5 #5 0x000000000041531b in Baloo::FileContentIndexer::run() (this=0x2603810) at /usr/src/debug/baloo-5.21.0/src/file/filecontentindexer.cpp:73 #6 0x00007fc629913382 in () at /usr/lib64/libQt5Core.so.5 #7 0x00007fc62991632f in () at /usr/lib64/libQt5Core.so.5 #8 0x00007fc627f570a4 in start_thread () at /lib64/libpthread.so.0 #9 0x00007fc628f2302d in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7fc62b403780 (LWP 2191)): [KCrash Handler] #6 0x00007fc626c4725c in mdb_get () at /usr/lib64/liblmdb-0.9.14.so #7 0x00007fc62a1e44cd in Baloo::IdTreeDB::get(unsigned long long) () at /usr/lib64/libKF5BalooEngine.so.5 #8 0x00007fc62a1e1dc0 in Baloo::DocumentUrlDB::getId(unsigned long long, QByteArray const&) const () at /usr/lib64/libKF5BalooEngine.so.5 #9 0x00007fc62a1f3949 in Baloo::Transaction::documentId(QByteArray const&) const () at /usr/lib64/libKF5BalooEngine.so.5 #10 0x000000000041d453 in Baloo::MetadataMover::removeMetadata(Baloo::Transaction*, QString const&) (this=this@entry=0x25dfbf0, tr=tr@entry=0x7ffcfc0617e0, url=...) at /usr/src/debug/baloo-5.21.0/src/file/metadatamover.cpp:74 #11 0x000000000041de02 in Baloo::MetadataMover::moveFileMetadata(QString const&, QString const&) (this=0x25dfbf0, from=..., to=...) at /usr/src/debug/baloo-5.21.0/src/file/metadatamover.cpp:53 #12 0x00007fc629b2173f in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib64/libQt5Core.so.5 #13 0x000000000041e75a in KInotify::moved(QString const&, QString const&) (this=this@entry=0x266cf40, _t1=..., _t2=...) at /usr/src/debug/baloo-5.21.0/build/src/file/moc_kinotify.cpp:330 #14 0x00000000004228f9 in KInotify::slotEvent(int) (this=<optimized out>, socket=<optimized out>) at /usr/src/debug/baloo-5.21.0/src/file/kinotify.cpp:421 #15 0x00007fc629b2173f in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib64/libQt5Core.so.5 #16 0x00007fc629ba38ee in QSocketNotifier::activated(int, QSocketNotifier::QPrivateSignal) () at /usr/lib64/libQt5Core.so.5 #17 0x00007fc629b2ea89 in QSocketNotifier::event(QEvent*) () at /usr/lib64/libQt5Core.so.5 #18 0x00007fc629af218d in QCoreApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #19 0x00007fc629af1e95 in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #20 0x00007fc629b49ca5 in () at /usr/lib64/libQt5Core.so.5 #21 0x00007fc625952c84 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0 #22 0x00007fc625952ed8 in () at /usr/lib64/libglib-2.0.so.0 #23 0x00007fc625952f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #24 0x00007fc629b48d6c in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5 #25 0x00007fc629aefd53 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5 #26 0x00007fc629af78f6 in QCoreApplication::exec() () at /usr/lib64/libQt5Core.so.5 #27 0x000000000040a832 in main(int, char**) (argc=1, argv=<optimized out>) at /usr/src/debug/baloo-5.21.0/src/file/main.cpp:88
Comment #1 is bug 352984.
Similar problem. After a reboot, baloo almost always crashes on my first login. If I hit the Restart App button, baloo and its associated programs consume 100% of CPU. Solution is to logout, the log back in.
*** This bug has been marked as a duplicate of bug 389848 ***
This is not a duplicate.
Did a web search on the topic and one suggestion was to delete ~/.local/share/baloo. I renamed the current file to baloo.sav, then did a complete reboot. Upon login, the baloo_file_extractor did NOT crash. It ran for a while, and I could watch the index file in ~/.local/share/baloo grow. No large CPU or memory usage. After maybe a couple of minutes, index stopped growing and a check of the process table showed no instance of baloo_file_extractor. The process baloo_file did continue to run. The new ../share/baloo file only has two files: index and index.lock The saved baloo file had drwxrwxr-x. 2 bob bob 4096 May 22 15:14 calendars drwxrwxr-x. 2 bob bob 4096 Nov 30 2017 contacts drwxrwxr-x. 2 bob bob 4096 Jun 2 17:10 email drwxrwxr-x. 2 bob bob 4096 Jun 2 17:10 emailContacts -rw-r--r--. 1 bob bob 76341248 May 20 21:57 index -rw-rw-r--. 1 bob bob 8192 Jun 2 17:38 index-lock drwxrwxr-x. 2 bob bob 4096 Oct 8 2016 notes So far it does not appear that I'm missing any data. Calendars and contacts show the same data as before.
*** This bug has been marked as a duplicate of bug 352984 ***