FG 2017.3.1 Upgrade to 2018.1.1 failed

[flywisher]

Thorsten, saiarcot895 and V12 are right. When I start Flightgear from the console, asking for the launcher, as "fgfs --launcher", it responds with "!Launcher was requested, but FlightGear was compiled without Qt suppport!"

Incidentally, when I click on File->Aircraft Center, it does not hang or freeze. Just... nothing happens.

Also a little puzzling: the previous version (2017) downloaded various aircraft into a folder in my home directory. This version seems to ignore that same folder. Was the Qt launcher starting FG with a spec' to look in there? Something like "--download-dir=(path)"?

OK, I can launch from the command line, and I can install aircraft manually as I've done for years.

Just one catch: before the launcher, we had a web page where we could download aircraft models. When the launcher became operational, the download page disappeared. Instead the Download Central page proclaims "All official release aircraft can now be individually downloaded and updated with FlightGear itself."

Well, now that a problem has appeared with Qt, we can't.

So, until the launcher issue is resolved, can the old download page be made available again so we can get the models manually?

[V12]

Yes, there are many parameters passed from launcher to flightgear executable. For example this is my set of the parameters :

Code: Select all

--launcher
--download-dir=/media/rado/MULTIMEDIA/FG/fgdata
--aircraft-dir=/usr/share/games/flightgear/Aircraft/ufo
--aircraft=ufo
--fg-scenery=/media/rado/MULTIMEDIA/FG/fgdata/TEST_SCENERY
--fg-scenery=/media/rado/MULTIMEDIA/FG/fgdata/Custom_Scenery/Barbados
--fg-scenery=/media/rado/MULTIMEDIA/FG/fgdata/Custom_Scenery/EGOD_AFB
--fg-scenery=/media/rado/MULTIMEDIA/FG/fgdata/Custom_Scenery/EGOsmScenery
--fg-scenery=/media/rado/MULTIMEDIA/FG/fgdata/Custom_Scenery/EastCaribbean
--fg-scenery=/media/rado/MULTIMEDIA/FG/fgdata/Custom_Scenery/FGscenery_Chagual
--fg-scenery=/media/rado/MULTIMEDIA/FG/fgdata/Custom_Scenery/Faeroe
--fg-scenery=/media/rado/MULTIMEDIA/FG/fgdata/Custom_Scenery/LKPR
--fg-scenery=/media/rado/MULTIMEDIA/FG/fgdata/Custom_Scenery/LOWW-fg-CustomScenery-master
--fg-scenery=/media/rado/MULTIMEDIA/FG/fgdata/Custom_Scenery/OMDB
--fg-scenery=/media/rado/MULTIMEDIA/FG/fgdata/Custom_Scenery/SBGL
--fg-scenery=/media/rado/MULTIMEDIA/FG/fgdata/Custom_Scenery/SVMI
--fg-scenery=/media/rado/MULTIMEDIA/FG/fgdata/Custom_Scenery/TNCM
--fg-scenery=/media/rado/MULTIMEDIA/FG/fgdata/Custom_Scenery/TerraGitEDDF
--fg-scenery=/media/rado/MULTIMEDIA/FG/fgdata/Custom_Scenery/VQPR
--fg-scenery=/media/rado/MULTIMEDIA/FG/fgdata/Custom_Scenery/VTSP-fg-CustomScenery-master
--fg-scenery=/media/rado/MULTIMEDIA/FG/fgdata/Custom_Scenery/ZBAA-CustomScenery-master
--fg-scenery=/media/rado/MULTIMEDIA/FG/fgdata/Custom_Scenery/canary-islands
--fg-scenery=/media/rado/MULTIMEDIA/FG/fgdata/Custom_Scenery/slovakia
--fg-scenery=/media/rado/MULTIMEDIA/FG/fgdata/Custom_Scenery/TNCS-master
--fg-scenery=/media/rado/MULTIMEDIA/FG/fgdata/Custom_Scenery/Airports
--fg-aircraft=/media/rado/MULTIMEDIA/FG/fgdata/Aircraft
--airport=EDDF
--disable-auto-coordination
--enable-terrasync
--enable-fullscreen
--disable-rembrandt
--prop:/sim/rendering/shaders/skydome=true
--httpd=8080
--season=summer
--enable-real-weather-fetch
--prop:/nasal/local_weather/enabled=true


This list has been copied from launcher, menu Tool, Show command line

[flywisher]

Of course. Thank you V12!

[Thorsten]

Incidentally, when I click on File->Aircraft Center, it does not hang or freeze. Just... nothing happens.

