1 |
On Thursday 21 Jul 2016 07:45:41 Daniel Frey wrote: |
2 |
> On 07/20/2016 10:37 PM, Mick wrote: |
3 |
> > On Wednesday 20 Jul 2016 20:37:58 Daniel Frey wrote: |
4 |
> >> On 07/20/2016 05:06 PM, Fernando Rodriguez wrote: |
5 |
> >>> This is fucking ridiculous. Baloo's kcm module is also part of |
6 |
> >>> plasma-desktop! Now after being forced to update it the indexer is |
7 |
> >>> making |
8 |
> >>> my system very unresponsive and I can't turn it off! |
9 |
> >> |
10 |
> >> Have you tried balooctl to turn it off? I think that's how I did it when |
11 |
> >> I tried plasma months ago. |
12 |
> >> |
13 |
> >> Dan |
14 |
> > |
15 |
> > I wasn't aware of this! It seems baloo has been busy all on its own: |
16 |
> > |
17 |
> > $ balooctl status |
18 |
> > Baloo File Indexer is not running |
19 |
> > Indexed 6412 / 7195 files |
20 |
> > Current size of index is 79.07 MiB |
21 |
> > |
22 |
> > $ balooctl config show includeFolders |
23 |
> > /home/michael |
24 |
> > |
25 |
> > So it's been indexing my whole /home directory. Will issuing a disable |
26 |
> > command survive a reboot? |
27 |
> |
28 |
> It's supposed to. It did for me for a while (i.e. several reboots) then |
29 |
> it started again. People have been reporting it works and doesn't work |
30 |
> so maybe it depends on the environment it's running in. There's other |
31 |
> baloo-related command line tools but I don't remember them now. |
32 |
> |
33 |
> I think I got annoyed at one point with all the freezing and crashing |
34 |
> (and I thought it was baloo even though it was disabled) and eventually |
35 |
> deleted all of the baloo* files, but plasma still kept crashing. |
36 |
> |
37 |
> Dan |
38 |
|
39 |
I've rebooted: |
40 |
|
41 |
$ balooctl status |
42 |
Baloo is currently disabled. To enable, please run "balooctl enable" |
43 |
|
44 |
Nice! :-) |
45 |
|
46 |
-- |
47 |
Regards, |
48 |
Mick |