Hide Forgot
abrt version: 1.1.14 architecture: x86_64 Attached file: backtrace cmdline: fgfs comment: Install FlightGear with "yum install". Then attempt to run FlightGear. Splash Screen comes up then goes down. FlightGear crashes within 10 seconds of attempt to run. This does NOT give user much confidence when an application cannot even load. (But what the heck it is free.) component: FlightGear crash_function: nv50_program_validate executable: /usr/bin/fgfs kernel: 2.6.35.10-74.fc14.x86_64 package: FlightGear-2.0.0-4.fc14 rating: 4 reason: Process /usr/bin/fgfs was killed by signal 6 (SIGABRT) release: Fedora release 14 (Laughlin) time: 1295555698 uid: 500 How to reproduce ----- 1. Launched FlightGear from desktop icon 2. Splash Screen displays and then disappears 10 seconds after launch as FlightGear crashes 3. It appears FlightGear needs some QA.
Created attachment 474549 [details] File: backtrace
Package: FlightGear-2.0.0-4.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. ran fgfs 2. splash screen appears and states that it is loading scenery 3. fgfs crashes on scenery loading
Package: FlightGear-2.0.0-4.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Launch FlightGear from the KDE desktop. 2. 3.
I assume you see this error message when starting the program from command line: [bellet@monkey ~]$ fgfs nv50_screen_get_param:162 - Unknown PIPE_CAP 11 FGMultiplayMgr - No receiver port, Multiplayermode disabled KI266 dme indicator #0 initialized loading scenario 'nimitz_demo' creating 3D noise texture... DONE Cannot connect to server socket err = No such file or directory Cannot connect to server socket jack server is not running or cannot be started Initializing Nasal Electrical System nv50_program_tx_insn:3191 - invalid opcode 71 fgfs: nv50_program.c:4138: nv50_program_validate: Assertion `0' failed. Aborted (core dumped) In this case, that is a problem with the driver of the nvidia graphic card (nouveau), that has been fixed in the upcoming Fedora 15 release. So I'll close this bug, as I think the nouveau driver won't have a major update during Fedora 14 life cycle. Feel free to reopen this case if the problem still persists in Fedora 15.
*** Bug 668492 has been marked as a duplicate of this bug. ***
*** Bug 655344 has been marked as a duplicate of this bug. ***