You can enable the old canvas-based aircraft center, I believe the wiki explains what line to change. Currently the button essentially starts the Qt launcher - which you don't have...

Was the Qt launcher starting FG with a spec' to look in there? Something like "--download-dir=(path)"?

Yes. Basically with the commandline, you specify all the folders.

So, until the launcher issue is resolved, can the old download page be made available again so we can get the models manually?

It's been there since forever - not overly pretty but functional

http://mirrors.ibiblio.org/flightgear/ftp/Aircraft/

And it's even linked from the FG webpage...

[flywisher]

Oh, OK.

The webpage reads "If you would like to bulk download the entire set, ..." so I always thought it would d/l one huge file of everything. Now I understand.

Thank you Thorston!

[flywisher]

OK, using the command line with "--fg-aircraft=(my path)" with "--show-aircraft", FG does "see" and show all the models the 2017 version downloaded for me.

BUT...
when I try to start it with any of those models ("--aircraft="), it seg-faults. Every time. But these are the models FG downloaded itself, just a few weeks ago.

Anyone have an idea what's wrong here?

[MikeSierra67]

Good evening!

saiarcot895: the "/usr/share/games/flightgear/AI/tankers.xml" doesn't exist in my system. In "/usr/share/games/flightgear/AI" is only one folder, called "Aircraft", with one file: "performancedb.xml" at it.

V12: this is my QT5 modules list:

liboxideqtquick-dev/xenial-updates,xenial-security 1.21.5-0ubuntu0.16.04.1 amd64
liboxideqtquick0/xenial-updates,xenial-security 1.21.5-0ubuntu0.16.04.1 amd64
python-pyqt5.qtquick/xenial 5.5.1+dfsg-3ubuntu4 amd64
python-pyqt5.qtquick-dbg/xenial 5.5.1+dfsg-3ubuntu4 amd64
python3-pyqt5.qtquick/xenial 5.5.1+dfsg-3ubuntu4 amd64
python3-pyqt5.qtquick-dbg/xenial 5.5.1+dfsg-3ubuntu4 amd64
qml-module-qtquick-controls/xenial,now 5.5.1-1ubuntu1 amd64 [installed]
qml-module-qtquick-controls-styles-breeze/xenial,now 4:5.5.5-0ubuntu1 amd64 [installed]
qml-module-qtquick-dialogs/xenial 5.5.1-1ubuntu1 amd64
qml-module-qtquick-extras/xenial 5.5.1-1ubuntu1 amd64
qml-module-qtquick-layouts/xenial,now 5.5.1-1ubuntu1 amd64 [installed,automatic]
qml-module-qtquick-localstorage/xenial 5.5.1-2ubuntu6 amd64
qml-module-qtquick-particles2/xenial 5.5.1-2ubuntu6 amd64
qml-module-qtquick-privatewidgets/xenial 5.5.1-1ubuntu1 amd64
qml-module-qtquick-scene3d/xenial 5.5.1-4ubuntu3 amd64
qml-module-qtquick-window2/xenial,now 5.5.1-2ubuntu6 amd64 [installed]
qml-module-qtquick-xmllistmodel/xenial 5.5.1-2ubuntu6 amd64
qml-module-qtquick2/xenial,now 5.5.1-2ubuntu6 amd64 [installed,automatic]
qtdeclarative4-kqtquickcharts-1/xenial 4:15.12.3-0ubuntu1 amd64
qtdeclarative5-qtquick2-plugin/xenial,now 5.5.1-2ubuntu6 amd64 [installed]
qtquick1-5-dbg/xenial 5.5.1-2build1 amd64
qtquick1-5-dev/xenial 5.5.1-2build1 amd64
qtquick1-5-dev-tools/xenial 5.5.1-2build1 amd64
qtquick1-5-examples/xenial 5.5.1-2build1 amd64
qtquick1-qml-plugins/xenial 5.5.1-2build1 amd64
qtquick1-qmltooling-plugins/xenial 5.5.1-2build1 amd64
qtquickcontrols5-doc/xenial,xenial 5.5.1-1ubuntu1 all
qtquickcontrols5-doc-html/xenial,xenial 5.5.1-1ubuntu1 all
qtquickcontrols5-examples/xenial 5.5.1-1ubuntu1 amd64

the modules "qml-module-qtquick-controls2", "qml-module-qtquick-scene2d", "qml-module-qtquick-templates2" and "qml-module-qtquick-virtualkeyboard", are missing. And I have the modules "qtquick1-5-dbg", "qtquick1-5-dev", "qtquick1-5-dev-tools", "qtquick1-5-examples" and "qtquick1-qml-plugins" instead the "qtquickcontrols2-5-dev", "qtquickcontrols2-5-doc", "qtquickcontrols2-5-doc-html" and "qtquickcontrols2-5-examples".

