Bug 233648

Summary:	Marble crashs when typing something into search that cannot be found
Product:	[Applications] marble	Reporter:	Frank Niethardt <frank>
Component:	general	Assignee:	marble-bugs
Status:	RESOLVED WORKSFORME
Severity:	crash	CC:	nienhueser, tgridel
Priority:	NOR	Keywords:	investigated, triaged
Version:	unspecified
Target Milestone:	0.8 (KDE 4.3)
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed In:

Description Frank Niethardt 2010-04-07 22:28:05 UTC

Version:           0.9.2 (using KDE 4.4.2)
OS:                Linux
Installed from:    Archlinux Packages

When you type something in the search box, that cannot be found, press return and after that type in something different that is not in the cache, press return, marble will crash.

- start marble
- copy some coordinates - or anything different, that is not found - in the search box. I tried with coordinates..
- press return
- type in a city you have not searched for, but you know it is there
- press return
-> marble crashes

After trying to reproduce that a couple of times, it seems that the second search is cached and does not produce a crash anymore. But when I try a different city, it just crashes...

Comment 1 Dennis Nienhüser 2010-04-07 22:40:53 UTC

I couldn't reproduce it with marble from svn trunk and the Kubuntu package (Marble 0.9.2, KDE 4.4.2). I tried the following for both:

- Start Marble
- Copy coordinates from the map
- Put coordinates into the search box, enter
- Replace search text with 'Aachen', enter

I also tried different search terms. Can you reproduce the crash always after a fresh start of Marble? Is it maybe related to the time that passes between search requests?

Comment 2 Frank Niethardt 2010-04-07 23:10:29 UTC

mmh, right the time after I saw your message it didn't work for "Aachen" or "Cottbus", after a fresh start it did work for "Berlin" or "Leisnig"

I have KDEmod packages for Archlinux

Comment 3 Thibaut Gridel 2011-01-20 19:45:03 UTC

never saw such a problem occur with trunk for past years.
Please reopen if you can reproduce and give a backtrace.

Comment 4 Andrew Crouthamel 2018-09-19 14:30:48 UTC

This bug has had its resolution changed, but accidentally has been left in NEEDSINFO status. I am thus closing this bug and setting the status as RESOLVED to reflect the resolution change.