[RESOLVED] Dolphin not showing tags

[tiro_uspsss]

Hello all!

I’ve recently begun the habit of tagging pics on my ZFS storage array. I do this within Dolphin itself. The tags save, but when I use the details view, & select the tags column, none show.

any idea what I’m doing wrong?

[jlittle]

This has never worked for me; the tags column is always empty. I can see the tags in the Information panel, or the "properties" of the file. If desperate, I can run getfattr -d -m - in a konsole.

I've always suspected that dolphin is using the baloo index ("File search" in system settings) for this column. I won't allow baloo to run since it tried to kill my SSD repeatedly (I'm not exaggerating, 60 MB/s writing continuously).

[claydoh]

Tags might be a feature using baloo:



So if the external share isn't indexed, maybe tags are not there?

Buuuuutt on my NFS share:


My shares are most definitely NOT being indexed, like may home dirs are.
So tags definitely are NOT using baloo, though it can index them for search.

Of course, this is in the current Plasma (neon)

https://wiki.archlinux.org/title/Dolphin#File_tagging

[tiro_uspsss]

This has never worked for me; the tags column is always empty. I can see the tags in the Information panel, or the "properties" of the file. If desperate, I can run getfattr -d -m - in a konsole.

I've always suspected that dolphin is using the baloo index ("File search" in system settings) for this column. I won't allow baloo to run since it tried to kill my SSD repeatedly (I'm not exaggerating, 60 MB/s writing continuously).

I've heard that as well (re: indexing killing SSDs.. I may experiment - I'll only specify my HDDs, & exclude my SSDs

[tiro_uspsss]

Tags might be a feature using baloo:



So if the external share isn't indexed, maybe tags are not there?

Buuuuutt on my NFS share:


My shares are most definitely NOT being indexed, like may home dirs are.
So tags definitely are NOT using baloo, though it can index them for search.

Of course, this is in the current Plasma (neon)

https://wiki.archlinux.org/title/Dolphin#File_tagging

mmmm... interesting.. my HDDs aren't a network share, fwiw, they're local.

[tiro_uspsss]

turning on file indexing has solved my issue! thanks for the help folks!

[jlittle]

I've heard that as well (re: indexing killing SSDs..

I concluded that that baloo failure was dependent on my data. Baloo had failed in so many other ways, usually corrupting the index or balooning it to several GB, or running pegged to 100% on one core.

I may experiment - I'll only specify my HDDs, & exclude my SSDs

If you keep an eye on it, purging and rebuilding the index at any sign of trouble, it might work well for you. I imagine that consumer HDDs may have shortened lives writing continuously, and would significantly increase electricity usage.

[oshunluvr]

I've not had any noticeable trouble with Baloo for what seems like years now. This post prompted me to check what was up. Baloo had a 5.7GB file with 2.9GB used and had 380.000+ files indexed. So I ran "balooctl purge" and now it has a 304MB file with 182MB used and 17,000 files indexed. I read a bit and apparently baloo has an issue where if fails to clean its index.

Seems like maybe running purge one a year or so is a good idea!

[claydoh]

I've not had any noticeable trouble with Baloo for what seems like years now. This post prompted me to check what was up. Baloo had a 5.7GB file with 2.9GB used and had 380.000+ files indexed. So I ran "balooctl purge" and now it has a 304MB file with 182MB used and 17,000 files indexed. I read a bit and apparently baloo has an issue where if fails to clean its index.

Seems like maybe running purge one a year or so is a good idea!

Interesting. I have not touched my index in ages and ages, definitely no purging as far as I can recall. So I took a peek at some of my snapshots to compare sizes over time. My oldest snapshot is from April, it was at 250Mb
I index content and hidden files, and some locations outside of $HOME.

In August it grew to 5.7Gb. September 4: 7.2. Later that month, it dropped to 532Mb. I could swear I didn't purge it.
I believe I was indexing a larger set of directories and drives at the time, but not by much. Maybe something triggered a purge or cleanup?⁽¹⁾
October: 427Mb
Mid November 503
Today, 575
I still swear I haven't run a purge, It isn't something I'd think of, and haven't done for ages and ages, back when baloo was actually and truly s****y.


(1) Ahhh......https://bugs.kde.org/show_bug.cgi?id=402154#c66. A BTRFS-related bug in baloo. The update triggered a reindex, though 5.111 was released in October, after my sudden drop.

[tiro_uspsss]

well that's a fail after all - indexing would complete, but then start from the beginning after each boot.