https://bugs.kde.org/show_bug.cgi?id=417976
Bug ID: 417976
Summary: Baloo got a complete crash with stack trace ; it is
probably involved in system freezes and OS crashes
Product: frameworks-baloo
Version: 5.67.0
Platform: Archlinux Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Baloo File Daemon
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
SUMMARY
There's a crash report visible in systemctl
STEPS TO REPRODUCE
1. Nothing specific, just use the computer and at some point it crashes.
2.
3.
OBSERVED RESULT
System freez or crashes. The freezes and crashes might be unrelated, I can't
know for sure
EXPECTED RESULT
No crash.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: ArchLinux, Plasma 5.18.1
(available in About System)
KDE Plasma Version: 5.18.1
No other informations as I can't have them by the about menu: I installed
several DE/WM on this computer and sometimes use one or another. The current
crash report happened on a Gnome session, but it seems that Baloo service is
anyway running everytime once instealled with the KDE DE, whether it's a KDE
session or not.
ADDITIONAL INFORMATION
The system is encrypted through LUKS, which might explain heavier resource
usage.
Here's the stacktrace from journalctl:
Feb 19 00:28:10 T470-clement systemd-coredump[46933]: Process 46873
(baloo_file) of user 1000 dumped core.
Stack trace of thread
46880:
#0 0x00007f9592f89ce5
raise (libc.so.6 + 0x3bce5)
#1 0x00007f9593bdb6b0
_ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x46b0)
#2 0x00007f9592f89d70
__restore_rt (libc.so.6 + 0x3bd70)
#3 0x00007f9592f89ce5
raise (libc.so.6 + 0x3bce5)
#4 0x00007f9592f73857
abort (libc.so.6 + 0x25857)
#5 0x00007f959252a753
n/a (liblmdb.so + 0x10753)
#6 0x00007f95925229a3
n/a (liblmdb.so + 0x89a3)
#7 0x00007f9592525d61
mdb_cursor_put (liblmdb.so + 0xbd61)
#8 0x00007f95925284ab
mdb_put (liblmdb.so + 0xe4ab)
#9 0x00007f9593aa64d2
_ZN5Baloo10PositionDB3putERK10QByteArrayRK7QVectorINS_12PositionInfoEE
(libKF5BalooEngine.so.5 + 0x284d2)
#10 0x00007f9593ac2551
_ZN5Baloo16WriteTransaction6commitEv (libKF5BalooEngine.so.5 + 0x44551)
#11 0x00007f9593ab1e50
_ZN5Baloo11Transaction6commitEv (libKF5BalooEngine.so.5 + 0x33e50)
#12 0x0000556a44cc06a5
n/a (baloo_file + 0x196a5)
#13 0x00007f95935101f2
n/a (libQt5Core.so.5 + 0xcd1f2)
#14 0x00007f959350cfc6
n/a (libQt5Core.so.5 + 0xc9fc6)
#15 0x00007f959258546f
start_thread (libpthread.so.0 + 0x946f)
#16 0x00007f959304d3d3
__clone (libc.so.6 + 0xff3d3)
Stack trace of thread
46876:
#0 0x00007f9593042abf
__poll (libc.so.6 + 0xf4abf)
#1 0x00007f9591d62120
n/a (libglib-2.0.so.0 + 0x6c120)
#2 0x00007f9591d621f1
g_main_context_iteration (libglib-2.0.so.0 + 0x6c1f1)
#3 0x00007f9593741020
_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE
(libQt5Core.so.5 + 0x2fe020)
#4 0x00007f95936e74cc
_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 +
0x2a44cc)
#5 0x00007f959350be52
_ZN7QThread4execEv (libQt5Core.so.5 + 0xc8e52)
#6 0x00007f9593ae3b28
n/a (libQt5DBus.so.5 + 0x15b28)
#7 0x00007f959350cfc6
n/a (libQt5Core.so.5 + 0xc9fc6)
#8 0x00007f959258546f
start_thread (libpthread.so.0 + 0x946f)
#9 0x00007f959304d3d3
__clone (libc.so.6 + 0xff3d3)
Stack trace of thread
46873:
#0 0x00007f9593042abf
__poll (libc.so.6 + 0xf4abf)
#1 0x00007f9591d62120
n/a (libglib-2.0.so.0 + 0x6c120)
#2 0x00007f9591d621f1
g_main_context_iteration (libglib-2.0.so.0 + 0x6c1f1)
#3 0x00007f9593741020
_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE
(libQt5Core.so.5 + 0x2fe020)
#4 0x00007f95936e74cc
_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 +
0x2a44cc)
#5 0x00007f95936ef4d6
_ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x2ac4d6)
#6 0x0000556a44cb4402
n/a (baloo_file + 0xd402)
#7 0x00007f9592f75023
__libc_start_main (libc.so.6 + 0x27023)
#8 0x0000556a44cb45be
n/a (baloo_file + 0xd5be)
Additionally, if it can be of any help, journalctl is also filed with this kind
of lines:
Feb 19 00:28:08 T470-clement baloo_file[46930]: org.kde.baloo.engine:
IdFilenameDB::put MDB_BAD_TXN: Transaction must abort, has a child, or is
invalid
Feb 19 00:28:08 T470-clement baloo_file[46930]: org.kde.baloo.engine:
IdTreeDB::put MDB_BAD_TXN: Transaction must abort, has a child, or is invalid
Feb 19 00:28:08 T470-clement baloo_file[46930]: org.kde.baloo.engine:
IdFilenameDB::put MDB_BAD_TXN: Transaction must abort, has a child, or is
invalid
Feb 19 00:28:08 T470-clement baloo_file[46930]: org.kde.baloo.engine:
IdTreeDB::put MDB_BAD_TXN: Transaction must abort, has a child, or is invalid
Feb 19 00:28:08 T470-clement baloo_file[46930]: org.kde.baloo.engine:
DocumentTimeDB::put 36080564259847682 MDB_BAD_TXN: Transaction must abort, has
a child, or is invalid
--
You are receiving this mail because:
You are watching all bug changes.
