Bug 2031642 - SDL_mixer double-free causes tuxmath crash at startup
Summary: SDL_mixer double-free causes tuxmath crash at startup
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: SDL_mixer
Version: 38
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Gwyn Ciesla
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-12-13 06:22 UTC by Nicolas De Amicis
Modified: 2023-05-26 01:50 UTC (History)
6 users (show)

Fixed In Version: SDL_mixer-1.2.12-29.fc39 SDL_mixer-1.2.12-29.fc37 SDL_mixer-1.2.12-29.fc38
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-05-17 12:00:05 UTC
Type: Bug


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github libsdl-org sdl12-compat issues 289 0 None closed tuxmath segfaults at startup 2023-05-17 11:21:02 UTC
Github tux4kids tuxmath issues 25 0 None open Crash at launch 2022-07-21 19:18:04 UTC

Description Nicolas De Amicis 2021-12-13 06:22:40 UTC
Description of problem:
tuxmath doesn't work. It crash at startup. It's inusable.

Version-Release number of selected component (if applicable):
tuxmath-2.0.3-11.fc35.x86_64

How reproducible:
Install and start tuxmath

Steps to Reproduce:
1.sudo dnf install tuxmath
2.run tuxmath in console or on desktop (tested with plasma and mate)
3.

Actual results:
it crash

Expected results:


Additional info:
In console, I have these few outputs:
Initializing Tux4Kids-Common 0.1.1
free(): double free detected in tcache 2
Abandon (core dumped)

Comment 1 TianShixiong 2022-07-13 14:52:39 UTC
Have this problem on Fedora 36 x86_64 xfce desktop too.

Comment 2 Ben Cotton 2022-11-29 17:29:16 UTC
This message is a reminder that Fedora Linux 35 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '35'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 35 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 3 Ben Cotton 2022-12-13 16:05:52 UTC
Fedora Linux 35 entered end-of-life (EOL) status on 2022-12-13.

Fedora Linux 35 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 4 Andrea Musuruane 2023-04-10 10:30:01 UTC
This issue is still present in F37.

A workaround is to run tuxmath with the --nosound option.

Comment 5 Neal Gompa 2023-05-17 11:21:03 UTC
Per sdl12-compat upstream, the issue is a missing commit backported to the SDL_mixer package: https://github.com/libsdl-org/SDL_mixer/commit/23b6289224edb24fcb8266fce9647822b69c4298

Reassigning to SDL_mixer.

(Also verified it affects Fedora 38 and Rawhide, set to F38 for now)

Comment 6 Hans de Goede 2023-05-17 11:48:03 UTC
Thanks for figuring this out.

An updated SDL_mixer pkg with the upstream fix added is on its way to updates-testing now.

Comment 7 Fedora Update System 2023-05-17 11:58:43 UTC
FEDORA-2023-751baaa5c2 has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-751baaa5c2

Comment 8 Fedora Update System 2023-05-17 12:00:05 UTC
FEDORA-2023-751baaa5c2 has been pushed to the Fedora 39 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 9 Fedora Update System 2023-05-17 12:08:16 UTC
FEDORA-2023-bb42160bcb has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2023-bb42160bcb

Comment 10 Fedora Update System 2023-05-17 12:08:17 UTC
FEDORA-2023-5645d5d2eb has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-5645d5d2eb

Comment 11 Fedora Update System 2023-05-18 02:06:45 UTC
FEDORA-2023-5645d5d2eb has been pushed to the Fedora 38 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-5645d5d2eb`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-5645d5d2eb

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 12 Fedora Update System 2023-05-18 04:39:38 UTC
FEDORA-2023-bb42160bcb has been pushed to the Fedora 37 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-bb42160bcb`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-bb42160bcb

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 13 Fedora Update System 2023-05-26 01:30:51 UTC
FEDORA-2023-bb42160bcb has been pushed to the Fedora 37 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 14 Fedora Update System 2023-05-26 01:50:25 UTC
FEDORA-2023-5645d5d2eb has been pushed to the Fedora 38 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.