https://bugs.kde.org/show_bug.cgi?id=407530
tagwer...@innerjoin.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tagwer...@innerjoin.org
Status|REPORTED |CONFIRMED
Ever confirmed|0 |1
--- Comment #2 from tagwer...@innerjoin.org ---
(In reply to Patrick Silva from comment #1)
> Currently we apparently can delete tags while baloo indexes files.
> But all them are back after Dolphin to be restarted.
Are the tags removed "on disc" and baloo (and dolphin) are having to catch up
or has the delete action not worked?
My understanding of the process (from observation) is:
Dolphin is showing a cached view of tagged files, derived from baloo
... It would be nice to know how to get this list of "indexed tags"
from the command line.
The tags exist "at source" in extended attributes on disc (you can see them for
a particular file with "getfattr -d filename")
When you delete a tag, dolphin finds all the files that include that tag and
updates the extended attributes for each file in turn to remove it. I think it
also immediately "drops" that tag from the display; say that it is "hoping"
that the remove will be successful.
You should be able to check that the tag has gone "at source" with getfattr...
In the mean time, baloo will have been told of the changes via iNotify and know
that it has to update its index. When this has gone "full circle" the tags have
gone at source, the index no longer includes them, the cacheing tags.so
processes have caught up with the change and they have "really gone" from
Dolphin
If baloo is busy, the job of reindexing the extended attributes is "in the
queue" and the tags folders will only disappear when the reindexing is done (I
see this behaviour in Neon Testing, so flagging as "Confirmed")
If you look at:
balooshow -x filename
you should see whether baloo still has the tags listed as "XAttr Terms:" (and
the Ctime, or the time the file properties were changed - as far as baloo
knows).
It's possible that things can go wrong.
If you have read-only files that have tags, dolphin will not be able
to remove the tags "on disc" (but it seemingly does not give an error)
If "too much is happening" and baloo does not pick up the changes (there
is an iNotify limit of "max_queued_events") then "balooctl check"
prompts baloo to go back and check for changes (see Bug 353874)
--
You are receiving this mail because:
You are watching all bug changes.
