Hi Jakob,
thanks for testing that.
73
Bill
G4WJS.
On 25/01/2021 17:02, Jakob Ketterl DD5JFK wrote:
Hello Bill,
just a quick update on this, I'm happy to confirm that this has been
fixed in RC4.
Thank you and keep up the good work!
73s
Jakob DD5JFK
On Tue, Jan 12, 2021 at 2:13 AM Bill Somerville <[email protected]
<mailto:[email protected]>> wrote:
On 11/01/2021 20:43, Jakob Ketterl DD5JFK wrote:
> Hello List,
>
> I have been updating some machines to WSJT-X 2.3.0 for testing and
> implementing the new FST4 and FST4W modes in OpenWebRX.
>
> While doing so, I noticed that the WSPR decoding stopped working on
> these hosts. For reference: The decoding process for all WSJT-X
modes
> in OpenWebRX uses the command-line binaries (jt9 and wsprd) and
feeds
> them with already "chopped" audio files.
>
> While analyzing, I found that wsprd command-line utility seems
to fail
> whenever the "-a" option is not specified. The usage message states
> that the option should have a fallback, but it seems like that
part is
> failing for some reason:
>
> -a <path> path to writeable data files, default="."
>
> The corresponding error message:
>
> Error: inaccessible data directory: '(null)'
>
> I was able to fix this for now by passing "-a ." to the process,
but
> given the usage message I'd consider this a bug (albeit a minor
one).
> I have not looked at the code at this point, but I can do so if
necessary.
>
> Also: I don't remember this kind of error in RC2, although I would
> need to downgrade one of my machines to be able to make a final
> statement on this.
>
> Thank you and 73s
> Jakob DD5JFK
Hi Jakob,
thanks for the issue report, I can conform this was a regression in
v2.3.0 RC3 introduced when a check for an inaccessible data directory
was implemented. It is fixed for the next release.
73
Bill
G4WJS.
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
