Hi Mike and Richard,
that message was added in Hamlib commit 6fbe4a5f which means it was used
from WSJT-X v1.7.0. It was removed in commit 7062b67 which means it was
no longer in WSJT-X from v2.0.1 onwards.
Unless this is in a pre-v2.0.1 WSJT-X version it must be a custom build
of WSJT-X not using the recommended Hamlib version, probably some
distribution's default Hamlib build which may be ancient.
The message is benign but we do not support WSJT-X built with arbitrary
versions of Hamlib, this will be particularly true for the next release
given that there have been a lot of changes in Hamlib recently.
73
Bill
G4WJS.
On 26/03/2020 04:39, Black Michael via wsjt-devel wrote:
What version of WSJT-X are you running?
I don't see that message in V2.1.2 or in the hamlib code for v2.1.2
de Mike W9MDB
On Wednesday, March 25, 2020, 07:33:01 PM CDT, Richard Shaw
<[email protected]> wrote:
I switched from hamlib to flrig some time ago and just happened to
check my journal on my Fedora 31 box and I'm getting one of these
about every second...
journalctl -f
-- Logs begin at Tue 2020-03-24 17:13:20 CDT. --
Mar 25 19:25:50 hobbes.localdomain wsjtx[25855]: Hamlib:
flrig_get_mode has_get_modeA=1
Mar 25 19:25:51 hobbes.localdomain wsjtx[25855]: Hamlib:
flrig_get_mode has_get_modeA=1
Mar 25 19:25:52 hobbes.localdomain wsjtx[25855]: Hamlib:
flrig_get_mode has_get_modeA=1
Mar 25 19:25:53 hobbes.localdomain wsjtx[25855]: Hamlib:
flrig_get_mode has_get_modeA=1
Mar 25 19:25:54 hobbes.localdomain wsjtx[25855]: Hamlib:
flrig_get_mode has_get_modeA=1
Mar 25 19:25:55 hobbes.localdomain wsjtx[25855]: Hamlib:
flrig_get_mode has_get_modeA=1
Mar 25 19:25:56 hobbes.localdomain wsjtx[25855]: Hamlib:
flrig_get_mode has_get_modeA=1
How to I stop this?
Thanks,
Richard
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
