SUMMARY STEPS TO REPRODUCE 1. Chat in konversation 2. Observe Baloo indexing status 3. OBSERVED RESULT Baloo tries to index files, failing with error messages and tries to index again. When files are excluded by user, it doesn't seem to care and tries to index them again causing massive CPU load. EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.17.3 (available in About System) KDE Plasma Version: 5.17.3 KDE Frameworks Version: 5.64.0 Qt Version: 5.12.5 ADDITIONAL INFORMATION output of journalctl |grep baloo Nov 20 09:21:33 localhost.localdomain baloo_file_extractor[7871]: org.kde.baloo.engine: PositionDB::put MDB_BAD_TXN: Transaction must abort, has a child, or is Nov 20 09:21:31 localhost.localdomain baloo_file_extractor[7871]: org.kde.baloo.engine: PostingDB::put MDB_BAD_TXN: Transaction must abort, has a child, or is iinvalid Nov 20 09:21:33 localhost.localdomain baloo_file_extractor[7871]: org.kde.baloo.engine: PostingDB::put MDB_BAD_TXN: Transaction must abort, has a child, or is invalid Nov 20 09:21:33 localhost.localdomain baloo_file_extractor[7871]: org.kde.baloo.engine: PositionDB::put MDB_BAD_TXN: Transaction must abort, has a child, or is invalid Nov 20 09:21:33 localhost.localdomain baloo_file_extractor[7871]: org.kde.baloo.engine: Transaction::commit MDB_BAD_TXN: Transaction must abort, has a child, or is invalid Nov 20 09:21:33 localhost.localdomain baloo_file_extractor[7871]: org.kde.baloo: Found "/home/ilgaz/logs/freenode_#kubuntu-devel.log" in the ContentIndexingDB, although it should be skipped Nov 20 09:21:33 localhost.localdomain baloo_file_extractor[7871]: org.kde.baloo: Found "/home/ilgaz/logs/freenode.log" in the ContentIndexingDB, although it should be skipped Nov 20 09:21:33 localhost.localdomain baloo_file_extractor[7871]: org.kde.baloo: Found "/home/ilgaz/logs/freenode_#kubuntu.log" in the ContentIndexingDB, although it should be skipped Nov 20 09:21:33 localhost.localdomain baloo_file_extractor[7871]: org.kde.baloo: Found "/home/ilgaz/logs/freenode_#kubuntu-offtopic.log" in the ContentIndexingDB, although it should be skipped
See 425017. Fixed in KF 5.73 *** This bug has been marked as a duplicate of bug 425017 ***