Bug 597702 - [abrt] crash in FlightGear-2.0.0-1.fc13: Process /usr/bin/fgfs was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in FlightGear-2.0.0-1.fc13: Process /usr/bin/fgfs was killed by ...
Keywords:
Status: CLOSED DUPLICATE of bug 590490
Alias: None
Product: Fedora
Classification: Fedora
Component: FlightGear
Version: 13
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Fabrice Bellet
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:0cf94479201b054bff81234bcf5...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-30 07:48 UTC by Richard Keech
Modified: 2010-06-08 08:09 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-06-08 08:09:50 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (14.77 KB, text/plain)
2010-05-30 07:48 UTC, Richard Keech
no flags Details

Description Richard Keech 2010-05-30 07:48:21 UTC
abrt 1.1.0 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: fgfs
component: FlightGear
crash_function: flightgear::CameraGroup::buildGUICamera
executable: /usr/bin/fgfs
global_uuid: 0cf94479201b054bff81234bcf56f7d23b8a9a11
kernel: 2.6.33.4-95.fc13.i686
package: FlightGear-2.0.0-1.fc13
rating: 4
reason: Process /usr/bin/fgfs was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

comment
-----
Same error both with and without mesa-dri-drivers-experimental.
Other programs seem to run without error including Extreme Tuxracer.
System has NVidea card with nouveau driver



How to reproduce
-----
1. Installed FlightGear-2.0.0-1.fc13.i686 from repo
2. run
3. fails immediately with 
"Error: Not able to create requested visual.
Error: Not able to create requested visual."

Comment 1 Richard Keech 2010-05-30 07:48:24 UTC
Created attachment 417991 [details]
File: backtrace

Comment 2 Fabrice Bellet 2010-06-08 08:09:50 UTC

*** This bug has been marked as a duplicate of bug 590490 ***


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