Il 03/06/2019 00:10, Bill Somerville ha scritto:
Hi Mike,
it will help but it is not a viable workaround.
If you can reproduce the issue and have a build area, can you try the
patch I just asked Christoph to test please? The wsjtx-2.1.0-rc6 tag is
in the SF repo.
73
Bill
G4WJS.
On 02/06/2019 23:06, Black Michael via wsjt-devel wrote:
Can you see if renaming the wsjtx_log.adi file in the original config
solves problem?
Mike
On Sunday, June 2, 2019, 4:05:55 PM CDT, Christoph Berg <c...@df7cb.de>
wrote:
Re: To WSJT software development 2019-06-02
<20190602205424.ga3...@msg.df7cb.de
<mailto:20190602205424.ga3...@msg.df7cb.de>>
> Re: Joe Taylor 2019-06-02
<93dbfb69-b762-58fa-5e4e-0094419b1...@princeton.edu
<mailto:93dbfb69-b762-58fa-5e4e-0094419b1...@princeton.edu>>
> > - OK/Cancel buttons on Log QSO window maintain fixed positions
>
> Thanks :)
>
> > Release candidate WSJT-X 2.1.0-rc6 will be available for beta-testing
>
> It's segfaulting for me (amd64 Debian buster, Debian packaging):
It's not segfaulting immediately on startup with "-r test" (haven't
done any further testing yet). Config that causes the immediate
segfault attached.
Christoph
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Thanks Bill,
now rc6 read my rc5 configuration file.
windows 10
qt 5.12.3 64 bits
--
73
Sandro
IW3RAB
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
