Bug 570298 - [abrt] crash in celestia-1.5.1-2.fc12: Process /usr/bin/celestia was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in celestia-1.5.1-2.fc12: Process /usr/bin/celestia was killed b...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: celestia
Version: 12
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Steven Pritchard
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:d6db17e0dea36df5325302619db...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-03-03 19:41 UTC by John Vincent
Modified: 2010-12-03 22:04 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-12-03 22:04:41 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (20.74 KB, text/plain)
2010-03-03 19:41 UTC, John Vincent
no flags Details

Description John Vincent 2010-03-03 19:41:37 UTC
abrt 1.0.7 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: celestia
component: celestia
executable: /usr/bin/celestia
kernel: 2.6.31.12-174.2.22.fc12.i686.PAE
package: celestia-1.5.1-2.fc12
rating: 4
reason: Process /usr/bin/celestia was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)

comment
-----
As well as this crash backtrace, I have some more information:
1. I'm using a ATI radeon video card
2. If I don't start the kernel with the "nomodeset" option, the whole PC freezes (display freezes, keyboard is unresponsive, caps-lock doesn't make the light go on/off) so I have to power-cycle the machine
3. if I start with "nomodeset" and the default Xserver config I get this crash
4. if I start with "nomodeset" and use "system-config-display" to set the display to "thousands of colours" then the program does not crash, but the whole screen is dark green, so this is not an acceptable work-around.

I hope this explanation can help someone find and fix this problem. Thanks.

How to reproduce
-----
1. run celestia
2. wait a few seconds
3. it crashes

Comment 1 John Vincent 2010-03-03 19:41:39 UTC
Created attachment 397646 [details]
File: backtrace

Comment 2 John Vincent 2010-03-03 19:47:35 UTC
Just re-reading my discription, I should make it clear that whether or not I use the "nomodeset" kernel option, I only have a problem when trying to run celestia, not at any other time.

Comment 3 John Vincent 2010-03-04 13:53:08 UTC
I created an xorg.conf file and in that I added the two lines:

 Option      "RenderAccel" "false"
 Option      "Accel" "Off"

so the entire section looked like this:

Section "Device"
        Identifier  "Videocard0"
        Driver      "radeon"
        Option      "RenderAccel" "false"
        Option      "Accel" "Off"
EndSection

after doing this celestia now runs bug-free (except for being very slow) so I guess this is a bug in the radeon driver, not in celestia...

Comment 4 John Vincent 2010-03-12 00:24:42 UTC
Got updates for the kernel and X11. Celestia works OK now! :-)

Comment 5 Bug Zapper 2010-11-03 20:51:40 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  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 '12'.

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 12'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 12 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: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 6 Bug Zapper 2010-12-03 22:04:41 UTC
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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.