Thanks Mike!
Indeed, the wsprd I find in /usr/bin dates to January 12, 2019, so it is likely an old binary, since it was earlier this summer that I upgraded to 2.2.2.
I likely made a mistake somewhere. Now that I'm pretty sure the error is unique to my setup, I'm going to just nuke it and re-build from source and hopefully that should fix it.
--al
WB1BQE
-------- Original Message --------
Subject: Re: [wsjt-devel] Subprocess Error while trying to run WSPR with
2.2.2
From: Black Michael via wsjt-devel <[email protected]>
Date: Sat, August 22, 2020 8:00 am
To: "[email protected]"
<[email protected]>
Cc: Black Michael <[email protected]>
That error indicates that /usr/local/bin/wsprd does not exist.The error is from execvp....not from wsprd....Mike W9MDBOn Saturday, August 22, 2020, 06:52:52 AM CDT, Bill Somerville <[email protected]> wrote:On 22/08/2020 12:41, [email protected] wrote:
HI Folks,
I'll start out by admitting that software testing was never my strong suit, but wanted to share the following scenario in case it is helpful.
I have an Atomic Pi (Single board embedded - similar to a raspberry pi) running Ubuntu.
Previously, I had built and run V2.2.1 with both wspr (I think) and FT-8.
A couple of months ago, I build and installed V2.2.2 on this machine, and have been using it for FT-8 continuously with good results.
This morning, I decided to try wspr, so I switched modes.
The entire receive cycle appeared normal, then at the end, I got the following error in a Message Box:
Subprocess ErrorRunning: /usr/local/bin/wsprd -C 500 -o 4 -d -a /home/atomicpi/.local/share/WSJT-X -f 50.293000 /home/atomicpi/.local/share/WSJT-X/save/200822_1124.wavexecvp: No such file or directory
The failure was repeatable, regardless of whether I switched to wspr from FT-8, or simply started the program in wspr mode.
At the time, I had the "Save" option set to "None". Selecting"Save Decoded" and restarting the program did not resolve the issue.
Interestingly, the wave file in question does exist (at least later when I go look.)
Also interesting is that if I click on "OK" to dismiss the message box, wsjtx exits (as expected.) If I ignore it, another receive cycle starts, and a similar error is thrown for the new wav file.
My conclusion is that there is either some sort of a race condition between the creation of the .wav file and whatever goes looking for it, or the missing file is something other than what is mentioned in the error message.
This could indeed be some artifact unique to my setup here, but I'm mentioning it on the chance that it might be helpful. (I'm happy to investigate, or send a zip etc. if asked.)
--alWB1BQEHi Al,check that the directory ~/.local/share/WSJT-X/save exists, if it doesn't then try:mkdir ~/.local/share/WSJT-X/save/ 73
Bill
G4WJS.
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
