Bug 492742 - SDL hangs on initialization
SDL hangs on initialization
Status: CLOSED WORKSFORME
Product: Fedora
Classification: Fedora
Component: SDL (Show other bugs)
10
All Linux
low Severity high
: ---
: ---
Assigned To: Thomas Woerner
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2009-03-29 03:49 EDT by Penelope Fudd
Modified: 2009-03-29 04:04 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2009-03-29 04:04:32 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Output of strace -fo/tmp/trace.out berusky (51.82 KB, text/plain)
2009-03-29 03:49 EDT, Penelope Fudd
no flags Details

  None (edit)
Description Penelope Fudd 2009-03-29 03:49:18 EDT
Created attachment 337147 [details]
Output of strace -fo/tmp/trace.out berusky

Description of problem:
I'm attempting to run any SDL-based game.  They all hang after printing 'SDL Init' or some variation thereof.  I've temporarily disabled SElinux, to no effect.

Version-Release number of selected component (if applicable):
SDL-1.2.13-7.fc10.i386

How reproducible:
Always

Steps to Reproduce:
1. Try running an SDL game, such as 'berusky' from the command line.
2. See 'SDL Init...' show up on the screen
  
Actual results:
The program hangs

Expected results:
The program runs

Additional info:
I'm attaching the output of 'strace -fo/tmp/trace.out berusky'.  It's not that berusky is the program I want to run, but it's the first SDL program I found in the Fedora RPM repository.
Comment 1 Penelope Fudd 2009-03-29 04:04:32 EDT
Problem fixed.

I logged in again, updated all of my rpms, and it started to work.  Here is the list of rpms updated:

devhelp-0.22-6.fc10.i386
firefox-3.0.8-1.fc10.i386
gimp-2.6.6-1.fc10.i386
gimp-help-browser-2.6.6-1.fc10.i386
gimp-libs-2.6.6-1.fc10.i386
gnome-python2-extras-2.19.1-28.fc10.i386
gnome-python2-gtkhtml2-2.19.1-28.fc10.i386
gnome-python2-libegg-2.19.1-28.fc10.i386
htdig-3.2.0-0.3.b6.fc10.i386
imsettings-0.105.1-4.fc10.i386
imsettings-libs-0.105.1-4.fc10.i386
java-1.6.0-openjdk-1.6.0.0-13.b14.fc10.i386
java-1.6.0-openjdk-plugin-1.6.0.0-13.b14.fc10.i386
kdebase3-3.5.10-4.fc10.i386
kdebase3-libs-3.5.10-4.fc10.i386
kdebase3-pim-ioslaves-3.5.10-4.fc10.i386
kdebase-runtime-4.2.1-2.fc10.i386
kdebase-runtime-libs-4.2.1-2.fc10.i386
libmtp-0.3.7-1.fc10.i386
libX11-1.1.5-2.fc10.i386
libX11-devel-1.1.5-2.fc10.i386
NetworkManager-0.7.0.99-5.git20090326.fc10.i386
NetworkManager-glib-0.7.0.99-5.git20090326.fc10.i386
NetworkManager-gnome-0.7.0.99-5.git20090326.fc10.i386
ntfs-3g-2009.3.8-1.fc10.i386
rhino-1.7-0.3.r2pre.1.1.fc10.noarch
system-config-keyboard-1.2.15-5.fc10.noarch
xulrunner-1.9.0.8-1.fc10.i386
xulrunner-devel-1.9.0.8-1.fc10.i386
yelp-2.24.0-7.fc10.i386

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