Confirming $ wesnoth --nocache works here too.But what is causing this? Is this an upstream bug? Or one debian introduces?
- Bug#970520: wesnoth: Crash on starting wesnoth - stack... Max Hofer
- Bug#970520: The same bug Max Minenko
- Bug#970520: wesnoth: Crash on starting wesnoth - ... Davide Prina
- Bug#970520: Max Minenko
- Bug#970520: confirm workaround Benedikt Hallinger
- Bug#970520: wesnoth: Crash on starting wesnoth - ... Bernhard Übelacker
- Bug#970520: wesnoth: Crash on starting wesnot... Felix Lechner
- Bug#970520: confirm workaround Adrian Heine
- Bug#970520: confirm workaround Bolan Moonward