Hi Bill,
Will do and thanks for quick reply.
Best Regards
Viv
On Friday 29/05/2020 at 13:51:40, Bill Somerville wrote:
On 29/05/2020 13:41, v...@vpwilliams.com wrote:
Hi All,
For your information I have experienced another example of
wsjt-x stopping decoding of incoming
Hi John,
the documentation is correct. For v2.2.0 RC1 & RC2 we use Qt v5.14, but
proved to be premature and a couple of issues forced us to revert to
using Qt v5.12. That has allowed macOS 10.12 back in as a supported
platform, for now.
73
Bill
G4WJS.
On 29/05/2020 14:33, Joe Taylor wrote:
On 29/05/2020 15:07, Stephen VK3SIR wrote:
Joe, Bill and Steve,
A great job with rc3 ! It compiles almost without message under the Windows 3.1
x64 JTSDK. I have yet to test it with the Ubuntu 20.04 LTE release yet.
Also I note the comments regarding releasing code under Qt 5.12.8 - required
Thanks to all who have provided reports on their testing of WSJT-X
2.2.0-rc1 and -rc2. Special thanks to Mike, W9MDB, for his dedicated
work on several Hamlib problems.
A third candidate release for WSJT-X 2.2.0, WSJT-X 2.2.0-rc3, is now
available for download and beta testing. Most users
David,
It’s a good reminder for us all... New software versions (and especially
JT-software) should start with a fresh, clean wsjtx.ini file. Yes we get used
to our screen settings etc... but once the new "default" wsjtx.ini file is in
place we can cut and paste across identical settings as
On 29/05/2020 13:41, v...@vpwilliams.com wrote:
Hi All,
For your information I have experienced another example of
wsjt-x stopping decoding of incoming signals. Wsjt-x was running for
around 3 hours. It was being used only to monitor with no TX
activity. Suddenly no decodes appeared
Hi John,
Please check with Bill. He believes RC3 should be OK on macOS 10.12.
-- Joe
On 5/29/2020 9:30 AM, John Nelson via wsjt-devel wrote:
Hi Joe,
Thanks for rc3. The web-site reports:
*Version 2.2.0-rc3 for macOS 10.12 and newer: wsjtx-2.2.0-rc3-Darwin.dmg*
*
*
Should this
Hi All,
For your information I have experienced another example of
wsjt-x stopping decoding of incoming signals. Wsjt-x was running for
around 3 hours. It was being used only to monitor with no TX
activity. Suddenly no decodes appeared in the window. The Decode
button was
(2.2.0-rc2 )
With RC2 I have been having random(?) cases where the Decode button
hangs up highlighted in blue.
The wide graph is still active but there are no further decodes and GUI
inputs are unresponsive.
Requires closing and restarting WSJT-X to recover.
Most of there freezes have
Hi Joe,
Thanks for rc3. The web-site reports:
Version 2.2.0-rc3 for macOS 10.12 and newer: wsjtx-2.2.0-rc3-Darwin.dmg
Should this refer to 10.13 and newer to avoid confusion.wsjtx-2.2.0-rc3
does not load on 10.12
— John G4KLA
smime.p7s
Description: S/MIME cryptographic signature
Joe, Bill and Steve,
A great job with rc3 ! It compiles almost without message under the Windows 3.1
x64 JTSDK. I have yet to test it with the Ubuntu 20.04 LTE release yet.
Also I note the comments regarding releasing code under Qt 5.12.8 - required
due to Mac-deployment issues. Qt 5.12.8 is
Hello,
I tried to put in a bug report earlier about a problem I and a lot of
others are having with the software just stopping to decode with no
apparent reason. Good thing it was rejected because the membership list
hadn't caught up, because I found out what's going on.
One of the things I
Bill,
Thanks for the comments ... still working here on a Ubuntu 20.04 release
> Note that the LTS releases of Qt have little bearing on Qt open source users
> since for them support always ends at the date of the next release.
All Noted and :-)
BUT we are aware of some grief across
On 29/05/2020 15:20, David Reinhart wrote:
Hello,
I tried to put in a bug report earlier about a problem I and a lot of
others are having with the software just stopping to decode with no
apparent reason. Good thing it was rejected because the membership
list hadn't caught up, because I
I changed from 2.2.1 Win 64 bit to 2.2.0-rc3 Win 64 bit. RC3 would not
connect to OmniRig using the TS-590 file I had been using with ver 2.2.1. It
also would not connect with the default OmniRig TS-590 file.
However, when I closed RC3 and re-started with the default OmniRig TS-590 file,
it
On 29/05/2020 16:37, Kari wrote:
Hello,
I'm still getting "Feature not available while getting current VFO" error
on my Ubuntu 18.04.4 LTS systmem(s) when trying to use "rigctld-wsjtx"
with either IC7300 or IC-703 rigs.
73's de Kari, oh2gqc
Hi Kari,
you report and others seem to conform
Hi Mike,
On 29.5.2020 19.11, Black Michael via wsjt-devel wrote:
What do you get from these commands?
ldd rigctld-wsjtx | grep hamlib
ldd wsjtx | grep hamlib
I get no output.
FYI, I compiled rc3 from sources ( if that makes any difference ... )
'Kari
Hi Bill and team,
I note that the release notes for rc3 includes "Load language translations only
when matching primary language", so I wanted to let you know that I'm
continuing to observe this behavior in rc3. If you meant that it will be fixed
in the non-rc version, then my apologies for
Hello,
I'm still getting "Feature not available while getting current VFO" error
on my Ubuntu 18.04.4 LTS systmem(s) when trying to use "rigctld-wsjtx"
with either IC7300 or IC-703 rigs.
73's de Kari, oh2gqc
IC7300 trace below:
karza@carole:~/ham/wsjtx/wsjtx220-rc3/bin$ ./rigctld-wsjtx -m
Joe,
The advice that you have issued is against what any academic or trade educator
would EVER recommend as sound practise to our trainees / clients / researchers
etc.
One always starts with a clean slate and then introduces changes - especially
when testing and evaluating. That is
On 5/29/2020 11:00 AM, Stephen VK3SIR wrote:
It’s a good reminder for us all... New software versions (and especially JT-software)
should start with a fresh, clean wsjtx.ini file. Yes we get used to our screen settings
etc... but once the new "default" wsjtx.ini file is in place we can cut and
Hi Joe,
Just downloaded RC3. Restoring minimized windows works. Thanks.Minor bug,
Started WSJTX rc3. Radio (power) was not on. Canceled WSJTX.Turned on the
radio. Started WSJTX rc3, brought up settings screen, changed input, output
from default to USB, clicked Ok. Input was working properly,
On 29/05/2020 16:07, Sam W2JDB via wsjt-devel wrote:
Hi Joe,
Just downloaded RC3. Restoring minimized windows works. Thanks.
Minor bug, Started WSJTX rc3. Radio (power) was not on. Canceled WSJTX.
Turned on the radio. Started WSJTX rc3, brought up settings screen,
changed input, output from
What do you get from these commands?
ldd rigctld-wsjtx | grep hamlibldd wsjtx | grep hamlib
Mike W9MDB
On Friday, May 29, 2020, 10:43:10 AM CDT, Kari wrote:
Hello,
I'm still getting "Feature not available while getting current VFO" error
on my Ubuntu 18.04.4 LTS systmem(s) when
On 29/05/2020 16:54, Andy Durbin wrote:
I changed from 2.2.1 Win 64 bit to 2.2.0-rc3 Win 64 bit. RC3 would
not connect to OmniRig using the TS-590 file I had been using with ver
2.2.1. It also would not connect with the default OmniRig TS-590 file.
However, when I closed RC3 and re-started
On 29/05/2020 17:11, Black Michael via wsjt-devel wrote:
What do you get from these commands?
ldd rigctld-wsjtx | grep hamlib
ldd wsjtx | grep hamlib
Mike W9MDB
Mike,
that won't tell you anything as in both cases Hamlib is statically linked.
73
Bill
G4WJS.
Hi Bill and Christoph,
Thanks for the help.
Removing all the wsjtx packages improved the situation. dpkg now installs
wsjtx incompletely and leaves a broken package. Ubuntu 20.04 has
libgfortran5 by default, 4 is available and 3 is not. For libreadline, 8
is the default and 5 is available.
Re: jeff millar
> Removing all the wsjtx packages improved the situation. dpkg now installs
> wsjtx incompletely and leaves a broken package. Ubuntu 20.04 has
> libgfortran5 by default, 4 is available and 3 is not. For libreadline, 8
> is the default and 5 is available.
>
> Is there a way to
Hi Ryan,
thanks for the issue report. I have tracked down the problem which only
happens when the primary UI language is 'en-US', there are no other 'en'
languages installed, and another language is installed. I had missed it
because I always had 'en-GB' installed. It is fixed for the next
Hi!
Just jumped from rc1(snap) to rc3. (self compiled source from K1JT homepage)
Sad to see that the same hamlib error still exist there in rc3 too!!
"Hamlib error: Feature not available while getting current VFO"
Fedora 31, icom 7300, rigctld started by crontab script at PC startup,
wsjtx
On 5/29/2020 3:53 PM, Rich Zwirko - K1HTV wrote:
I just downloaded and installed RC3. With the RxFrequency column in
focus, the Erase button works, but with the Band Activity side in focus
the Erase button has no effect. However, using a right click and then
selecting 'Erase' does work OK on
Hi BIll and Christoph...
This is the pleasures of the bleeding edge...when will I ever learn?
jeff
On Fri, May 29, 2020 at 3:57 PM Bill Somerville
wrote:
> Hi Jeff,
>
> you have two viable options, build from sources, or wait for the package
> maintainers to make WSJT-X 2.2.0 available for
Subscribe
-Brett
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Hi Jeff,
you have two viable options, build from sources, or wait for the package
maintainers to make WSJT-X 2.2.0 available for your distribution
version. We, the WSJT-X development team, only build a single package
targeted at one commonly used distribution version. Currently Ubuntu
20.4.0
On 29/05/2020 20:53, Rich Zwirko - K1HTV wrote:
I just downloaded and installed RC3. With the RxFrequency column in
focus, the Erase button works, but with the Band Activity side in
focus the Erase button has no effect. However, using a right click and
then selecting 'Erase' does work OK on
Re: Rich Zwirko - K1HTV
> I just downloaded and installed RC3. With the RxFrequency column in focus,
> the Erase button works, but with the Band Activity side in focus the Erase
> button has no effect. However, using a right click and then selecting
> 'Erase' does work OK on both sides.
I just downloaded and installed RC3. With the RxFrequency column in focus,
the Erase button works, but with the Band Activity side in focus the Erase
button has no effect. However, using a right click and then selecting
'Erase' does work OK on both sides.
I reloaded RC2 and found that it has the
We know...working on it.
Mike W9MDB
On Friday, May 29, 2020, 11:17:43 PM CDT, Saku wrote:
Saku kirjoitti 30.5.2020 klo 6.06:
Hi!
Just jumped from rc1(snap) to rc3. (self compiled source from K1JT homepage)
Sad to see that the same hamlib error still exist there in rc3
Saku kirjoitti 30.5.2020 klo 6.06:
Hi!
Just jumped from rc1(snap) to rc3. (self compiled source from K1JT
homepage)
Sad to see that the same hamlib error still exist there in rc3 too!!
"Hamlib error: Feature not available while getting current VFO"
Fedora 31, icom 7300, rigctld started by
39 matches
Mail list logo
