On master branch with two different installs. After reboot this fills my log ~/.local/share/sddm/wayland-session.log: org.kde.baloo.engine: MTimeDB::del 0 38891358362011651 MDB_BAD_TXN: Transaction must abort, has a child, or is invalid org.kde.baloo.engine: MTimeDB::del 0 38891427081488387 MDB_BAD_TXN: Transaction must abort, has a child, or is invalid org.kde.baloo.engine: MTimeDB::del 0 38891435671422979 MDB_BAD_TXN: Transaction must abort, has a child, or is invalid (QUrl("tags:/"), QUrl("tags:/"), QUrl("tags:/"), QUrl("tags:/")) org.kde.baloo.engine: MTimeDB::del 0 38893342636902403 MDB_BAD_TXN: Transaction must abort, has a child, or is invalid org.kde.baloo.engine: MTimeDB::del 0 38901447240189955 MDB_BAD_TXN: Transaction must abort, has a child, or is invalid org.kde.baloo.engine: MTimeDB::del 0 38901455830124547 MDB_BAD_TXN: Transaction must abort, has a child, or is invalid Need to issue quick enough killall baloo_file otherwise at one point my disk will be full.
I hope this issue is not in the new frameworks release. Why is no one investigating this? Is baloo a matinained product anymore? Should I just disable it like everybody else does apparently? I'm now looking through its source code because I don't have anything else to do.
roman@workstation ~/dev/kde/src/frameworks/baloo (git)-[0e6f1c9...|bisect] % git bisect bad 0e6f1c92378226060ee08b356e503f9000992756 is the first bad commit commit 0e6f1c92378226060ee08b356e503f9000992756 Author: Stefan Brüns <stefan.bruens@rwth-aachen.de> Date: Sat Jun 8 18:29:30 2019 +0200 [PowerStateMonitor] Be conservative when determining power state Summary: When the state defaults to AC-powered, the indexer may start some energy consuming tasks, only to stop these later when the pending DBus call finishes. Especially the content indexer can take a while to stop, until the current batch is finished. In case the DBus call fails AC-powered is assumed, to match the previous default. Test Plan: unplug AC power start baloo_file -> the content indexer no longer processes its first batch Reviewers: #baloo, ngraham, astippich, poboiko Reviewed By: poboiko Subscribers: kde-frameworks-devel, #baloo Tags: #frameworks, #baloo Differential Revision: https://phabricator.kde.org/D21672
Git commit d6d86cb86cb631a0d736858ecdf2efb71c20172f by Roman Gilg. Committed on 16/07/2019 at 09:34. Pushed by romangilg into branch 'master'. Revert "[PowerStateMonitor] Be conservative when determining power state" This reverts commit 0e6f1c92378226060ee08b356e503f9000992756. M +1 -3 src/file/powerstatemonitor.cpp https://commits.kde.org/baloo/d6d86cb86cb631a0d736858ecdf2efb71c20172f
I reverted the broken commit now on master. If this affects users in Frameworks 5.60 and how to fix it for them needs to be checked by Stefan.
This just sucks. You were obviously able to find my mail address, but then you wait 3 minutes until you just revert a commit?
I waited two weeks for the person responsible to notice this bug report. Don't be angry, be better.
The revert does only fix the problem when restarting baloo from command line. On boot the log still gets spammed. So there needs to be put in place a different fix for the issue. It's still interesting that it does not happen with the revert in place when launching baloo from command line.
I'm not seeing this spam in the log file anymore with Frameworks 5.76. Are you?
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!