[Bug 213650] devel/simgear version 2016.3.1 can cause flightgear to crash with assertion failure when changing radio frequencies

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213650

            Bug ID: 213650
           Summary: devel/simgear version 2016.3.1 can cause flightgear to
                    crash with assertion failure when changing radio
                    frequencies
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: martymac at FreeBSD.org
          Reporter: russo at bogodyn.org
             Flags: maintainer-feedback?(martymac at FreeBSD.org)
          Assignee: martymac at FreeBSD.org

Created attachment 175987
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=175987&action=edit
Patch combining simgear git commits b9deeb and a97c14

A known bug in the release version of the simgear 2016.3.1 can lead to
flightgear crashing with an assertion failure when the pilot changes a comm
radio frequency or silences the radio.

A forum thread describing the issue is at 
https://sourceforge.net/p/flightgear/mailman/message/35388214/

The bug has been fixed in the simgear project's git repo, but until the next
release that leaves FreeBSD's port somewhat broken.

To reproduce, one has to have flightgear set up so that it starts up with the
radios turned on and receiving ATIS information.  If you then turn the volume
knob to zero or click the "swap frequency" button on the com1 radio, the code
exits with the assertion failure.

I have applied the changes made in simgear's git commits b9deeb and a97c14, and
found that it fixes the problem with flightgear.  These commits may be found at 
https://sourceforge.net/p/flightgear/simgear/ci/b9deebb59d872169eb164101b83b6ba957583ee2/
and
https://sourceforge.net/p/flightgear/simgear/ci/a97c145f56233f2b4df633c13e5767d3a1b8617b/.

The attached patch, if dropped into devel/simgear/files will fix the problem
until the next release of simgear and flightgear, which won't have the bug.

-- 
You are receiving this mail because:
You are the assignee for the bug.