Bug 1101517

Summary: [abrt] FlightGear: exit(): fgfs killed by SIGSEGV
Product: [Fedora] Fedora Reporter: z.d <z.dolezal>
Component: FlightGearAssignee: Fabrice Bellet <fabrice>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: daniel, fabrice
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/49aba0250359c659791d88f483d1dbea530f1afd
Whiteboard: abrt_hash:ead5736f281b66baa2e87d9696866fef3eda31f2
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 20:49:01 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description z.d 2014-05-27 11:45:12 UTC 
Version-Release number of selected component:
FlightGear-2.12.0-1.fc20

Additional info:
reporter:       libreport-2.2.2
backtrace_rating: 4
cmdline:        fgfs -v --aircraft=concorde --fg-scenery=/run/media/zb/ntfsdata/nfsdata/tmp/fg/scenery --fg-aircraft=/run/media/zb/ntfsdata/nfsdata/tmp/inst/fg/a --airport=LKNA
crash_function: exit
executable:     /usr/bin/fgfs
kernel:         3.14.2-200.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (2 frames)
 #23 exit at exit.c:104
 #25 _start
Comment 1 z.d 2014-05-27 11:45:16 UTC 
Created attachment 899477 [details]
File: backtrace
Comment 2 z.d 2014-05-27 11:45:18 UTC 
Created attachment 899478 [details]
File: cgroup
Comment 3 z.d 2014-05-27 11:45:19 UTC 
Created attachment 899479 [details]
File: core_backtrace
Comment 4 z.d 2014-05-27 11:45:21 UTC 
Created attachment 899480 [details]
File: dso_list
Comment 5 z.d 2014-05-27 11:45:22 UTC 
Created attachment 899481 [details]
File: environ
Comment 6 z.d 2014-05-27 11:45:23 UTC 
Created attachment 899482 [details]
File: exploitable
Comment 7 z.d 2014-05-27 11:45:25 UTC 
Created attachment 899483 [details]
File: limits
Comment 8 z.d 2014-05-27 11:45:28 UTC 
Created attachment 899484 [details]
File: maps
Comment 9 z.d 2014-05-27 11:45:29 UTC 
Created attachment 899485 [details]
File: open_fds
Comment 10 z.d 2014-05-27 11:45:30 UTC 
Created attachment 899486 [details]
File: proc_pid_status
Comment 11 z.d 2014-05-27 11:45:32 UTC 
Created attachment 899487 [details]
File: var_log_messages
Comment 12 z.d 2014-05-30 17:57:44 UTC 
Another user experienced a similar problem:

concorde has crashed into terrain (speed stall)

reporter:       libreport-2.2.2
backtrace_rating: 4
cmdline:        fgfs -v --aircraft=concorde --fg-scenery=/run/media/zb/ntfsdata/nfsdata/tmp/fg/scenery --fg-aircraft=/run/media/zb/ntfsdata/nfsdata/tmp/inst/fg/a --airport=LKNA
crash_function: exit
executable:     /usr/bin/fgfs
kernel:         3.14.2-200.fc20.x86_64
package:        FlightGear-2.12.0-1.fc20
reason:         fgfs killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 13 z.d 2014-05-30 18:28:54 UTC 
Another user experienced a similar problem:

after landing with concorde. Fuel fill to max T/O and max landing weight. AP used.

reporter:       libreport-2.2.2
backtrace_rating: 4
cmdline:        fgfs -v --aircraft=concorde --fg-scenery=/run/media/zb/ntfsdata/nfsdata/tmp/fg/scenery --fg-aircraft=/run/media/zb/ntfsdata/nfsdata/tmp/inst/fg/a --airport=LKNA
crash_function: exit
executable:     /usr/bin/fgfs
kernel:         3.14.2-200.fc20.x86_64
package:        FlightGear-2.12.0-1.fc20
reason:         fgfs killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 14 Fedora End Of Life 2015-05-29 11:57:17 UTC 
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.
Comment 15 Fedora End Of Life 2015-06-29 20:49:01 UTC 
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.