>Sorry, I forgot to respond to this. I was only doing the mode change with
the new mode buttons, not the mode drop down.
Hi Gary and All,
So this could be related somehow to the mode change using the new buttons as
you may have not had the same issue using the menu selection. In any case it
may
> On Sep 18, 2022, at 22:32, Reino Talarmo via wsjt-devel
> wrote:
>
> This may be irrelevant, but how you returned from FT4 to FT8 to work the
> single station?
Reino,
Sorry, I forgot to respond to this. I was only doing the mode change with the
new mode buttons, not the mode drop
> On Sep 18, 2022, at 22:32, Reino Talarmo via wsjt-devel
> wrote:
>
> This may be irrelevant, but how you returned from FT4 to FT8 to work the
> single station?
>
>> When I tried to restart WSJT-X, it failed, giving me the following error:
> Sub Process Error
> Failed to
> On Sep 18, 2022, at 21:25, Black Michael via wsjt-devel
> wrote:
>
> About how long were you running when this happened?
If by “running” you mean the program was loaded and running, it runs 24/hrs a
day. Since we are in lightning storm season, it was probably shut down and
restarted the
I’ve also had this happen on maybe four occasions when using FT8. RC4 on
Windows10 running in Parallels on MacBook. Seems to be random. Resolved by
killing the JT9 process in Task manager and restarting WSJT-X
> On Sep 19, 2022, at 9:34 AM, Bill Lederer via wsjt-devel
> wrote:
>
> I've had
I've had three segfaults on rc4.
One when I had just started up, another after I had been running for a
little while, and a third when I clicked the "menus" button. No other
correlation that I could find. I didn't find a "core" file.
On Sun, Sep 18, 2022 at 10:32 PM Black Michael via wsjt-devel
Hi Gary,
>I was on 17M FT8, made a few contacts with no problem. After the last one
>logged, I hit the FT4 button and jumped up the band as I frequently do when
>things are busy. I worked one station on FT8 and logged it. After it logged,
>the program simply closed itself - gone.
This may
About how long were you running when this happened?
I also had a segfault when WSJTX was just decoding but it was probably 20 hours
of runtime.
Mike W9MDB
On Sunday, September 18, 2022 at 08:49:23 PM CDT, Gary McDuffie via
wsjt-devel wrote:
I seldom report problems that I might
I seldom report problems that I might have because I don’t usually have enough
notes on all the details, but this one seemed serious enough that I’ll tell you
what I know about it. Can I duplicate? Of course not, yet. I’ve been using
RC4 since it came out, so it's likely a one-off event.
