Arch Linux

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#43614 - [baloo-frameworks] can not disable baloo-frameworks

Attached to Project: Arch Linux
Opened by patrick (potomac) - Wednesday, 28 January 2015, 17:53 GMT
Last edited by Andrea Scarpino (BaSh) - Wednesday, 28 January 2015, 18:56 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Andrea Scarpino (BaSh)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No



baloo4 has been replaced by the package "baloo-frameworks (5.6.0-1)",

and I notice a bug : it's impossible to disable baloo, at each boot baloo runs and slows down the boot process ( high I/O hardisk with the process "baloo-file" )

in KDE4 systemsettings I set baloo options to not scan my /home, but this setting is not respected by baloo

how to disable baloo-frameworks ?

Additional info:
* package version(s) baloo-frameworks (5.6.0-1)
* config and/or log files etc.

Steps to reproduce:
- install baloo-frameworks (5.6.0-1)
- you will notice that baloo_file is running at each boot and generates slow boot ( excessive I/O hardisk )
- and the baloo settings in KDE4 systemsettings are not followed by baloo-frameworks
This task depends upon

Closed by  Andrea Scarpino (BaSh)
Wednesday, 28 January 2015, 18:56 GMT
Reason for closing:  Not a bug
Additional comments about closing:  Not a packaging one at least
Comment by Andrea Scarpino (BaSh) - Wednesday, 28 January 2015, 18:05 GMT
You are correct, it seems there is no UI at the moment.

You could copy $HOME/.kde4/share/config/baloofilerc to $HOME/.config/
But I don't see it as a packaging bug, maybe we should just mention this to the wiki.
Comment by patrick (potomac) - Wednesday, 28 January 2015, 18:12 GMT
I installed kde-cli-tools package,

but how to use "kcmshell5" in order to disable baloo ?

if I type kcmshell5 I get this output :

$ kcmshell5
Could not find drkonqi at /usr/lib/drkonqi
Usage: kcmshell5 [Qt-options] [KDE-options] [options] module

A tool to start single KDE control modules

Generic options:
--help Show help about options
--help-qt Show Qt specific options
--help-kde Show KDE specific options
--help-all Show all options
--author Show author information
-v, --version Show version information
--license Show license information
-- End of options

--list List all possible modules

module Configuration module to open
--lang <language> Specify a particular language
--silent Do not display main window
--args <arguments> Arguments for the module

then I type :

$ kcmshell5 --list
Could not find drkonqi at /usr/lib/drkonqi
The following modules are available:
kf5.kservice.sycoca: Trying to open ksycoca from "/home/cesar/.cache/ksycoca5"
cache - Configuration des param?tres du cache Web
cookies - Configuration du fonctionnement des cookies
filetypes - Configuration des associations de fichiers
kcm_activities - Configure le syst?me d'activit?s
kcm_ssl - Certificats et versions SSL
kcmtrash - Configurer les param?tres de la corbeille
netpref - Configuration g?n?rique du r?seau comme, par exemple, les valeurs des d?lais d'attente
proxy - Configuration des serveurs mandataires (proxy) utilis?s
smb - Configuration des syst?mes de fichiers Windows (SMB) pour que vous y naviguiez
useragent - Configuration de la mani?re dont Konqueror se signale
webshortcuts - Configurer les raccourcis web

so it's not clear, what is the exact procedure if I want to disable baloo ?
Comment by Antonio Rojas (arojas) - Wednesday, 28 January 2015, 18:16 GMT
balooctl disable
Comment by Andrea Scarpino (BaSh) - Wednesday, 28 January 2015, 18:16 GMT
Nope, I was wrong and I modified my previous comment.
Comment by patrick (potomac) - Wednesday, 28 January 2015, 18:30 GMT
Andreas Scarpino : thanks for your answer,

so the workaround is to copy the file ~/.kde4/share/config/baloofilerc to ~/.config,

maybe you should add this information in a "texttooltip" when the user do the upgrade of baloo with pacman, for example during the pacman -Syu :

>> info : don't forget to copy the file ~/.kde4/share/config/baloofilerc to your ~/.config