On 30/10/2020 13:41, Andy Stewart wrote:
I recommend moving your config file to a safe place and restarting xlog
with no config file, as an experiment.
Yes I did this effectively by using a new user and later by just
re-naming the ~/.xlog dir.
That allows the program to start without crashing, but would lock up
when trying to enter settings in hamlib config dialog when using hamlib-4.0
I have not tested xlog with hamlib-4.0.
I just built hamlib-4.1 and xlog against it and I can now edit the
hamlib settings without a hang or crash, however rig control fails to
work at all, even using a manual config string for the port. It just
fails to communicate, looking at the hamlib tracker in xlog.
wsjtx-2.3.0-rc1 and klog-1.4rc5 are working fine built with hamlib-4.1
so it does look like an xlog issue.
I'm not familiar with Mageia. It is an Ubuntu derivative, and if so,
from which version of Ubuntu are you seeing an issue? I've not tested
anything past 18.04.
No, Mageia has no connection to *buntus whatsoever. It was forked from
Mandrake/Mandriva in 2010 but is community driven with no commercial
ties :) RPM based like Fedora, SuSe etc.
I maintain most of our radio related packages and am currently tying up
loose ends for the next Mageia release (Mageia 8).
I can only test Hamlib with my Kenwood TS450S, but please let me know
how/if I can help to resolve this.
73,
Barry
G4MKT
Thanks for the report, and 73,
Andy
Xlog maintainer