I tried to install those modules, and the "qtquickcontrols2-5" via Synaptic package manager and via terminal, but it was unsuccessful.

[saiarcot895]

MikeSierra67, can you check to see if the flightgear-data-ai package is installed and that the version installed is 2018.1.1? (apt-cache policy flightgear-data-ai) If not, explicitly install that package. It should have been downloaded automatically, but the fact that the tanker.xml file isn't on your system (and the fact that directory is almost empty except for performancedb.xml which is from another package) means that something went wrong in your installation.

[flywisher]

Now this is interesting. I tried starting from console with the option "--fg-aircraft=/home/erick/.fgfs/Aircraft/org.flightgear.fgaddon/Aircraft" (the folder the 2017 launcher left my downloads in) and just specifying "--show-aircraft".

It lists all the aircraft.

So I tried starting it with the "--fg-aircraft" path (above) and specifying one of the aircraft.

It seg-faulted.

I tried various aircraft. Even the c172p. It seg-faults on every one.

Now, even with a fresh start (even re-starting the computer itself), and no reference to the old models, it seg-faults. It seg-faults every time, even with just "%fgfs" or starting from the menu.

I examined the log. Everything looks OK to me, except for this one odd entry:

Code: Select all

io:4:/build/simgear-hO7BWH/simgear-2018.1.1/simgear/scene/model/ModelRegistry.cxx:204:Image loading failed:Warning: reading "/usr/share/games/flightgear/Aircraft/c172p" not supported.

This message is from simgear, but that directory, "/usr/share/games/flightgear/Aircraft" is the same one mentioned elsewhere in the log as the default. That's where this install put the c172p and the ufo.

Now I'm really puzzled. It puts up a splash screen for about 1/2 second, then it's gone.

Any idea why it's now seg-faulting all the time?

[wkitty42]

BUT...
when I try to start it with any of those models ("--aircraft="), it seg-faults. Every time. But these are the models FG downloaded itself, just a few weeks ago.

Anyone have an idea what's wrong here?

we cannot know anything without seeing the log file... you can find it in the flightgear directory in %APPDATA% on winwhatever... it is in ~/.fgfs on *nix... not sure about mac but probably close to the same...

[saiarcot895]

Additionally, if you're willing to, running it under GDB and giving the backtrace will help us see where it's segfaulting. To do that:

1. Add the following line into /etc/apt/sources.list.d/saiarcot895-flightgear-xenial.list (substitute xenial for the distro you're running, or look for the flightgear file):
   

   Code: Select all

   deb http://ppa.launchpad.net/saiarcot895/flightgear-edge/ubuntu xenial main/debug #Flightgear Edge


2. Update your package list and install flightgear-dbgsym, libsimgearcore2018.1.1-dbgsym, and libsimgearscene2018.1.1-dbgsym.
3. From the shell, run "gdb fgfs", and when it comes to the gdb prompt, enter "run". (If you want to specify any additional arguments, add it after the "run" command.)
4. When it crashes, run "bt", and copy-paste the stacktrace.
5. Type in quit to exit GDB.

[V12]

Today I updated FG. And troubles with bad OSGTEXT color are back. What was changed ?

[AndersG]

Today I updated FG. And troubles with bad OSGTEXT color are back. What was changed ?

Maybe the OSG version?

[MikeSierra67]

Good evening to everybody.

saiarcot895: I've checked the flightgear-data-ai package installed in my system and, in effect, I had the version 2018.1.1. But I've uninstall FlightGear totally, and I've reinstalled it again. Now, it's all correct, and works perfectely.

Thanks for all your help, gentlement.

[flywisher]

saiarcot895, great idea. I will try it as soon as I can and report back. Thank you!

(Update)
OK, I added the line to the sources.list.d file, then had Synaptic refresh its package info.
When I selected the flightgear-dbgsym, Synaptic responded with the following window:

"Could not mark all packages for installation or upgrade
The following packages have unresolvable dependencies. Make sure that all required repositories are added and enabled in the preferences"

Code: Select all

flightgear-dbgsym:
  Depends: flightgear (=1:2017.4.0~13132+gitb7a2e993b-0ubuntu1~ppa1~14.04.1) but 1:2018.1.1-0ubuntu1~ppa1~14.04.1 is to be installed


Is this a show-stopper? If not, what should I do?