Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 1970553

Summary: impressive segfaults on F34 because of too recent version of python3-pygame
Product: [Fedora] Fedora Reporter: Benedikt Gollatz <benedikt>
Component: impressiveAssignee: Michael J Gruber <mjg>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 34CC: gwync, mjg
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: impressive-0.13.0-0.8.20210612svn311.fc34 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-06-14 01:05:53 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Benedikt Gollatz 2021-06-10 17:08:44 UTC
Description of problem:

impressive segfaults in SDL when run on Fedora 34. This seems to be due to Fedora 34 including pygame 2.0.1, whereas Fedora 33 shipped pygame 1.9.6.

Version-Release number of selected component (if applicable):

impressive-0.13.0-0.6.20210107svn310.fc34.x86_64
python3-pygame-2.0.1-2.fc34.x86_64

How reproducible:

Always

Steps to Reproduce:
1. Run impressive on any file or directory with displayable content.
2.
3.

Actual results:

Segementation fault

Expected results:

A presentation.

Additional info:

Downgrading pygame to python3-pygame-1.9.6-9.fc33.x86_64 from Fedora 33 fixes the problem.

Comment 1 Michael J Gruber 2021-06-10 21:09:04 UTC
Thanks for the report.

This is a crash in impressive's OpenGL loader, as soon as it tries to use SDL_GL_GetProcAddress on any GL function.

The version in F34 is the latest from svn already, which contains a commit supposedly making some things work with pygame-2.0.1 already. Upstream is pretty dead, though.

@gwync Do you have an idea what changed between pygame-1.9.6 and 2.0.1 in terms of GL loading? (I'm also wondering why impressive needs to do the loading manually, oh well....)

Comment 2 Gwyn Ciesla 2021-06-10 21:20:37 UTC
I do not. Nothing jumped out at me in the changelog, or in my testing.

Comment 3 Fedora Update System 2021-06-12 10:45:23 UTC
FEDORA-2021-48f1c98ad1 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-48f1c98ad1

Comment 4 Michael J Gruber 2021-06-12 13:13:36 UTC
I'd like to emphasize that the update is made possible by a *very speedy* response from upstream! So, while the commit rate upstream might be slow, the contact is alive and well :)

The bug occured because impressive did not find SDL2 in Fedora - searching for SDL (due to a packaging error) lead to a seg fault, searching for SDL2 lead to an exception (due to a missing search path upstream). Both are corrected now.

pygame was not involved other than switching from SDL to SDL2 in pygame 2.0.*. While looking there, I noticed a few unrelated (and uncritical) issues which will be the subject of an upcoming PR.

Looking forward to a test report from the original reporter ;)

Comment 5 Fedora Update System 2021-06-13 01:03:43 UTC
FEDORA-2021-48f1c98ad1 has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-48f1c98ad1`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-48f1c98ad1

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

Comment 6 Fedora Update System 2021-06-14 01:05:53 UTC
FEDORA-2021-48f1c98ad1 has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.