Bug 258955

Summary:	Restore tag autocompletion in the search box
Product:	[Applications] dolphin	Reporter:	fatgerman
Component:	search	Assignee:	Dolphin Bug Assignee <dolphin-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	adrian
Priority:	NOR
Version:	2.1
Target Milestone:	---
Platform:	Chakra
OS:	Linux
Latest Commit:		Version Fixed In:

Description fatgerman 2010-12-06 00:39:16 UTC

Version:           unspecified (using KDE 4.5.80) 
OS:                Linux

I can enable the Search toolbar, but nothing appears. Under KDE 4.5 there was a text entry box from which I could initiate Nepomuk searches. There is now no way to do Nepomuk searches (the KFind integration doesn't achieve the same goal)

Reproducible: Always

Steps to Reproduce:
I've installed the Kubuntu packages from their beta ppa, upgrading KDE 4.5.3. Perhaps the upgrade went wrong?

Comment 1 Peter Penz 2010-12-06 09:41:19 UTC

Thanks for the report. If you can still see the search toolbar entry in your installation, then something went wrong with your update. The search toolbar has been removed and the KFind integration is now a replacement for this which also supports Nepomuk search. If something does not work with the searching and Nepomuk, please let us know.

Comment 2 fatgerman 2010-12-06 12:38:59 UTC

In my installation the KFind integration does not perform Nepomuk searches.
In the old Search toolbar, as I start to type the name of a Tag it would give me a drop-down showing me the tags that match what I type, then I could select one. This was seriously useful.

Using the new KFind find box, typing Tag names produces no drop-down menu, and no files are found when I type in a Tag name and search, nor when I type in hasTag:"TagName".

Comment 3 Peter Penz 2010-12-06 13:12:33 UTC

Thanks for the update, I'll will try to restore this functionality in the scope of this report.

Comment 4 Jeroen van Meeuwen (Kolab Systems) 2012-08-24 16:22:28 UTC

Resetting assignee to default as per bug #305719

Comment 5 Frank Reininghaus 2013-05-12 20:32:04 UTC


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