[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#995198: wsjtx: No transmit audio



On Mon, Oct 04, 2021 at 07:32:28AM -0700, tony mancill wrote:
> On Mon, Sep 27, 2021 at 09:07:49PM +0100, Hilary Snaden wrote:
> > Package: wsjtx
> > Version: 2.5.0~rc6+repack-1
> > Severity: important
> > 
> > Dear Maintainer,
> > 
> > The program generates no audio output on transmit, in any mode. This is identical to a bug which I reported on the previous version of wsjtx, under Debian bullseye/sid (though on different hardware).
> > 
> > The program works satisfactorily on receive.
> > 
> > The similar (in function) program fldigi generates good, clean audio on transmit on the same machine.
> 
> I am not experiencing any problems with transmit with this version of
> wsjtx.  Can you provide more details about your configuration and/or
> hardware?

I believe I encountered the same behavior you are reporting with wsjtx
2.5.0+repack-1.  wsjtx receives audio as expected, but nothing is
generated during transmit or tune, and PTT (via CAT for my rig) doesn't
even switch my radio into TX.

This same version and configuration of wsjtx worked correctly a week
ago.  I run testing/unstable and update every few days, so my initial
thought was that the change in behavior was due to an apt update of the
system.

I tried reconfiguring and reinstalling wsjtx, and then uninstalling
pulseaudio, to no effect.  However, rebuilding wsjtx against unstable in
a clean chroot and installing the resulting deb results in a fully
functioning wsjtx again.

At this point, I couldn't tell you whether it is library dependency of
wsjtx or something in the build environment that has changed and is
addressed by the rebuild.  However, it is reproducible - meaning my
locally build .deb works consistently, and reinstalling the .deb from
the archive (I believe generated by this build [1]) fails to generate TX
audio.

I am tempted to upload a new source package to trigger a rebuild to see
if that solves the problem with the deb in the archive.  Perhaps wsjtx
got caught up in a transition causing this subtle failure?

Christoph or Dave, do you have any suggestions on how to track down the
root cause?

Thank you,
tony

[1] https://buildd.debian.org/status/fetch.php?pkg=wsjtx&arch=armhf&ver=2.5.0%2Brepack-1&stamp=1632820833&raw=0

Attachment: signature.asc
Description: PGP signature


Reply to: