On Thursday 21 Jul 2016 07:45:41 Daniel Frey wrote: > On 07/20/2016 10:37 PM, Mick wrote: > > On Wednesday 20 Jul 2016 20:37:58 Daniel Frey wrote: > >> On 07/20/2016 05:06 PM, Fernando Rodriguez wrote: > >>> This is fucking ridiculous. Baloo's kcm module is also part of > >>> plasma-desktop! Now after being forced to update it the indexer is > >>> making > >>> my system very unresponsive and I can't turn it off! > >> > >> Have you tried balooctl to turn it off? I think that's how I did it when > >> I tried plasma months ago. > >> > >> Dan > > > > I wasn't aware of this! It seems baloo has been busy all on its own: > > > > $ balooctl status > > Baloo File Indexer is not running > > Indexed 6412 / 7195 files > > Current size of index is 79.07 MiB > > > > $ balooctl config show includeFolders > > /home/michael > > > > So it's been indexing my whole /home directory. Will issuing a disable > > command survive a reboot? > > It's supposed to. It did for me for a while (i.e. several reboots) then > it started again. People have been reporting it works and doesn't work > so maybe it depends on the environment it's running in. There's other > baloo-related command line tools but I don't remember them now. > > I think I got annoyed at one point with all the freezing and crashing > (and I thought it was baloo even though it was disabled) and eventually > deleted all of the baloo* files, but plasma still kept crashing. > > Dan
I've rebooted: $ balooctl status Baloo is currently disabled. To enable, please run "balooctl enable" Nice! :-) -- Regards, Mick
signature.asc
Description: This is a digitally signed message part.
