https://bugs.kde.org/show_bug.cgi?id=471099
--- Comment #4 from Dean Rikrik Ichsan Hakiki <deanrikrikichsanhakiki+kde...@gmail.com> --- (In reply to tagwerk19 from comment #3) > 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...) I see, yes, I'm using BTRFS, I apologize for not mentioning it, and indeed `balooctl purge` seems to fix things, but now it seems that baloo doesn't even indexing or monitoring any changes after a purge and then a restart. I restart the computer after executing `balooctl purge` (wait till it finishes the purge), and sure enough the Tag is now gone, and I waited a little while until baloo have 100% indexing my home folder, and then trie to modify a tag of a file in my home folder, the tag seems to be applied and I can see it through `getfattr` command, but baloo doesn't seem to detect this changes and stays at "Idle" on the `balooctl monitor` command resulting in no tags added to Dolphin collection, I think I need some time to see the behaviour of these two software, but I guess it's the bug? Also, sorry if somehow I make this bug report section like a forum discussion and break any guidelines. -- You are receiving this mail because: You are watching all bug changes.