Harry S's questions

KDE baloo has recently caused rsyslog to start logging many errors.

Part of 'Syslog'

Mar  3 15:01:53 harry-S340 baloo_file.desktop[2982]: org.kde.baloo.engine: PositionDB::put MDB_BAD_TXN: Transaction must abort, has a child, or is invalid
Mar  3 15:01:53 harry-S340 baloo_file.desktop[2982]: org.kde.baloo.engine: PostingDB::put MDB_BAD_TXN: Transaction must abort, has a child, or is invalid
Mar  3 15:01:53 harry-S340 baloo_file.desktop[2982]: org.kde.baloo.engine: PositionDB::put MDB_BAD_TXN: Transaction must abort, has a child, or is invalid
Mar  3 15:01:53 harry-S340 baloo_file.desktop[2982]: org.kde.baloo.engine: PostingDB::put MDB_BAD_TXN: Transaction must abort, has a child, or is invalid
Mar  3 15:01:53 harry-S340 baloo_file.desktop[2982]: org.kde.baloo.engine: PositionDB::put MDB_BAD_TXN: Transaction must abort, has a child, or is invalid
Mar  3 15:01:53 harry-S340 baloo_file.desktop[2982]: org.kde.baloo.engine: PostingDB::put MDB_BAD_TXN: Transaction must abort, has a child, or is invalid
Mar  3 15:01:53 harry-S340 baloo_file.desktop[2982]: org.kde.baloo.engine: PostingDB::put MDB_BAD_TXN: Transaction must abort, has a child, or is invalid
Mar  3 15:01:53 harry-S340 baloo_file.desktop[2982]: org.kde.baloo.engine: PositionDB::put MDB_BAD_TXN: Transaction must abort, has a child, or is invalid
Mar  3 15:01:53 harry-S340 baloo_file.desktop[2982]: org.kde.baloo.engine: PostingDB::put MDB_BAD_TXN: Transaction must abort, has a child, or is invalid
Mar  3 15:01:53 harry-S340 baloo_file.desktop[2982]: org.kde.baloo.engine: PositionDB::put MDB_BAD_TXN: Transaction must abort, has a child, or is invalid
Mar  3 15:01:53 harry-S340 baloo_file.desktop[2982]: org.kde.baloo.engine: PostingDB::put MDB_BAD_TXN: Transaction must abort, has a child, or is invalid

It caused my /var/log/syslog to grow exponentially, it filled the disk once already, I've since disabled rsyslog to stop this from destroying my SSD and making Ubuntu unusable but I don't know what Baloo is or how to stop and uninstall it. When i fist noticed this /var/log/syslog had grown to 66GB causing my disk to be FULL. I was able to delete it and log back in and disable rsyslog through recovery mode. Running rsyslog for one second caused it to go up to 75MB.

'Neofetch --off' result

OS: Ubuntu 19.10 x86_64 
Host: 81NC Lenovo IdeaPad S340-15API 
Kernel: 5.3.0-40-generic 
Uptime: 11 mins 
Packages: 3040 (dpkg), 38 (snap) 
Shell: bash 5.0.3 
Resolution: 1920x1080 
DE: GNOME 
WM: Mutter 
WM Theme: Adwaita 
Theme: Yaru-dark [GTK2/3] 
Icons: Yaru [GTK2/3] 
Terminal: gnome-terminal 
CPU: AMD Ryzen 5 3500U with Radeon Vega Mobile Gfx (8) @ 2.100GHz 
GPU: AMD ATI 04:00.0 Picasso 
Memory: 2756MiB / 5945MiB 

I don't want to uninstall the whole of KDE straight away but if that is the only way to get rid of this broken program then I happily will.

Other commands

harry@harry-S340:~$ whereis baloo
baloo:

harry@harry-S340:~$ sudo apt-get autoremove baloo
[sudo] password for harry: 
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Package 'baloo' is not installed, so not removed
0 to upgrade, 0 to newly install, 0 to remove and 4 not to upgrade.

harry@harry-S340:~$ whereis baloo_file
baloo_file: /usr/bin/baloo_file

harry@harry-S340:~$ sudo apt-get autoremove baloo_file
Reading package lists... Done
Building dependency tree       
Reading state information... Done
E: Unable to locate package baloo_file

harry@harry-S340:~$ sudo systemctl status baloo_file
Unit baloo_file.service could not be found.

Pressing tab to see all the commands that have baloo in them:

harry@harry-S340:~$ baloo
balooctl                           baloo_filemetadata_temp_extractor
baloo_file                         baloosearch
baloo_file_extractor               balooshow

these all don't have any manuals

harry@harry-S340:~$ man baloo
No manual entry for baloo
harry@harry-S340:~$ man baloo_file
No manual entry for baloo_file
harry@harry-S340:~$ man balooctl
No manual entry for balooctl
harry@harry-S340:~$ man baloosearch
No manual entry for baloosearch
harry@harry-S340:~$ man balooshow
No manual entry for balooshow
harry@harry-S340:~$ man baloo_filemetadata_temp_extractor
No manual entry for baloo_filemetadata_temp_extractor
harry@harry-S340:~$ man baloo_file_extractor
No manual entry for baloo_file_extractor

Desktop file mentioned in syslog

[Desktop Entry]
Type=Application
Exec=baloo_file
X-KDE-StartupNotify=false
X-KDE-autostart-condition=baloofilerc:Basic Settings:Indexing-Enabled:true
X-KDE-autostart-phase=0
X-GNOME-Autostart-enabled=true
OnlyShowIn=KDE;GNOME;Unity;XFCE
NoDisplay=true

Requests

Balooctl status

harry@harry-S340:~$ balooctl status
Baloo File Indexer is running
Indexer state: Indexing file content
Total files indexed: 109,311
Files waiting for content indexing: 3
Files failed to index: 4
Current size of index is 507.65 MiB

harry@harry-S340:~$ sudo balooctl disable
[sudo] password for harry: 
Disabling and stopping the File Indexer

this stopped rsyslog filling up /var/log/syslog.

Thanks, Harry

I am running Ubuntu 18.04.3 LTS (GNU/Linux 4.15.0-62-generic i686) and each time the computer lid is closed it goes to sleep and then wakes the screen displays this and it is unresponsive.
I have since disabled the sleep function when the lid is closed and keep it logged in to stop it from coming unresponsive.
It is quite old hardware:

• CPU: mobile AMD Athlon XP-M 2400+ @ 1.79126GHz
• GPU: ProSavage8 KM266/KL266
• RAM: 51MiB / 394MiB

It runs without a Desktop Environment in terminal mode most of the time. It has LXDE Desktop Environment installed (the hardware can't handle any more intensive).
The problem I have is that I can't put it to sleep so I either have to have it on (and it is quite loud) or off (it takes a few minutes to boot). I would love to be able to put it to sleep every so often.
I have super user privileges, current access (through ssh) and I know how to use the terminal quite well.

Cropped image showing the faces here: