https://bugs.kde.org/show_bug.cgi?id=432474
Bug ID: 432474
Summary: baloo_file core dump on every system boot
Product: frameworks-baloo
Version: 5.78.0
Platform: Archlinux Packages
OS: Linux
Status: REPORTED
Severity: crash
Priority: NOR
Component: Baloo File Daemon
Assignee: stefan.bru...@rwth-aachen.de
Reporter: isa...@graces.com
Target Milestone: ---
SUMMARY
I was looking through journalctl and noticed that baloo_file crashes every time
my computer boots up. However, I have not noticed any adverse affects on KDE.
ALT+F2 still shows krunner, and files are searchable (I'm not actually sure if
that's relevant).
STEPS TO REPRODUCE
1. Restart computer
2. Open terminal and execute 'journalctl -r'
3. Core dump report from systemd-coredump
OBSERVED RESULT
I have not noticed any adverse effects on my KDE experience. But baloo_file
does crash on every system boot.
When I run baloo_file from the terminal, this is the output:
isaiah@arch-tower ~ % baloo_file
[1]15908 segmentation fault (core dumped) baloo_file
EXPECTED RESULT
baloo_file probably shouldn't crash on every boot up.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux 5.10.11-arch1-1
(available in About System)
KDE Plasma Version: plasma-meta (Arch package) 5.20-1
KDE Frameworks Version: baloo 5.78.0-1
Qt Version: qt5-base (Arch package) 5.15.2-3
ADDITIONAL INFORMATION
This is the core dump report from 'journalctl -r'
-- Journal begins at Sun 2020-08-09 12:26:34 EDT, ends at Wed 2021-02-03
13:06:14 EST. --
Feb 03 11:04:35 arch-tower audit[1062]: ANOM_ABEND auid=1000 uid=1000 gid=985
ses=2 pid=1062 comm=5468726561642028706F6F6C656429 exe="/usr/bin/baloo_file"
sig=11 res=1
Feb 03 11:04:35 arch-tower kernel: audit: type=1701 audit(1612368275.023:150):
auid=1000 uid=1000 gid=985 ses=2 pid=1062 comm=5468726561642028706F6F6C656429
exe="/usr/bin/baloo_file" sig=11 res=1
Feb 03 11:04:35 arch-tower audit: BPF prog-id=28 op=LOAD
Feb 03 11:04:35 arch-tower audit: BPF prog-id=29 op=LOAD
Feb 03 11:04:35 arch-tower kernel: audit: type=1334 audit(1612368275.163:151):
prog-id=28 op=LOAD
Feb 03 11:04:35 arch-tower kernel: audit: type=1334 audit(1612368275.163:152):
prog-id=29 op=LOAD
Feb 03 11:04:35 arch-tower systemd[1]: Started Process Core Dump (PID 1762/UID
0).
Feb 03 11:04:35 arch-tower audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295
ses=4294967295 msg='unit=systemd-coredump@1-1762-0 comm="systemd"
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 03 11:04:35 arch-tower kernel: audit: type=1130 audit(1612368275.167:153):
pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@1-1762-0
comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=?
res=success'
Feb 03 11:04:35 arch-tower systemd-coredump[1763]: Process 1062 (baloo_file) of
user 1000 dumped core.
Stack trace of thread 1761:
#0 0x7f7dfb49bef9 n/a
(liblmdb.so + 0x6ef9)
#1 0x7f7dfb49c644 n/a
(liblmdb.so + 0x7644)
#2 0x7f7dfb49cc50
mdb_get (liblmdb.so + 0x7c50)
#3 0x7f7dfc96b66a
_ZN5Baloo10DocumentDB3getEy (libKF5BalooEngine.so.5 + 0xd66a)
#4 0x7f7dfc9845cc
_ZN5Baloo16WriteTransaction14removeDocumentEy (libKF5BalooEngine.so.5 +
0x265cc)
#5 0x7f7dfc98568a
_ZN5Baloo16WriteTransaction17removeRecursivelyEyRKSt8functionIFbyEE
(libKF5BalooEngine.so.5 + 0x2768a)
#6 0x7f7dfc985607
_ZN5Baloo16WriteTransaction17removeRecursivelyEyRKSt8functionIFbyEE
(libKF5BalooEngine.so.5 + 0x27607)
#7 0x7f7dfc985607
_ZN5Baloo16WriteTransaction17removeRecursivelyEyRKSt8functionIFbyEE
(libKF5BalooEngine.so.5 + 0x27607)
#8 0x7f7dfc985607
_ZN5Baloo16WriteTransaction17removeRecursivelyEyRKSt8functionIFbyEE
(libKF5BalooEngine.so.5 + 0x27607)
#9 0x7f7dfc985607
_ZN5Baloo16WriteTransaction17removeRecursivelyEyRKSt8functionIFbyEE
(libKF5BalooEngine.so.5 + 0x27607)
#10 0x7f7dfc985607
_ZN5Baloo16WriteTransaction17removeRecursivelyEyRKSt8functionIFbyEE
(libKF5BalooEngine.so.5 + 0x27607)
#11 0x7f7dfc985607
_ZN5Baloo16WriteTransaction17removeRecursivelyEyRKSt8functionIFbyEE
(libKF5BalooEngine.so.5 + 0x27607)
#12 0x7f7dfc985607
_ZN5Baloo16WriteTransaction17removeRecursivelyEyRKSt8fu
