baloo_file crashes after some time in Ubuntu Bionic

Bug #1766648 reported by Lorenzo Bettini on 2018-04-24
46
This bug affects 10 people
Affects Status Importance Assigned to Milestone
baloo (Ubuntu)
Undecided
Unassigned

Bug Description

After some time of use, baloo_file crashes; after this happens, baloo has to be started again manually, but modifying any file leads to the same crash. The only way of making it work again is to "disable" it and then "enable" it, so that the index is completely recreated... thus the problem could be the index gets easily corrupted?

Application: baloo_file (5.44.0)

Qt Version: 5.9.5
Frameworks Version: 5.44.0
Operating System: Linux 4.15.0-19-generic x86_64
Distribution: Ubuntu Bionic Beaver (development branch)

-- Backtrace:
Application: Baloo File Indexing Daemon (baloo_file), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f896c49f200 (LWP 4997))]

Thread 2 (Thread 0x7f8961b02700 (LWP 5007)):
#0 0x00007f8969e51bf9 in __GI___poll (fds=0x7f895c003ce0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
#1 0x00007f89665b5439 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x00007f89665b554c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x00007f896ab3d90b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4 0x00007f896aae29ea in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5 0x00007f896a90122a in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6 0x00007f896bd51d45 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#7 0x00007f896a90616d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8 0x00007f8968e846db in start_thread (arg=0x7f8961b02700) at pthread_create.c:463
#9 0x00007f8969e5e88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 1 (Thread 0x7f896c49f200 (LWP 4997)):
[KCrash Handler]
#6 __memmove_avx_unaligned_erms () at ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:427
#7 0x00007f896b260973 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5
#8 0x00007f896b2523e4 in Baloo::PostingDB::get(QByteArray const&) () from /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5
#9 0x00007f896b25e060 in Baloo::WriteTransaction::commit() () from /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5
#10 0x00007f896b257942 in Baloo::Transaction::commit() () from /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5
#11 0x0000557479809958 in ?? ()
#12 0x00007f896ab136cf in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x00005574798120e5 in ?? ()
#14 0x000055747980797e in ?? ()
#15 0x00007f896ab136cf in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x00007f896ab20027 in QTimer::timeout(QTimer::QPrivateSignal) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x00007f896ab20388 in QTimer::timerEvent(QTimerEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#18 0x00007f896ab140db in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#19 0x00007f896aae4991 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#20 0x00007f896ab3cd8e in QTimerInfoList::activateTimers() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#21 0x00007f896ab3d551 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#22 0x00007f89665b5287 in g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#23 0x00007f89665b54c0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#24 0x00007f89665b554c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#25 0x00007f896ab3d8ef in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#26 0x00007f896aae29ea in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#27 0x00007f896aaeba84 in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#28 0x00005574797f380c in ?? ()
#29 0x00007f8969d5eb97 in __libc_start_main (main=0x5574797f3560, argc=1, argv=0x7ffdf65abf18, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffdf65abf08) at ../csu/libc-start.c:310
#30 0x00005574797f3a7a in _start ()

tags: added: bionic
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in baloo (Ubuntu):
status: New → Confirmed
John Little (john-b-little) wrote :

My crash has been avoided for now by deleting the index:

rm ~/.local/share/baloo/*

Reinstating those files from a snapshot three days ago, and resetting "first run=true", reinstates the crash. The index is 9 MiB, I could make it available if that would be useful.

So, a workaround for the crash may be to delete the index files, set first run=true in .config/baloofilerc, and restart baloo with balooctl start.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers