Hide Forgot
Description of problem: 1. Install FlightGear from fedora's repository 1a. Run FG, all works fine 2. download A380_1.2.zip and e020n50.tgz, e020n60.tgz, e030n50.tgz, e030n60.tgz 3. Run FG, it craches just after loading is complete Bug repeats on nvidia 331.20 drivers from repos and from nvidia site. On neuveau FG don't start at all: Your system currently is not capable of hardware accelerated 3D. Therefore fgfs cannot run. Usually the cause of this error is that there are no Free Software drivers for your graphics card, please contact your graphics card manufacturer and kindly ask them to provide Free Software support for your card. xorg-x11-drv-nouveau x86_64 epoch 1 version 1.0.9 release 2.fc20 Fedora 20 x86_64, KDE, Video Gigabyte GT 610 Version-Release number of selected component: FlightGear-2.12.0-1.fc20 Additional info: reporter: libreport-2.1.9 backtrace_rating: 4 cmdline: fgfs crash_function: unref executable: /usr/bin/fgfs kernel: 3.11.10-301.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 0 (10 frames) #5 unref at /usr/include/osg/Referenced:198 #6 ~ref_ptr at /usr/include/osg/ref_ptr:35 #7 osgDB::ReaderWriter::ReadResult::~ReadResult at /usr/include/osgDB/ReaderWriter:103 #8 (anonymous namespace)::(anonymous namespace)::setAttrs at /usr/src/debug/simgear-2.12.0/simgear/scene/material/TextureBuilder.cxx:264 #9 simgear::TexBuilder<osg::Texture2D>::build at /usr/src/debug/simgear-2.12.0/simgear/scene/material/TextureBuilder.cxx:303 #10 simgear::TextureUnitBuilder::buildAttribute at /usr/src/debug/simgear-2.12.0/simgear/scene/material/TextureBuilder.cxx:133 #11 simgear::buildPass at /usr/src/debug/simgear-2.12.0/simgear/scene/material/Effect.cxx:168 #12 simgear::buildTechnique at /usr/src/debug/simgear-2.12.0/simgear/scene/material/Effect.cxx:1202 #13 simgear::Effect::realizeTechniques at /usr/src/debug/simgear-2.12.0/simgear/scene/material/Effect.cxx:1287 #14 SGMaterial::get_effect at /usr/src/debug/simgear-2.12.0/simgear/scene/material/mat.cxx:450
Created attachment 837164 [details] File: backtrace
Created attachment 837165 [details] File: cgroup
Created attachment 837166 [details] File: core_backtrace
Created attachment 837167 [details] File: dso_list
Created attachment 837168 [details] File: environ
Created attachment 837169 [details] File: limits
Created attachment 837170 [details] File: maps
Created attachment 837171 [details] File: open_fds
Created attachment 837172 [details] File: proc_pid_status
Created attachment 837173 [details] File: var_log_messages
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora 'version' of '20'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.