Summary: | Multiple issues with tags | ||
---|---|---|---|
Product: | [Frameworks and Libraries] frameworks-baloo | Reporter: | Matej Mrenica <matejm98mthw> |
Component: | Tags | Assignee: | Stefan Brüns <stefan.bruens> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | matejm98mthw, nate, tagwerk19 |
Priority: | NOR | ||
Version: | 5.67.0 | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Matej Mrenica
2020-02-15 11:57:23 UTC
You cannot delete tags, you can only remove it from files/directories. If there are no files left, the tag is removed. Make sure your file/directory is writable. You can check the raw tag data with $> getfattr -d <filepath> output of getfattr (In reply to Stefan Brüns from comment #1) > Make sure your file/directory is writable. By who? They are only writable by me/owner not group nor other. > $> getfattr -d <filepath> Gives me no output for folders that are shown in tags, but shows tags for diffrent folders that are not shown in Tags in Dolphin. So, after some testing: After adding a tag to an item, this tag is shown in the output of getfattr. After removing this tag, it is also no longer shown by getfattr. There are two issues now: 1. new tags dont appear in the tags:/ view. 2. tags:/ shows tags that don't exist anymore and can't be removed Both remaining issues are tracked by Bug 401019. *** This bug has been marked as a duplicate of bug 401019 *** If it is not a 'temporary' issue; that is Dolphin still shows the wrong tags even if you log out and back in, then maybe rebuilding the baloo index would help. Try: baloo purge; baloo monitor The 'monitor' will show a stream of output showing each file as it is indexed. (In reply to tagwerk19 from comment #6) > If it is not a 'temporary' issue; that is Dolphin still shows the wrong tags > even if you log out and back in, then maybe rebuilding the baloo index would > help. > > Try: > baloo purge; baloo monitor > > The 'monitor' will show a stream of output showing each file as it is > indexed. Thanks, rebuilding the index fixed this. Now only https://bugs.kde.org/show_bug.cgi?id=401019 remains. |