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

bugzilla_noreply at kde.org bugzilla_noreply at kde.org
Fri Jun 16 11:23:12 BST 2023


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

--- Comment #3 from tagwerk19 at innerjoin.org ---
There's layers....

If you want to start at the bottom and check, the tags are stored in xattr and
you can see them with:

    getfattr -d your-tagged-file.txt

You'll see your tags listed as a "user.xdg.tags" comma-separated list of
values. If you've added tags through Dolphin you can see whether they've got to
the filesystem with a "getfattr"

You can check whether baloo has indexed the file with balooshow:

    balooshow -x your-tagged-file.txt

(look for the "XAttr Terms" line), if that's worked, then you should be able to
find the file when searching by the tag:

    baloosearch tags:"yourtag"

If it's gone wrong up to here, then there's an issue with baloo.

You don't say what sort of filesystem you are using. It's possible that your
"baloosearch" would show several matches for each file, that can happen if you
are using BTRFS and the best bet then to recreate the index, try

    balooctl purge

(You might need patience while the files are reindexed)

Dolphin queries baloo to get its "tag folders", however it caches results and
it can be that it gets hung up with stale results. It should show the same
results in the left hand panel that you see when you manually open "tags:"

Possibly an F5 would refresh the data but very likely not, closing Dolphin and
relaunching can help but it's a bit distribution dependent, sometimes there's a
copy of Dolphin running quietly in the background.

If you want to look deeper, there are likely "tags.so" processes running, these
are the processes that cache the results from baloo. If you've got more than
one "tags.so" process, there's a chance that the different processes are
holding different sets of results (this happened a while back, possible it's
been fixed...)

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


More information about the kfm-devel mailing list