Yet ANother Baloo Problem - Baloo File Indexing has been disabled QStandardPaths: wrong ownership on

Hello,
I don’t get it: how can baloo eat 100% of my CPU, a classic problem, if it is not even enabled (and cannot be) ? And what’s with the “QStandardPaths: wrong ownership on runtime directory /run/user/0, -2 instead of 0” error?

top - 09:31:02 up 1 min,  1 user,  load average: 1.46, 0.47, 0.16
Tasks:** 286 **total,**   2 **running,** 284 **sleeping,**   0 **stopped,**   0 **zombie
%Cpu(s):**  4.7 **us,**  4.2 **sy,** 10.6 **ni,** 69.7 **id,** 10.6 **wa,**  0.0 **hi,**  0.1 **si,**  0.0 **st
KiB Mem: ** 16357208 **total,**  3815620 **used,** 12541588 **free,**   611808 **buffers
KiB Swap:**  8386556 **total,**        0 **used,**  8386556 **free.**  1375160 **cached Mem

  PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND                                            
** 1888 fakemoth  39  19 5701320  36424  29080 R 100.0 0.223   1:01.06 baloo_file_extr                                    **
 1735 fakemoth  39  19 5494788  43272  16832 D 9.667 0.265   0:05.98 baloo_file                                          
 2385 fakemoth  20   0 1171636 139700  68692 S 9.000 0.854   0:01.61 chromium                                            
 1740 fakemoth  20   0 4201920 330164 145304 S 8.000 2.018   0:08.40 plasmashell                                         
 1522 root      20   0  299036 120632  90500 S 6.667 0.737   0:05.22 X                                                   
 1732 fakemoth  20   0 3209712 120448  94912 S 6.000 0.736   0:03.03 kwin_x11                                            
 1992 fakemoth  20   0 1432000 235140 133300 S 5.333 1.438   0:04.32 chromium                                            
 2360 fakemoth  20   0 1226864 135512  67632 S 3.333 0.828   0:02.36 chromium                                            
 2075 fakemoth  20   0  958732 236144 170000 S 1.333 1.444   0:01.14 chromium                                            
 1929 fakemoth  20   0  575764  74836  60784 S 1.000 0.458   0:00.45 konsole                                             
 1802 fakemoth  20   0  649640  51984  39160 S 0.667 0.318   0:00.57 ktorrent                                            
    7 root      20   0       0      0      0 S 0.333 0.000   0:00.17 rcu_preempt                                         
  114 root      20   0       0      0      0 S 0.333 0.000   0:00.08 kworker/u16:5                                       
  119 root      20   0       0      0      0 S 0.333 0.000   0:00.03 kworker/1:1                                         
  311 root      20   0       0      0      0 S 0.333 0.000   0:00.10 kworker/0:2                                         
 1736 fakemoth  20   0  811628  94332  73628 S 0.333 0.577   0:00.74 krunner                                             
    1 root      20   0   34380   6140   3436 S 0.000 0.038   0:01.58 systemd                                             
    2 root      20   0       0      0      0 S 0.000 0.000   0:00.00 kthreadd                                            
    3 root      20   0       0      0      0 S 0.000 0.000   0:00.00 ksoftirqd/0                                         
    4 root      20   0       0      0      0 S 0.000 0.000   0:00.00 kworker/0:0                                         
    5 root       0 -20       0      0      0 S 0.000 0.000   0:00.00 kworker/0:0H                                        
    6 root      20   0       0      0      0 S 0.000 0.000   0:00.04 kworker/u16:0                                       
    8 root      20   0       0      0      0 S 0.000 0.000   0:00.00 rcu_sched                                           
    9 root      20   0       0      0      0 S 0.000 0.000   0:00.00 rcu_bh                                              
   10 root      20   0       0      0      0 S 0.000 0.000   0:00.04 rcuop/0                                             
   11 root      20   0       0      0      0 S 0.000 0.000   0:00.00 rcuos/0                                             
   12 root      20   0       0      0      0 S 0.000 0.000   0:00.00 rcuob/0                                             
   13 root      rt   0       0      0      0 S 0.000 0.000   0:00.03 migration/0                                         
   14 root      rt   0       0      0      0 S 0.000 0.000   0:00.00 watchdog/0                                          
   15 root      rt   0       0      0      0 S 0.000 0.000   0:00.00 watchdog/1                                          
   16 root      rt   0       0      0      0 S 0.000 0.000   0:00.03 migration/1                                         
   17 root      20   0       0      0      0 S 0.000 0.000   0:00.00 ksoftirqd/1                                         
   18 root      20   0       0      0      0 S 0.000 0.000   0:00.00 kworker/1:0                                         
**FakeMoth-PC:/home/fakemoth #** balooctl status
Baloo is currently disabled. To enable, please run "balooctl enable"
**FakeMoth-PC:/home/fakemoth #** balooctl start
**FakeMoth-PC:/home/fakemoth #** QStandardPaths: wrong ownership on runtime directory /run/user/0, -2 instead of 0
Baloo File Indexing has been disabled

**FakeMoth-PC:/home/fakemoth #** balooctl enable
Enabling the File Indexer
**FakeMoth-PC:/home/fakemoth #** QStandardPaths: wrong ownership on runtime directory /run/user/0, -2 instead of 0
Failed to register via dbus. Another instance is running

**FakeMoth-PC:/home/fakemoth #** balooctl status
Baloo Index could not be opened


Please check the /run/user/ directory; I’ve checked a freshly booted Leap 42.1 system and found the following:


drwxr-xr-x  5 root root   100 22. Apr 10:31 ./
drwxr-xr-x 34 root root  1080 22. Apr 10:32 ../
drwx------  3 root root    60 22. Apr 10:29 0/
drwx------  6 ...  users  180 22. Apr 10:31 1000/
drwx------  3 sddm sddm    60 22. Apr 10:28 389/

[HR][/HR]Please note that, a 13.2 system is different:


drwxr-xr-x  3 root root    60 22. Apr 10:30 ./
drwxr-xr-x 33 root root  1040 22. Apr 08:26 ../
drwx------  8 ...  users  160 22. Apr 08:45 1000/

[HR][/HR]As an aside: I suspect that, it’s not a good idea to run baloo from the ‘root’ user. On the other hand there may be good reasons to do so; who knows …

@fakemoth: A question: which desktop environment are you running?
[HR][/HR]From the ‘top’ output you seem to be running some KDE Plasma components.
[HR][/HR]Also, please check the /tmp/ and /var/tmp/ directories; with KDE Plasma 5 there should be neither ‘kde-root’ nor ‘kdecache-root’ directories present.

Yes, I am using plasma 5, on Leap, everything updated. I have both directories the first in /tmp the second in /var/temp. I didn’t create them, nor do I intend to run baloo as root (I was having the impression it scans only /home? and in top you can clearly see that it runs as my user?) - can I safely delete those? Why did I get them, why aren’t necessary etc, can anyone provide some more info?

In /run/user I have only a 1000 directory. Thanks!

AFAIK Leap 42.1 systems running KDE Plasma 5 Desktops do not need the ‘/tmp/kde-root/’ and ‘/var/tmp/kdecache-root/’ directories; they can be safely removed.

Hmmm … AFAIK with Leap 42.1 /run/user/ should contain directories for the ‘root’ and ‘sddm’ (system) users.
[HR][/HR]

  • Check that any baloo instances running for the user ‘root’ are stopped and disabled.
  • The directory /root/.local/share/baloo/
    should be empty. - The file /root/.config/baloofilerc
    should only contain a [General] section containing “exclude filters” definitions.