Bug 238951

Summary:	games/flightgear: Crash when loading F-35B: ICE default IO error handler doing an exit()
Product:	Ports & Packages	Reporter:	Aaron Farias <timido>
Component:	Individual Port(s)	Assignee:	Ganael LAPLANCHE <martymac>
Status:	Closed Not A Bug
Severity:	Affects Some People	CC:	martymac
Priority:	---	Keywords:	crash, needs-qa
Version:	Latest	Flags:	koobs: maintainer-feedback? (martymac) koobs: merge-quarterly?
Hardware:	Any
OS:	Any

Description Aaron Farias 2019-07-03 05:16:03 UTC

This aircraft does not use the latest yasim configuration version.
YASim warning: possible convergence problem.
Terrain Map ......... Initialized
Nasal runtime error: nil used in numeric context
  at /usr/local/share/flightgear/Aircraft/F-35B/Nasal/fan-yasim.nas, line 12
  called from: /usr/local/share/flightgear/Nasal/globals.nas, line 119
Texture file not found: ''
Texture file not found: ''
Texture file not found: ''
Texture file not found: ''
Texture file not found: ''
Texture file not found: ''
Texture file not found: ''
This aircraft does not use the latest yasim configuration version.
Terrain Map ......... Initialized
ICE default IO error handler doing an exit(), pid = 46387, errno = 32
Error: caught signal 11:
  0x803fc83b0 <_pthread_sigmask+0x530> at /lib/libthr.so.3
Abort trap (core dumped)

Comment 1 Ganael LAPLANCHE freebsd_committer

2019-07-03 10:04:39 UTC

Hello Aaron,

I cannot find that aircraft in Flightgear packages.

Can you tell me where it comes from ? Can you run :

$ pkg which '/usr/local/share/flightgear/Aircraft/F-35B/Nasal/fan-yasim.nas'

?

Comment 2 Aaron Farias 2019-07-10 05:37:35 UTC

(In reply to Ganael LAPLANCHE from comment #1)
Aaron@Unix:~ $ pkg which '/usr/local/share/flightgear/Aircraft/F-35B/Nasal/fan-yasim.nas'
/usr/local/share/flightgear/Aircraft/F-35B/Nasal/fan-yasim.nas was not found in the database

Comment 3 Ganael LAPLANCHE freebsd_committer

2019-07-10 10:10:08 UTC

Hi Aaron,

Thanks. As you can see, that aircraft does not come with regular packages (either flightgear-data package or additional aicraft through flightgear-aircraft package).

For a quick fix (and if you don't mind loosing those extra files), you should try to uninstall flightgear-* packages, then cleanup (remove) the /usr/local/share/flightgear directory and finally reinstall flightgear packages. That shoud fix the situation.

If the goal is to fix Flightgear when dealing with older Aicraft data (it should not crash but maybe emit an error message instead), you might want to report that bug upstream on FG project area : https://sourceforge.net/projects/flightgear/.

Hope that helps,

Best regards,

Ganael.