Created attachment 105015 [details] backtrace Hi, Almost everytime I check my messages via clawsmail I get a Baloo crash error. There are other times too some times when KDE starts and sometimes with file manager (Dolphin). For security reasons I try not to use things like nepomuk and baloo but it seems many system programs require them. I have in order to try overcome the crashes, installed other baloo packages not marked as required with no difference. When baloo crashes I have the option to enter (I think its Gdb) but dont know what to type at that prompt. I have attached list of baloo packages and last backtrace, which the auto service says does not have enough info to do.
The backtrace is missing, you only added the package list. Please also test recent versions, e.g. http://www.kubuntu.org/news/kubuntu-17-04-released/
Created attachment 105144 [details] _usr_bin_baloo_file.1001.crash Hi, Sorry, I have upgraded to 17.04 but ballo still crashes. Hope below is more helpful backtrace and I found var/crash/_usr_bin_baloo_file.1001.crash. Trying paste it causes Clawsmail to hang so Ive Attempted to attach it ****Backtrace***** Application: Baloo File Indexing Daemon (baloo_file), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f07d216c900 (LWP 1649))] Thread 2 (Thread 0x7f07c67fc700 (LWP 1687)): #0 0x00007f07cfd05cad in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x00007f07cc6dcb30 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x00007f07cc698042 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007f07cc698514 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x00007f07cc69868c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x00007f07d0936f2b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x00007f07d08e088a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x00007f07d070dfe3 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x00007f07d1af45c5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #9 0x00007f07d0712c98 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x00007f07cef616da in start_thread (arg=0x7f07c67fc700) at pthread_create.c:456 #11 0x00007f07cfd1617f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 1 (Thread 0x7f07d216c900 (LWP 1649)): [KCrash Handler] #6 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:58 #7 0x00007f07cfc4537a in __GI_abort () at abort.c:89 #8 0x00007f07cde4d0e2 in ?? () from /usr/lib/x86_64-linux-gnu/liblmdb.so.0 #9 0x00007f07cde42445 in ?? () from /usr/lib/x86_64-linux-gnu/liblmdb.so.0 #10 0x00007f07cde43643 in ?? () from /usr/lib/x86_64-linux-gnu/liblmdb.so.0 #11 0x00007f07cde438b9 in ?? () from /usr/lib/x86_64-linux-gnu/liblmdb.so.0 #12 0x00007f07cde454ef in ?? () from /usr/lib/x86_64-linux-gnu/liblmdb.so.0 #13 0x00007f07cde48742 in mdb_cursor_put () from /usr/lib/x86_64-linux-gnu/liblmdb.so.0 #14 0x00007f07cde4b2c0 in mdb_put () from /usr/lib/x86_64-linux-gnu/liblmdb.so.0 #15 0x00007f07d0fe8efc in Baloo::PostingDB::put(QByteArray const&, QVector<unsigned long long> const&) () from /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5 #16 0x00007f07d0ffb996 in Baloo::WriteTransaction::commit() () from /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5 #17 0x00007f07d0ff2402 in Baloo::Transaction::commit() () from /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5 #18 0x0000559c655b85db in ?? () #19 0x00007f07d090e81e in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x0000559c655bb7c7 in ?? () #21 0x00007f07d090e81e in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x00007f07d098846e in QSocketNotifier::activated(int, QSocketNotifier::QPrivateSignal) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #23 0x00007f07d091aa62 in QSocketNotifier::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x00007f07d08e288b in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #25 0x00007f07d09373bd in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #26 0x00007f07cc698377 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #27 0x00007f07cc6985e0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #28 0x00007f07cc69868c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #29 0x00007f07d0936f0f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #30 0x00007f07d08e088a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #31 0x00007f07d08e8ffc in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #32 0x0000559c6559ef54 in ?? () #33 0x00007f07cfc2e3f1 in __libc_start_main (main=0x559c6559ead0, argc=1, argv=0x7ffd344dedb8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, out>stack_end=0x7ffd344deda8) at ../csu/libc-start.c:291 #34 out>0x0000559c6559f01a in _start () ***End Backtrace*** On Fri, 21 Apr 2017 02:16:39 +0000 Christoph Feck <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=378750 > > Christoph Feck <cfeck@kde.org> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Severity|normal |crash > Resolution|--- |BACKTRACE > Product|BalooWidgets |frameworks-baloo > Status|UNCONFIRMED |NEEDSINFO > Component|general |general > > --- Comment #1 from Christoph Feck <cfeck@kde.org> --- > The backtrace is missing, you only added the package list. > > Please also test recent versions, e.g. > http://www.kubuntu.org/news/kubuntu-17-04-released/ >
Thanks for the update; changing status.
Created attachment 105328 [details] _usr_bin_baloo_file.1001.crash Hi, thought it useful if I sent another crash log, I have had baloo crash several times since updating to Kubuntu 17.04 but only have 1 new file in /var/crash dated 3/5/17 I have attached it for your info. On Thu, 27 Apr 2017 11:34:13 +0000 Christoph Feck <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=378750 > > Christoph Feck <cfeck@kde.org> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Version|unspecified |5.31.0 > Status|NEEDSINFO |UNCONFIRMED > Resolution|BACKTRACE |--- > > --- Comment #3 from Christoph Feck <cfeck@kde.org> --- > Thanks for the update; changing status. >
Created attachment 105436 [details] _usr_bin_baloo_file.1001.crash Hi, Thought I should contact you to say that the bug has not recurred for a week or so. Maybe another update of another package has fixed the issue. looking through synaptic history I only see linux*, libicu that may have helped. If I dont contact you again before 1st of June, You can consider the bug closed. It may be the bug was due to another package or one of the above. If it does not come up again before then it is likely your code does not have backward compatibility, and based on the newer versions of the above or other packages. I hope this is acceptable. THANKS On Thu, 27 Apr 2017 11:34:13 +0000 Christoph Feck <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=378750 > > Christoph Feck <cfeck@kde.org> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Version|unspecified |5.31.0 > Status|NEEDSINFO |UNCONFIRMED > Resolution|BACKTRACE |--- > > --- Comment #3 from Christoph Feck <cfeck@kde.org> --- > Thanks for the update; changing status. >
*** This bug has been marked as a duplicate of bug 389848 ***