https://bugs.kde.org/show_bug.cgi?id=450171
tagwer...@innerjoin.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tagwer...@innerjoin.org
--- Comment #1 from tagwer...@innerjoin.org ---
When you add a tag, you are adding something to the "metadata" for the file.
Think of it as something like the modification time; it's there in the
filesystem but not part of the file (and not written to another file/folder
somewhere else).
(You will find that there _are_ also tags embedded in files, EXIF and ID3 tags.
A good example being "Duration"...)
If you've tagged;
The_Monster.mp4
say with "Test", you can see the tags with the command line tool getfattr
$ getfattr -d The_Monster.mp4
...
user.xdg.tags="Test"
OK, that's the first stage. A point to watch here is that the Linux filesystems
(such as ext2/3/4, btrfs) can deal with the "metadata" but a FAT system on a
USB stick cannot. So, need to be careful copying files to a USB stick...
Second stage is that Baloo "is told that" there's been a change and goes and
indexes the new information. Here it will read the info for "The_Monster.mp4"
and write it to its database (which as you've found, is a big file under
.local/share/baloo). You asked "where is the location of the tag folder", the
answer is that it when you look at, say tags:/Test, Baloo is doing a lookup in
its index and giving you the results. There quite some magic behind the scenes.
Assuming that Baloo has indexed the file, you can ask what info it has on it
$ balooshow -x The_Monster.mp4
This will give you a load of data, that should include "Test" and also the
other metadata "embedded" in the file.
This should work with the file on your local disc. It's possible (quite
possible) it won't if the file is on a NAS - so that's the first test to try,
compare the behaviour "locally" and on the NAS.
(In reply to linuxfluesterer from comment #0)
> But then I had a problem with duplicate entries of the same file names
> marked with tags. This looks like (e.g.):
> -The_Monster.mp4
> -The_Monster.mp4(1)
This is with Dolphin? I know I've seen the same (earlier times, not so often
now)
You can see what Baloo gives you with a
$ baloosearch -i The_Monster.mp4
If you get a single line, then Dolphin is generating the "ghost file" with the
"(1)", if there's more than one line then it's a problem with Baloo - that it
has seen the file more than once and not forgotten the earlier version. That's
the second test to try....
> Finally I decided to delete the index and baloo file in my home directory
> ~/.local/share/baloo. After doing this I resumed baloo, which then rebuilt
> the index. I thought, so far, so good.
The cleanest way of getting Baloo to restart the indexing "from scratch" is
$ balooctl purge
That stops the indexing processes, deletes the index and restarts the
processes.
I think I'll pause here and let you try things out, we can then work out what
to do next.
Wishing you luck
--
You are receiving this mail because:
You are watching all bug changes.
