SUMMARY I have got 5E5 lines of MDB_BAD_TXN in my syslog. The log partition is running out of space. STEPS TO REPRODUCE 1. Examine the file /var/log/messages! OBSERVED RESULT 2022-12-10T14:02:18.464789+01:00 [localhost] baloo_file[1729]: kf.baloo.engine: PostingDB::put MDB_BAD_TXN: Transaction must abort, has a child, or is invalid 2022-12-10T14:02:18.465068+01:00 [localhost] baloo_file[1729]: kf.baloo.engine: PositionDB::put MDB_BAD_TXN: Transaction must abort, has a child, or is invalid … 2022-12-10T17:27:19.254054+01:00 [localhost] baloo_file[1695]: kf.baloo.engine: Transaction::commit MDB_BAD_TXN: Transaction must abort, has a child, or is invalid EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: openSUSE Tumbleweed 20221209 (available in About System) KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.100.0 Qt Version: 5.15.7 ADDITIONAL INFORMATION
Looks similar to Bug 406868 scrolling down to: https://bugs.kde.org/show_bug.cgi?id=406868#c7 as a "heads up" though - it gets a bit nasty with baloo if you are using BTRFS and multiple subvolumes https://bugs.kde.org/show_bug.cgi?id=402154#c12 If you reboot, "/home" might be mounted with a different device number, if baloo sees files with new device numbers it tries to index them, if files with an "old" device number disappear, to remove the entries. There is some work to do here...
I'll mark as a duplicate, if you discover anything else feel free to reopen. I think the root cause is most likely the OpenSUSE and multiple BTRFS subvolumes issue though. *** This bug has been marked as a duplicate of bug 406868 ***