Crashing on Httt scenario The Elven Council
Moderator: Forum Moderators
Forum rules
Before reporting issues in this section, you must read the following topic:
Before reporting issues in this section, you must read the following topic:
Crashing on Httt scenario The Elven Council
Hello, I've been playing the Heir To The Throne campaign and it has crashed on The Elven Council scenario.
- My computer is running Ubuntu 20.04 with wesnoth installed via apt; that is, version 1.14.9.
- The build information is:
The Battle for Wesnoth version 1.14.9
Running on Ubuntu 20.04 LTS
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
OpenSSL/libcrypto: 1.1.1e-dev (runtime 1.1.1f)
Cairo: 1.16.0 (runtime 1.16.0)
Pango: 1.44.7 (runtime 1.44.7)
SDL: 2.0.10 (runtime 2.0.10)
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
========
JPG screenshots: yes
Lua console completion: yes
Legacy bidirectional rendering: yes
D-Bus notifications back end: yes - The crash happened while playing, but it can also be reproduced by starting a fresh campaign of Heir To The Throne and typing into the console
to enter debug mode and choose a scenario and then selecting the scenario The Elven Council.
Code: Select all
debug cl
- The logs do not provide any information at all:
Code: Select all
Battle for Wesnoth v1.14.9 Started on Tue Jun 16 14:16:51 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 1920x1016 Checking lua scripts... ok
- Pentarctagon
- Project Manager
- Posts: 5564
- Joined: March 22nd, 2009, 10:50 pm
- Location: Earth (occasionally)
Re: Crashing on Httt scenario The Elven Council
If possible, I would suggest using the Steam or Flatpak version instead. 1.14.10 specifically had a fix for using SDL 2.0.10, and 1.14.13 had fixes for a memory leak as well as a significant engine bug.
99 little bugs in the code, 99 little bugs
take one down, patch it around
-2,147,483,648 little bugs in the code
take one down, patch it around
-2,147,483,648 little bugs in the code
Re: Crashing on Httt scenario The Elven Council
Thank you for the recomendadion, I think I'll do so, but, is there a way to migrate my progress?
Re: Crashing on Httt scenario The Elven Council
I just realized how to migrate my progress (the build information tells the saved games directory). However, it still crashes the same way in the elven council, it draws some hexagons with the rest of hexagons in black and the first dialog from the scenario; and then it all goes black.
I also just discovered how to skip the scenario without using debug mode by just pressing Esc, so it is a kind of workaround since the scenario is just dialog.
I also just discovered how to skip the scenario without using debug mode by just pressing Esc, so it is a kind of workaround since the scenario is just dialog.
- Pentarctagon
- Project Manager
- Posts: 5564
- Joined: March 22nd, 2009, 10:50 pm
- Location: Earth (occasionally)
Re: Crashing on Httt scenario The Elven Council
This should be fixed now. The issue was that the game was built with SDL 2.0.9 but was using 2.0.10 at runtime.raul wrote: ↑June 17th, 2020, 1:31 pm I just realized how to migrate my progress (the build information tells the saved games directory). However, it still crashes the same way in the elven council, it draws some hexagons with the rest of hexagons in black and the first dialog from the scenario; and then it all goes black.
I also just discovered how to skip the scenario without using debug mode by just pressing Esc, so it is a kind of workaround since the scenario is just dialog.
99 little bugs in the code, 99 little bugs
take one down, patch it around
-2,147,483,648 little bugs in the code
take one down, patch it around
-2,147,483,648 little bugs in the code