https://bugs.kde.org/show_bug.cgi?id=454952
--- Comment #1 from tagwer...@innerjoin.org ---
Case 1...
Baloo needs to be running and indexing the folders you are using. Baloo can
be disabled,
failing, ignoring temporarily mounted or remote devices or not configured
to index
particular folders. There are various bugs here, for example Bug 424871,
Bug 435315,
Bug 441068
You might be thinking Baloo is indexing a folder whereas it is not, a
common cause of this
being folders mounted elsewhere with a symlink. Baloo has a policy of not
following
symlinks when indexing (see the Summary Bug 447119)
Note that if you add a tag through Dolphin, you are adding a file attribute
(xattr), not
modifying the file itself.
If Baloo is running, you will see the tag appear in Dolphin's "Places"
section (you may need
to force a refresh to see it, see below). You do not need to configure
Baloo to do "Content
indexing" to get this info.
Similarly if you have tagged files in the past and disabled Baloo, it's
possible to remove the
tag but the "tag folders" do not follow the change (Bug 414684)
... 1a
If Baloo is busy, it queues actions to add/remove tags (Bug 407530).
In this context, "busy" implies catching up with new files or dealing with
deletions (deleting a
large number of files can generate a lot of work, Bug 442453). The
background activity of
Context Indexing does not necessarily block metadata/tag updates.
... 1b
Baloo with remote storage is a separate issue - or collection of issues
dependent on the
protocol (Samba, NFS or ??) and the capabilities of the remote filesystem.
Baloo deliberately avoids trying to index remote filesystems and this may
impact both file
attribute (xattr) tags and embedded (EXIF/ID3) tags.
--
You are receiving this mail because:
You are watching all bug changes.
