[dolphin] [Bug 471099] Tags can't be renamed nor be deleted

[Dean Rikrik Ichsan Hakiki]

https://bugs.kde.org/show_bug.cgi?id=471099

--- Comment #8 from Dean Rikrik Ichsan Hakiki <deanrikrikichsanhakiki+kdebug at gmail.com> ---
(In reply to tagwerk19 from comment #7)
> > ... 'balooctl status' took quite a long time to return the result ...
> Balooctl is looking through the index and counting the files that still need
> to be indexed - at the same time as baloo is indexing and adding results to
> it. The two do a little dance as to who gets access to the file....
> 
> One thing to double-check:  Watch out whether you are using symlinks. Baloo
> does not follow these when it discovers what needs to be indexed. If you've
> created your text file in a folder "elsewhere" in your system and symlinked
> to it, then it is not going to be indexed.
> 
> Second, there's a recent change (something that is being looked at again at
> the moment) that caps the amount of memory that baloo can use.  You might
> want to check the:
> 
>     /usr/lib/systemd/user/kde-baloo.service
> 
> file (if it exists...) If there's a memory limit is there as a:
> 
>     MemoryHigh=512M
> 
> line, you can try changing it to:
> 
>     MemoryHigh=50%
> 
> and see whether the indexing changes.
> 
> However the underlying problem is likely to be with BTRFS (and the fact that
> when you reboot your disc might be mounted with a different device number -
> and this makes baloo think that all your files are "new files"). It's worth
> looking at Bug 470665.

I do use symlinks but when I found this issue I was editing a normal file in
the root of my home folder. Also, I assume that Baloo won't follow/index the
symlinked folder if the folder is not explicitly added to the index list on the
KDE Settings, right? Because after the Baloo behaved normally, I can add the
symlinked folder into it and it index the folder just fine.

Let's say the folder is located at `/mnt/tier_1/diagrams` and I symlinked it to
the home folder, so the path would look like `~/diagrams`, and I add
`~/diagrams` explicitly into the indexed folder on the File Search settings and
it now indexed and detect tag changes to the file inside this `diagrams`
folder, whether I change it from `~` or from `/mnt/tier_1`

I checked and the service file exists and it also contains the `MemoryHigh`
config with the same value, is it the limit of system memory that Baloo can
use? Does it have anything to do with the Baloo index size through `balooctl
indexSize`? Also, does 50% means 50% of the total system memory?

And the bug you mentioned seems interesting because I've never experienced
Baloo reindexing my partition again and again (or either because it's an SSD so
it didn't really matter or I just don't pay any attention), even when
previously it was non-responsive it just stays idle, I forgot to check the CPU
usage but it seems that it doesn't do anything since I have quite underpowered
and relatively old CPU (i3-8100) and doesn't feel anything become sluggish or
my fan ramping up when start-up, but just the Baloo itself quite slow to
respond (among other things I've stated and explained), but definitely will
check the next time when I'm going to do a restart.

-- 
You are receiving this mail because:
You are on the CC list for the bug.