wesnoth-1.14 crashes on groovy

[Hans-Peter]

This is my system (from screenfetch)

OS: Ubuntu 20.10 groovy
Kernel: x86_64 Linux 5.8.0-25-generic
Uptime: 2h 6m
Packages: 2881
Shell: bash 5.0.17
Resolution: 1680x1050
DE: KDE 5.74.0 / Plasma 5.19.5
WM: KWin
GTK Theme: Breeze [GTK2/3]
Icon Theme: breeze
Disk: 82G / 110G (79%)
CPU: AMD Phenom 8600B Triple-Core @ 3x 2.3GHz
GPU: AMD RS780 (DRM 2.50.0 / 5.8.0-25-generic, LLVM 11.0.0)
RAM: 2641MiB / 3664MiB

And since updating to groovy, wesnoth crashes with a flicker of the screen.
And this is what it says:

hp@hp:~$ wesnoth
Battle for Wesnoth v1.14.13
Started on Wed Oct 28 11:12:58 2020

Data directory: /usr/share/games/wesnoth/1.14
User configuration directory: /home/USER/.config/wesnoth-1.14
User data directory: /home/USER/.config/wesnoth-1.14
Cache directory: /home/USER/.config/wesnoth-1.14/cache

Setting mode to 1280x720
*** stack smashing detected ***: terminated
Aborted (core dumped)
hp@hp:~$

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: wesnoth 1:1.14.13-1build2
ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
Uname: Linux 5.8.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu50
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Wed Oct 28 11:09:20 2020
InstallationDate: Installed on 2018-10-01 (757 days ago)
InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
PackageArchitecture: all
SourcePackage: wesnoth-1.14
UpgradeStatus: Upgraded to groovy on 2020-10-09 (18 days ago)

[Hans Joachim Desserud (hjd)]

Thanks for reporting.

Marking confirmed as I get the same error message when attempting to run wesnoth on Ubuntu 20.10. I also found a corresponding Debian bug report, so I have attached a bug watch.

[Andrea Agnolin (agno94)]

Same crash and error message.

[Andrea Agnolin (agno94)]

The flatpak version seams to work just fine. So using it is possible workaround.

[Tomasz Sal (rtadf)]

Same.
wesnoth --nocache
is another workaround.

[Ziggy Smith (ziggy537)]

compiling from source worked for me

[nomike (michael-postmann)]

This was fixed in upstream https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970520.

---8<---
It was introduced by the Debian builder, using libwolfssl, instead of openssl, due to licensing issues.
--->8---

[nomike (michael-postmann)]

It could be solved by pulling the latest version from upstream.