Stack Smash from Wesnoth 1.14.13 (Debian)

Having trouble with the game? Report issues and get help here. Read this first!

Moderator: Forum Moderators

Forum rules
Before reporting issues in this section, you must read the following topic:
Post Reply
Voland0W
Posts: 1
Joined: October 7th, 2020, 2:55 pm

Stack Smash from Wesnoth 1.14.13 (Debian)

Post by Voland0W »

After upgrading from 1.14.5 to 1.14.13, starting Wesnoth fails with a report of a detected stack smashing:
~$ wesnoth
Battle for Wesnoth v1.14.13
Started on Wed Oct 7 07:34:53 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

Partial output of `dpkg -l wesnoth*`:
ii wesnoth-1.14-core 1:1.14.13-1 amd64 fantasy turn-based strategy game (branch 1.>
ii wesnoth-1.14-data 1:1.14.13-1 all data files for Wesnoth (branch 1.14)
ii wesnoth-1.14-music 1:1.14.5-1 all music files for Wesnoth (branch 1.14)

OS:
Linux bolanslaptop1 5.8.0-2-amd64 #1 SMP Debian 5.8.10-1 (2020-09-19) x86_64 GNU/Linux

It doesn't display the UI, so I am not able to get the build information, as directed on the How to Report a Bug Properly topic.

Update:
Reading the bug report on the Debian website, I learned that Wesnoth can be started with `wesnoth --nocache`. Upon doing that, I could get the build information:
The Battle for Wesnoth version 1.14.13
Running on Debian GNU/Linux bullseye/sid
Distribution channel: Default

Game paths
==========

Data dir: /usr/share/games/wesnoth/1.14
User config dir: /home/USER/.config/wesnoth-1.14
User data dir: /home/USER/.config/wesnoth-1.14
Saves dir: /home/USER/.config/wesnoth-1.14/saves
Add-ons dir: /home/USER/.config/wesnoth-1.14/data/add-ons
Cache dir: /home/USER/.config/wesnoth-1.14/cache

Libraries
=========

Boost: 1.71
Cairo: 1.16.0 (runtime 1.16.0)
Pango: 1.44.7 (runtime 1.46.2)
SDL: 2.0.12 (runtime 2.0.12)
SDL_image: 2.0.5 (runtime 2.0.5)
SDL_mixer: 2.0.4 (runtime 2.0.4)
SDL_ttf: 2.0.15 (runtime 2.0.15)

Features
========

JPEG screenshots: yes
Lua console completion: yes
Legacy bidirectional rendering: yes
D-Bus notifications back end: yes

Current video settings
======================

Current pixel resolution: 1366x768
Refresh rate: 60
SDL reports: 100.862x101.074 dots per inch.

Installed add-ons
=================

No add-ons installed.

Second Update: Upon further reading of the Debian bug report, it looks like a mismatch between libwolfssl versions or the headers. See https://bugs.debian.org/cgi-bin/bugrepo ... bug=970520

Third Update: I down-graded libwolfssl from 4.5.0 to 4.4.0, and Wesnoth starts up normally, now. I may ought to change the post title to Upgrade libwolfssl in Build, or something like that. ... Oh, that doesn't seem to be an option.
User avatar
Pentarctagon
Project Manager
Posts: 4532
Joined: March 22nd, 2009, 10:50 pm
Location: Earth (occasionally)

Re: Stack Smash from Wesnoth 1.14.13 (Debian)

Post by Pentarctagon »

Wesnoth doesn't use wolfssl itself - that's a change Debian made since openssl's license prior to version 3 isn't compatible with the GPL - it uses openssl. As far as we're concerned though, the license incompatibility problem will solve itself once openssl 3 is made available, so any problems caused by wolfssl would need to be solved by Debian as well.
99 little bugs in the code, 99 little bugs
take one down, patch it around
-2,147,483,648 little bugs in the code
Post Reply