Hi I have a problem running the FlightGear simulator when I clic the program icon it start to load but after initializing subsistems it dissapear, I downloaded the rpms for suse 11 from RPM Search and installed them using yast.
I had no problem installing it from the games repo. There’s a few other packages needed, plib for one.
I used the opensuse software search, but followed the “results from” link to the games repository, right-clicked the “games.repo” file and copied the location to the clipboard. After that, it’s open terminal, and type "sudo zypper ar (middle click to paste). Then the program can be installed letting the package manager resolve any dependancys.
“sudo zypper ar http://download.opensuse.org/repositories/games/openSUSE_11.0/games.repo”
Well, i also have problems.I use openSUSE 10.2, default kernel (no internet connection) and FlightGear 1.0.0-16.5 and FlightGear-data-1.0.0-1.1. I also have 3D acceleration enabled over a Nvidia TNT2. No XGL, no compiz.
Well here we go…
A)Running in KDE menu, Flight gear crashes when “initializing subsystems”.
B)Running FlightGear by Konsole it shows
pruebas@suse-northwood:~> fgfs
Model Author: Unknown
Creation Date: 2002-01-01
Version: $Id: c172p.xml,v 1.18 2007-01-15 12:50:45 ehofman Exp $
Description: Cessna C-172
Violación de segmento
pruebas@suse-northwood:~>
C)Running by command, GNU debuggter says
GNU gdb 6.5
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type “show copying” to see the conditions.
There is absolutely no warranty for GDB. Type “show warranty” for details.
This GDB was configured as “i586-suse-linux”.
(gdb) exec-file fgfs
(gdb) run fgfs
Starting program: /usr/bin/fgfs fgfs
Using host libthread_db library “/lib/libthread_db.so.1”.
Failed to read a valid object file image from memory.
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1226582288 (LWP 15241)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
—Type <return> to continue, or q <return> to quit—
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
Fatal error: Failed to open file
at fgfs
(received from SimGear XML Parser)
Program exited normally.
(gdb) q
What’s wrong? I don’t know. Packages are from opensuse repositories only (get software service).
Furthermore, if I change FlightGear1.0.0-16.5 by FlightGear1.0.0-16.3 its the same. If i change FlightGear-data-1.0.0-1.1 by FlightGear-data-1.0.0-37.3 it gives me unsolved dependencies (old libraries, not availables at opensuse repos).
Sorry for the “huge” post.
I answer myself: the solution was uninstall FlightGear 1.0.0 and install the old packages 0.9.10 from
http://download.opensuse.org/distribution/10.2/repo/oss/suse/i586/FlightGear-0.9.10.29.i586.rpm
It’s sad that the best openSUSE (from my point of view) have been discontinued. I will download all the repositories to my hard disk to prevent future problems.
Novell, don’t remove the repos at least!! 
OK, Here we go.
I had been continually frustrated with the older version of FlightGear that comes with the OpenSuSE 11.0 Version repository on my AMD 64 bit machine, with a Nvidia graphics card. Finally I tried it the other day using KfreeFlight, another frustrating project. It was broken, so that was the final straw.
Solution! Remove it, and install Version 1.9 from source, along with the fgrun GUI.
How to:
-
Make sure that you have one of those cool 3D
graphics cards and that 3D acceleration is set up and
working. -
Download FlightGear version 1.9.1 source code from:
FlightGear Flight Simulator
*Download FlightGear base package (data) v 1.9.0 from:
FlightGear Flight Simulator
-
Download SimGear version 1.9.1 source code from:
SimGear Downloads -
Download Fgrun version 1.0.0-17.8.x86_64 rpm from:
RPM Search FlightGear-fgrun]=46
All the rest of these commands are done using the root account.
-
Use Yast to remove FlightGear, SimGear, Flightgear data & fgrun.
-
Install all the dependent libraries using this command:
zypper install plib openal openal-soft-devel freeglut freeglut-devel OpenSceneGraph gcc43 gcc boost-devel gcc-c++ freealut freealut-devel plib-devel libOpenSceneGraph-devel OpenSceneGraph-plugins automake libOpenThreads-devel
-
unzip the FlightGear-data-1.9.0.tar.bz2 file and install it:
cd /usr/share/FlightGeartar cvzf data.tgz data
rm -Rf data
cp <downloads_directory>/FlightGear-data-1.9.0.tar.bz2 .
tar --use-compress-program bzip2 -xvf FlightGear-data-1.9.0.tar.bz2
rm FlightGear-data-1.9.0.tar.bz2
chown <your_username>:users -Rf *
-
unzip and build SimGear:
tar xvzf SimGear-1.9.1.tar.gzcd SimGear-1.9.1
./configure --libdir=/usr/local/lib64 --with-jpeg-factory
make
make install
-
unzip and build FlightGear:
tar xvzf FlighGear-1.9.1.tar.gzcd FlighGear-1.9.1
./configure --prefix=/usr/local/lib64 --bindir=/usr/local/bin --with-threads --with-simgear=/usr/local --with-osg=/usr/local --libdir=/usr/local/lib64 --without-plib --datarootdir=/usr/local/share/FlightGear
make
make install
-
Install fgrun:
rpm -Uvh --nodeps FlightGear-fgrun-1.0.0-17.8.x86_64.rpm
– OK Well that should do it –
All that is left to do is to plug in your joystick and go into your user account and type in: > fgrun
The paths that fgrun needs are:
executable: /usr/local/bin/fgfs
FG_ROOT: /usr/share/FlightGear
I added more scenery by placing it in the $FG_ROOT/data/WorldScenery/ directory and unziping them.
Then just add $FG_ROOT/data/WorldScenery/ to fgrun.
You can add more aircraft by just placing them into the $FG_ROOT/data/Aircraft directory and using
unzip <aircraft_name>.zip
rm <aircraft_name>.zip
This worked very well for me 
References:
http://www.mail-archive.com/flightgear-users@lists.sourceforge.net/msg06599.html
> All the rest of these commands are done using the root account.
>
> ./configure --libdir=/usr/local/lib64 --with-jpeg-factory
>
> make
>
> make install
hmmmmm…i was thinking that running config and make as root was not
the best thing to do…but, i could be wrong…i was back in '73, once.
–
.~.
/V
/( )
natural^^-^^pilot
“hmmmmm…i was thinking that running config and make as root was not
the best thing to do…but, i could be wrong…i was back in '73, once.”
What would you recommend then? Rather than just a smug remark.
@ajwsurfer
I’ve tried running FG from the repos with not much success, until eventually I forgot it. Now with your very detailed howto I’ll give it another try. Thank you.
Incidentally, I think the guest may be right, usually the configure and make commands don’t require root privileges.
> What would you recommend then? Rather than just a smug remark.
well, i wasn’t trying to be smug, instead i was trying to be precise!
personally i always run both ./configure and make as a simple user,
and THEN su prior to make install…
ymmv (that is, i do NOT know if it is crucial or not for full system
wide integrity and security for root to be used only for the last
step, which is exactly why i wrote my remark as i did…)
i was just saying that every step-by-step compile instruction i ever
saw prior to yours did not include running those first two steps as root…
ok?
–
.~.
/V
/( )
natural^^-^^pilot
Thank you Natural Pilot, that is what I was hoping for.
So “configure” and “make” should be run in a user account rather than the the root account.
> So “configure” and “make” should be run in a user account rather than
> the the root account.
that is the usual way to do it…
and, you can run “make install” as a user, but then it only gets
installed to your /home/[user] directory…
(remember, Linux, like Unix is a system designed for many users
sharing one operating system…where most users don’t have root access
but still should be able to install a program they need…without
having to involve the system administrator)
–
brassy
I like Flight Gear, but I wonder why the packages are so out of date …
Well, i also have problems.I use openSUSE 10.2, default kernel (no
internet connection) and FlightGear 1.0.0-16.5 and
FlightGear-data-1.0.0-1.1. I also have 3D acceleration enabled over a
Nvidia TNT2. No XGL, no compiz.
Well here we go…
A)Running in KDE menu, Flight gear crashes when “initializing
subsystems”.
B)Running FlightGear by Konsole it shows
pruebas@suse-northwood:~> fgfs
Model Author: Unknown
Creation Date: 2002-01-01
Version: $Id: c172p.xml,v 1.18 2007-01-15 12:50:45 ehofman Exp
$
Description: Cessna C-172
Violación de segmento
pruebas@suse-northwood:~>
C)Running by command, GNU debuggter says
GNU gdb 6.5
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and
you are
welcome to change it and/or distribute copies of it under certain
conditions.
Type “show copying” to see the conditions.
There is absolutely no warranty for GDB. Type “show warranty” for
details.
This GDB was configured as “i586-suse-linux”.
(gdb) exec-file fgfs
(gdb) run fgfs
Starting program: /usr/bin/fgfs fgfs
Using host libthread_db library “/lib/libthread_db.so.1”.
Failed to read a valid object file image from memory.
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1226582288 (LWP 15241)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
—Type <return> to continue, or q <return> to quit—
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
Fatal error: Failed to open file
at fgfs
(received from SimGear XML Parser)
Program exited normally.
(gdb) q
What’s wrong? I don’t know. Packages are from opensuse repositories
only (get software service).
Furthermore, if I change FlightGear1.0.0-16.5 by FlightGear1.0.0-16.3
its the same. If i change FlightGear-data-1.0.0-1.1 by
FlightGear-data-1.0.0-37.3 it gives me unsolved dependencies (old
libraries, not availables at opensuse repos).
Sorry for the “huge” post.
–
dfreijeiro
dfreijeiro’s Profile: http://forums.opensuse.org/member.php?userid=16174
View this thread: http://forums.opensuse.org/showthread.php?t=391551
I answer myself: the solution was uninstall FlightGear 1.0.0 and install
the old packages 0.9.10 from
It’s sad that the best openSUSE (from my point of view) have been
discontinued. I will download all the repositories to my hard disk to
prevent future problems.
Novell, don’t remove the repos at least!!
–
dfreijeiro
dfreijeiro’s Profile: http://forums.opensuse.org/member.php?userid=16174
View this thread: http://forums.opensuse.org/showthread.php?t=391551