Bug 417017

Summary:	Inconsistent result after we tag a file stored in a location non indexed by baloo: "assign tags" submenu of the context menu does not list the created tag and "Tags" section does not appear in places panel
Product:	[Applications] dolphin	Reporter:	Patrick Silva <bugseforuns>
Component:	general	Assignee:	Dolphin Bug Assignee <dolphin-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	kfm-devel, nate
Priority:	NOR
Version First Reported In:	19.12.1
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Patrick Silva 2020-02-01 10:00:54 UTC

STEPS TO REPRODUCE
1. make sure that information panel is enabled. If not, press F11 to enable it.
2. right click on any file located in a NTFS partition
3. hover over "assign tags" > click on "create new..."
4. type any tag and press enter/return
5. deselect the tagged file and select it again

OBSERVED RESULT
item "Tags" of information panel shows the created tag. But the created tag is not listed under "assign tags" submenu of the context menu when we right-click on any file nor when we press ctrl+l, type "tags:" and press enter/return. Furthermore, if we are tagging a file for the first time, "Tags" section does not appear in places panel even after you restart Dolphin.

EXPECTED RESULT
The same that happens when we tag a file located in an EXT4 partition:
created tag is listed under "assign tags" submenu of the context menu when we right-click on any file and when we press ctrl+l, type "tags:" and press enter/return. And "Tags" section should appear in places panel of Dolphin if we are tagging a file for the first time.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 5.17.90
KDE Frameworks Version: 5.66.0
Qt Version: 5.14.1

Comment 1 Patrick Silva 2020-02-01 10:14:02 UTC

In fact, if baloo is disabled we get the same observed result mentioned above
even if the tagged file is located in an EXT4 partition.

Comment 2 Nate Graham 2020-02-05 19:46:37 UTC


*** This bug has been marked as a duplicate of bug 401019 ***