Bug 436960 - Baloo crashed after daily system update, wallpaper and desktop settings lost.
Summary: Baloo crashed after daily system update, wallpaper and desktop settings lost.
Status: RESOLVED DUPLICATE of bug 389679
Alias: None
Product: frameworks-baloo
Classification: Frameworks and Libraries
Component: Baloo File Daemon (show other bugs)
Version: 5.68.0
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Stefan Brüns
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2021-05-12 08:39 UTC by Gottfried Freudenberger
Modified: 2021-05-12 12:53 UTC (History)
3 users (show)

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 Gottfried Freudenberger 2021-05-12 08:39:32 UTC
Application: baloo_file (5.68.0)

Qt Version: 5.12.8
Frameworks Version: 5.68.0
Operating System: Linux 5.4.0-73-lowlatency x86_64
Windowing system: X11
Distribution: Ubuntu 20.04.2 LTS

-- Information about the crash:
- What I was doing when the application crashed: I had loaded the update package as of May 12, 9:20 MEST using the Update Manager included in KDE Discover. Restart was requested to implement all updates, problem occurred after restart.

- Unusual behavior I noticed: Custom Wallpaper wasn't loaded after restart, even after several attempts. Also other desktop settings (e.g. icon size) weren't correctly loaded. Crash Handler appeared in Notification Area.

- Custom settings of the application:

The crash can be reproduced every time.

-- Backtrace:
Application: Baloo File Indexing Daemon (baloo_file), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
__GI___libc_read (nbytes=16, buf=0x7ffeb9d77a50, fd=3) at ../sysdeps/unix/sysv/linux/read.c:26
[Current thread is 1 (Thread 0x7fc08361d4c0 (LWP 5457))]

Thread 3 (Thread 0x7fc0824fa700 (LWP 5648)):
[KCrash Handler]
#6  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#7  0x00007fc086eb1859 in __GI_abort () at abort.c:79
#8  0x00007fc08652ca83 in ?? () from /lib/x86_64-linux-gnu/liblmdb.so.0
#9  0x00007fc08652a205 in mdb_txn_commit () from /lib/x86_64-linux-gnu/liblmdb.so.0
#10 0x00007fc087a2eca7 in Baloo::Transaction::commit() () from /lib/x86_64-linux-gnu/libKF5BalooEngine.so.5
#11 0x000055bb6076d2fc in ?? ()
#12 0x00007fc087471f82 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x00007fc08746e9d2 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x00007fc086e6c609 in start_thread (arg=<optimized out>) at pthread_create.c:477
#15 0x00007fc086fae293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 2 (Thread 0x7fc08300d700 (LWP 5470)):
#0  0x00007fc086fa1aff in __GI___poll (fds=0x7fc07c0029e0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x00007fc085e8436e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007fc085e844a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007fc08768e583 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x00007fc0876354db in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x00007fc08746d785 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x00007fc087a64efa in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5
#7  0x00007fc08746e9d2 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x00007fc086e6c609 in start_thread (arg=<optimized out>) at pthread_create.c:477
#9  0x00007fc086fae293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 1 (Thread 0x7fc08361d4c0 (LWP 5457)):
#0  __GI___libc_read (nbytes=16, buf=0x7ffeb9d77a50, fd=3) at ../sysdeps/unix/sysv/linux/read.c:26
#1  __GI___libc_read (fd=3, buf=0x7ffeb9d77a50, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:24
#2  0x00007fc085eccb2f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007fc085e83ebe in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007fc085e84312 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007fc085e844a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x00007fc08768e565 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x00007fc0876354db in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x00007fc08763d246 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x000055bb6075b109 in ?? ()
#10 0x00007fc086eb30b3 in __libc_start_main (main=0x55bb6075ad70, argc=1, argv=0x7ffeb9d77fe8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffeb9d77fd8) at ../csu/libc-start.c:308
#11 0x000055bb6075b2be in ?? ()
[Inferior 1 (process 5457) detached]

The reporter indicates this bug may be a duplicate of or related to bug 389848.

Possible duplicates by query: bug 430455, bug 429344, bug 428123, bug 427384, bug 427224.

Reported using DrKonqi
Comment 1 tagwerk19 2021-05-12 10:45:50 UTC
Have a look at Bug 427861.

There's some discussion about desktop settings "being lost" but nothing, as far as I can tell, linking this with baloo crashing.

You could try running "balooctl monitor" in one window (to watch what is happening) and "balooctl purge" in a second. The idea being to see if there was a specific file triggering the crash.
Comment 2 Nate Graham 2021-05-12 12:53:22 UTC

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