[resolved] Crash in 1.13 (Preferences)

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

Moderators: Forum Moderators, Developers

Forum rules
Before reporting issues in this section, you must read the following topic:
Post Reply
Posts: 4
Joined: March 4th, 2018, 2:22 pm

[resolved] Crash in 1.13 (Preferences)

Post by dleducq » March 6th, 2018, 1:14 pm

I've got a (systematic) crash in BfW 1.13.11 (already in 1.13.10, did'nt try previous dev versions), when accessing the preferences in main menu screen.
After investigation, this is due to the line :

Code: Select all

in the preferences file, replacing it with

Code: Select all

solved the problem...

I filed a bug report to the Red Hat Bugzilla : bug 1551609, with backtrace and all..

Code: Select all

The Battle for Wesnoth version 1.13.11
Running on Fedora release 27 (Twenty Seven)

Game paths

Data dir:        /usr/share/wesnoth
User config dir: /home/dleducq/.config/wesnoth
User data dir:   /home/dleducq/.local/share/wesnoth/1.13
Saves dir:       /home/dleducq/.local/share/wesnoth/1.13/saves
Add-ons dir:     /home/dleducq/.local/share/wesnoth/1.13/data/add-ons
Cache dir:       /home/dleducq/.cache/wesnoth


Boost:             1.64
OpenSSL/libcrypto: 1.1.0g  (runtime 1.1.0g)
Cairo:             1.15.10 (runtime 1.15.10)
Pango:             1.40.13 (runtime 1.40.13)
SDL:               2.0.7   (runtime 2.0.7)
SDL_image:         2.0.2   (runtime 2.0.2)
SDL_mixer:         2.0.2   (runtime 2.0.2)
SDL_ttf:           2.0.14  (runtime 2.0.14)
libpng:            1.6.31  (runtime 1.6.31)


Experimental OpenMP support:    no
PNG screenshots:                yes
Lua console completion:         no
Legacy bidirectional rendering: yes
D-Bus notifications back end:   no
Last edited by dleducq on March 9th, 2018, 1:40 pm, edited 1 time in total.

Posts: 340
Joined: April 24th, 2016, 4:18 pm

Re: Crash in 1.13 (Preferences)

Post by Tad_Carlucci » March 6th, 2018, 2:21 pm

We don't see Redhat bug reports and they don't forward them. Please open an Issue on our Github project. For more read "How to report a bug properly." in the read box at the top of this web page.
I forked real life and now I'm getting merge conflicts.

Posts: 240
Joined: July 13th, 2015, 9:53 pm
Location: Germany

Re: Crash in 1.13 (Preferences)

Post by Shiki » March 6th, 2018, 2:38 pm

redhat bugzilla wrote: You are not authorized to access bug #1551609. To see this bug, you must first log in to an account with the appropriate permissions.
Introduction to WML filtering and WML variables.
Active until mid-January.

Posts: 4
Joined: March 4th, 2018, 2:22 pm

Re: Crash in 1.13 (Preferences)

Post by dleducq » March 8th, 2018, 10:55 am

OK, I filed a bug report in Github: #2612
I don't see how to set the 'bug' category... Surely I don't have the perms...
Hope that helps, ask me for further details if needed.

Posts: 4
Joined: March 4th, 2018, 2:22 pm

Re: Crash in 1.13 (Preferences)

Post by dleducq » March 9th, 2018, 1:38 pm

Closed #2612 via 23a180b.
Thx :)

Post Reply