Follow-up Comment #2, bug #18769 (project wesnoth):
Hmmm...not sure what I'm doing wrong with entering the command line, will
have to work on it more later.
I did find a way that always produces the bug:
Just launch wesnoth with an empty cache folder, and at the title screen
before doing anything else, press f5.
The same message as below appears in stderr.
_______________________________________________________
Reply to this item at:
<http://gna.org/bugs/?18769>
_______________________________________________
Message sent via/by Gna!
http://gna.org/
_______________________________________________
Wesnoth-bugs mailing list
[email protected]
https://mail.gna.org/listinfo/wesnoth-bugs
