Bug 318501

Summary:	Search result completer stops working after one or more attempts
Product:	[Applications] marble	Reporter:	Bernhard Beschow <shentey>
Component:	general	Assignee:	marble-bugs
Status:	RESOLVED WORKSFORME
Severity:	major	CC:	nienhueser
Priority:	NOR
Version:	1.5 (KDE 4.10)
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed In:

Description Bernhard Beschow 2013-04-17 12:06:23 UTC

When searching for "Karlsruhe" (without pressing Enter afterwards, i.e. not triggering a network request), it's possible to click on the search result and be taken to Karlsruhe. When searching further for "Berlin" (again w/o hitting Enter afterwards), clicking on a search result does not take one to Berlin.

Reproducible: Always

Steps to Reproduce:
1. Type "Karlsruhe" into search field w/o hitting Enter -> a result list pops up
2. Select Karlsruhe from the list pop up -> Marble jumps to Karlsruhe
3. Overwrite the search field with "Berlin" w/o hitting Enter -> a result list pops up
Actual Results:  
Clicking the search result doesn't take one to Berlin. Hitting Enter performs a network search.

Expected Results:  
Clicking the search result OR selecting the search result and hitting Enter should take one to Berlin. A network request should not be made.

I believe this regression was introduced when the search field was moved to the toolbar.

Comment 1 Dennis Nienhüser 2013-04-21 17:22:52 UTC

I can reproduce that, although it does not happen always on the first attempt here. Sometimes several completions work fine in a row. The problem is that the completer stops emitting the activated() signal.

I looked into MarbleLineEdit to see if its mouseReleaseEvent interferes, but found nothing suspicious. Another possible error source could be modifications to MarblePlacemarkModel which somehow invalidate model indices in the proxy model chain. Then again a simple completion should not trigger a search at all, hence not modify MarblePlacemarkModel or the shared tree model.

Comment 2 Justin Zobel 2021-03-09 22:51:36 UTC

Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.