Thanks for clarifying that, I would suggest that this is filed as a proper bug/issue at the tracker, so that this can be revisited - because it's going against everything that's been previously said about Qt5 remaining 100% optional, and it's in line with numerous concerns voiced by various contributors about the Qt5 related developments possibly affecting other, unrelated, but desirable functionality (such as the Aircraft Center):
Subject: Aircraft CenterHooray wrote:Otherwise, it's almost certainly related to the package manager not being able to download the data it needs - which may be as simple as a version confllict, i.e. it getting outdated data.
It is for a reason that I suggested to file a bug report and provide additional data - and the background info I provided was also for a reason
Subject: New Canvas GUIHooray wrote:Qt5 is not intended to be required for building FG, even though useful functionality is going to be increasingly tied to it (think launcher, in-sim UI, package manager, AircraftCenter UI).
Subject: OSGearth as default scenery?Hooray wrote:the new Qt5 functionality is seeing improvements in areas for which there is no mapping outside Qt5, namely no PUI/Canvas or Phi bindings to bring features like the package manager up to par with the Qt5 code.
Subject: FG 2016,1.1Hooray wrote:if there are any actual bugs related to the Qt5 launcher, please report them - otherwise, Zakalawe keeps encouraging feature requests for the Qt5 launcher - so if you think anything is missing/broken etc, please also get in touch via the devel list, and/or, the issue tracker - some recently posted feedback was very much appreciated IIRC, and got implemented within a few days.
It seems increasingly likely that the Qt5 launcher will continue to developed, and it may even make built-in features obsolete, so it is a good idea to be proactive whenever you notice anything missing/broken or incomplete, because all the ongoing Qt5 work is likely to be the foundation for what FG is going to look like a few years from now - to see that that's the case, you only need to look at new developments that are solely integrated with the Qt5 front-end - thus, sooner or later, certain desirable functionality will be tied to Qt5, and you should not expect fgrun to support all features that the Qt5 launcher does/will support.