Bug 463911 - supertux segfaults at startup
supertux segfaults at startup
Product: Fedora
Classification: Fedora
Component: supertux (Show other bugs)
x86_64 Linux
medium Severity medium
: ---
: ---
Assigned To: Steven Pritchard
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-09-25 06:25 EDT by Aioanei Rares
Modified: 2009-12-18 01:26 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-12-18 01:26:05 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Aioanei Rares 2008-09-25 06:25:44 EDT
Description of problem:

When starting supertux from commandline, in order to get some messages, i get the following : 
/home/arares> supertux
[/home/arares/.supertux] is in the search path
[/usr/share/supertux] is in the search path
Couldn't load config file: Couldn't open file 'config': No such file or directory, using default settings
fullscreen 800x600 Ratio: 1.33333
Segmentation fault

No matter if i choose the verbose flag or any other one, i only get these messages...the screen goes blank for two or so seconds and that's all.

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


How reproducible:


Steps to Reproduce:
1.start supertux
Actual results:

Segmentation fault

Expected results:

A working supertux
Additional info:
Comment 1 Aioanei Rares 2008-11-04 02:27:54 EST
It works now , but it's so slow as if it needs hardware acceleration drivers (aka Nvidia's)...afaict, it works with nv only. Long story short, it's slowness
makes it unusable.
Comment 2 Bug Zapper 2008-11-25 22:13:02 EST
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle.
Changing version to '10'.

More information and reason for this action is here:
Comment 3 Bug Zapper 2009-11-18 03:25:35 EST
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10.  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 WONTFIX if it remains open with a Fedora 
'version' of '10'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 10's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 10 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
Comment 4 Bug Zapper 2009-12-18 01:26:05 EST
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 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 please feel free to reopen this bug against that version.

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

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