Wesnoth 1.17.1 fails on startup. Floating point exception (core dumped)

[dsime42]

###When reporting a bug, make sure that you include the following:
###
### Operating system, including its version; and Wesnoth version, including the configured language.

# dnf update
Last metadata expiration check: 3:36:36 ago on Sun 06 Nov 2022 11:49:47 AM PST.
Dependencies resolved.
Nothing to do.
Complete!

# uname -r
6.0.5-200.fc36.x86_64
# cat /etc/redhat-release
Fedora release 36 (Thirty Six)
# yum list |grep -i wesnoth
wesnoth.x86_64 1.17.7-1.fc36 @updates
wesnoth-data.noarch 1.17.7-1.fc36 @updates
wesnoth-server.x86_64 1.17.7-1.fc36 updates
wesnoth-tools.x86_64 1.17.7-1.fc36 updates

### If you installed Wesnoth from a Linux repository using the terminal, make sure that you downloaded the full package that includes all campaigns and ###music.
### The build information provided by the game by clicking on the Image icon on the bottom-left corner of the main menu and then the Image Copy button.

Game fails on startup -- not able to click on build information

### A step-by-step walkthrough of how to reproduce the problem.

Click on desktop icon (loading page appears and says "Loading game configuration"
OR
Issue "wesnoth" from command line
$ wesnoth
Battle for Wesnoth v1.17.7 x86_64
Started on Sun Nov 6 15:33:40 2022


Data directory: /usr/share/wesnoth
User configuration directory: /home/USER/.config/wesnoth
User data directory: /home/USER/.local/share/wesnoth/1.17
Cache directory: /home/USER/.cache/wesnoth


Setting mode to 1920x1144
Floating point exception (core dumped)


### If the problem cannot be reproduced, our ability to identify its cause and fix it will be severely limited.
### Locate the game logs and include them in your post, either in a

Code: Select all

 block or (for large/long logs) a file attachment.
###
### Additionally, whenever possible and applicable:
###
###    Attach a relevant saved game, as this is the easiest way for developers to reproduce errors that occur during gameplay.
###    If you are reporting a crash-to-desktop and you are on Linux, macOS, or other Unix-like operating systems, 
### do consider obtaining an execution backtrace of the game process and including it in your report.

[dsime42]

It looks like this thing got submitted while I was typing it up.

[Pentarctagon]

Does this happen when installed via flatpak or steam?

[dsime42]

I haven't tried flatpack and I don't use steam.

The problem started after upgrading from FC35 to FC36.

I thought it might be a version incompatability and so I uninstalled wesnoth and cleaned all references to wesnoth under /home.

I did have a problem with FC35 that cleared with the upgrade, I think it had something to do with pipewire.

[Pentarctagon]

I'd recommend using one of those, since those are created directly by the Wesnoth team and run in a more controlled container environment. Otherwise, if you upgraded Fedora and that caused Wesnoth to break, I'd lean towards the problem being caused by Fedora even if it does ultimately end up needing a fix implemented in Wesnoth.

Also, as a side note, your report is about 1.17.7, not 1.17.1. The -1 in 1.17.7-1 is Fedora-specific; the Wesnoth version is just the 1.17.7 part. The most recent version is also 1.17.9.

[dsime42]

Also, as a side note, your report is about 1.17.7, not 1.17.1. The -1 in 1.17.7-1 is Fedora-specific; the Wesnoth version is just the 1.17.7 part.

Yeah, thanks I see from my post:

$ wesnoth
Battle for Wesnoth v1.17.7 x86_64

and
wesnoth.x86_64 1.17.7-1.fc36 @updates

and I know that the "last dot number" is Fedora's build number so I just brain farted the 1.17.1

Which leads me to the resolution

I was preparing to install the flatpack, and after "dnf remove wesnoth" and "find /home -type d |grep -i wesnoth"

I found these two files:
~/.cache/gnome-software/odrs/org.wesnoth.Wesnoth.desktop.json
~/.config/wesnoth/preferences

After removing them I was able to reload Wesnoth and start the game.
Sloppy
Retired for 10 years and doing sloppy work.

Thanks for your help