Bug#995198: wsjtx: No transmit audio

[Christoph Berg <myon@debian.org>]

Re: tony mancill
> That's a good idea.  The diffoscope results in 100MB of diff, almost all
> of it in the resulting binaries,

Uh, I guess that was to be expected... sorry for the naive suggestion.

> environments for now.  There are a number of differences, most of which
> appear to be benign.  The only significant ones are the GCC-10 -> GCC-11
> transition and hamlib 4.1 -> 4.3

wsjtx runs fine here with hamlib 4.3 when still compiled against 4.1;
I have not tested rebuilding yet.

> The fact that the "Tune" button couldn't even key my radio, despite the
> fact that I'm using CAT, makes me suspect that I might have found a issue
> with running a binary compiled against hamlib 4.1 against a system with
> 4.3 installed.  That upload was on 2021-10-12, which would explain why I
> didn't see it a week ago; I updated my system on 2021-10-16.

Iirc there is some known issue with Tune interfering with audio
generation if you use the "wrong" button to abort the tune operation;
wsjtx wouldn't generate audio in the next cycle, but recover in the
2nd next cycle. I haven't observed that here lately, but maybe I just
haven't hit the Tune button enough. (There are probably reports of
that on wsjt-devel.)

The issue discussed here seems to be something else, but possibly they
are connected.

Christoph