Baloo file indexing daemon closed

English Applications
#1

For the past few days I’ve been getting the following error every time kde starts:

 Baloo file indexing daemon closed.    	 	 	 	  
 Executable: baloo_file PID: 1703 Signal: Aborted

When I click on “report but” I get the following:

 the generated crash information is not useful

 You can click “install debug symbols”

Clicking “install debug symbols” gives me this:

  pbuildid was not found on your system. Please install pbuildid and try again.

But when I try to install pbuildid using zypper I get this:

 'pbuildid' not found in package names. Trying capabilities. 
No provider of 'pbuildid' found

Has anyone else encountered this? It doesn’t seem to affect my computer in any noticeable way, but the message occurs every time I launch kde. I’m using an up-to-date tumbleweed with kde plasma 5.14.4, kde frameworks 5.52.0, and Qt version 5.11.2

#2

Hi
You can use command-not-found or zypper + file-list (there is also search-packages);


cnf pbuildid 
                          
The program 'pbuildid' can be found in the following package:
  * ptools  path: /usr/bin/pbuildid, repository: zypp (repo-oss) ]

Try installing with:
    sudo zypper install ptools

zypper se --file-list pbuildid

S | Name   | Summary                      | Type   
--+--------+------------------------------+--------
  | ptools | The process tools collection | package
#3

There’s an ongoing KDE Baloo issue which is being handled by the KDE Bug Report #367480: <https://bugs.kde.org/show_bug.cgi?id=367480>.

In that Bug Report there’s a hint for a work-around until such time as the repair to the Baloo code hits the streets:

As a workaround until such time as your Distro updates to Frameworks 5.51, you can add a symbolic link to this Bash script in ‘~/.config/plasma-workspace/env/’:


#!/bin/bash
#
# Clean Baloo …
#
if  -f ~/.local/share/baloo/dateLastCleaned ]]
then
  declare -i BalooLastDate
  BalooLastDate="$(cat ~/.local/share/baloo/dateLastCleaned)"
  declare -i TwoDaysAgo
  TwoDaysAgo="$(date --date='2 days ago' +%Y%m%d)"
  if (( $BalooLastDate < $TwoDaysAgo ))
  then
    balooctl stop
    rm ~/.local/share/baloo/dateLastCleaned
    find ~/.config/ -maxdepth 1 -iname '*baloo*' -execdir /usr/bin/rm '{}' \;
    find ~/.local/share/baloo/ -iname '*index*' -execdir /usr/bin/rm '{}' \;
    date +%Y%m%d > ~/.local/share/baloo/dateLastCleaned
  fi
else
  balooctl stop
  find ~/.config/ -maxdepth 1 -iname '*baloo*' -execdir /usr/bin/rm '{}' \;
  find ~/.local/share/baloo/ -iname '*index*' -execdir /usr/bin/rm '{}' \;
  date +%Y%m%d > ~/.local/share/baloo/dateLastCleaned
fi
#
#4

Thanks for the tips. I installed ptools but I get this error message when I try to install the debug packages:

An error was encountered during the installation of the debug symbol packages.

As a workaround until such time as your Distro updates to Frameworks 5.51,

It seems like the bug is still there in frameworks 5.52, which I’m using. And it looks like other people have already reported it. So I guess I’ll wait for an update to fix things?

#5

visudo

At about line #64, is the file’s contents as follows:


## In the default (unconfigured) configuration, sudo asks for the root password.
## This allows use of an ordinary user account for administration of a freshly
## installed system. When configuring sudo, delete the two
## following lines:
# Defaults targetpw   # ask for the password of the target user i.e. root
# ALL   ALL=(ALL) ALL   # WARNING! Only use this together with 'Defaults targetpw'!

If it is, uncomment “Defaults targetpw” and “ALL ALL=(ALL) ALL” before attempting to install the debug packages from DrKonqui …
You’ll also have to comment out any user-specific sudo items …

  • DrKonqui will then ask for the “root” password to allow the debug packages to be installed – via the network …

And then put everything back into place once the debug packages needed by DrKonqui have been installed …

With the Bash script executing the Baloo clean-up at 2 day intervals – assuming a daily login …

  • That script has passed my personal QA process … :wink:
#6

At about line #64, is the file’s contents as follows:

Where is that file located? I can’t seem to find it.

#7

It’s not a file. As root, at a console, simply type visudo, then press Enter.

#8

Thanks! Those lines were already commented out. So there must be some other reason why I can’t install the debug packages.

#9

Is the debug repo active?
http://download.opensuse.org/tumbleweed/repo/debug/

#10

Thanks–that solved the problem. I added the debug repo and was able to report the bug, which, as mentioned above, seems to be a duplicate of some existing reports.

#11

In that Bug Report there’s a hint for a work-around until such time as the repair to the Baloo code hits the streets:

By the way, I just wanted to belatedly thank you for that work-around–it fixed the annoying problem!