Re: Xlog and Hamlib-4
On 10/29/20 7:06 PM, Barry Jackson wrote: Hello - first visit here! I am having issues with xlog segfaulting when launched on a system that has a config file that was created in an earlier version. Hi Barry, I recommend moving your config file to a safe place and restarting xlog with no config file, as an experiment. I have narrowed this down (I think) to the fact that the new system has hamlib-4.0.0. I have not tested xlog with hamlib-4.0. I filed a bug report about this but have had no response as yet. https://savannah.nongnu.org/bugs/?59362 I'll take a look. By chance I was just looking at this list recent archive and saw some discussion about hamlib and xlog, so here I am. I maintain (or try to) xlog in Mageia. Barry 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. Thanks for the report, and 73, Andy Xlog maintainer -- Andy Stewart (KB1OIQ) Vice President: PART of Westford, MA (WB1GOF)
Re: Xlog and Hamlib-4
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
Re: Xlog and Hamlib-4
On 10/30/20 10:56 AM, Barry Jackson wrote: 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 HI Barry, Did you notice in the release notes for hamlib-4.0-rc2 that the model numbers for all of the rigs have changed? https://sourceforge.net/projects/hamlib/files/hamlib/4.0%7Erc2/ My question: are you using the correct value for the model of rig that you are using? Did you try using the rigctl program to isolate potential hamlib issues from potential xlog issues? I have not tested xlog with hamlib-4.0. On Ubuntu 18.04, I just compiled xlog with hamlib-4.0 and saw no issues. Note: I have not tested it with my rig (yet). That's next. 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. Where are you finding hamlib-4.1? On Sourceforge, I'm finding hamlib-4.0-rc2, which is what I'm currently using for testing the latest version of xlog. Thanks, and 73, Andy -- Andy Stewart (KB1OIQ) Vice President: PART of Westford, MA (WB1GOF)
Re: Xlog and Hamlib-4
HI Barry, The following stack worked for me: * Andy's Ham Radio Linux, version 24c+ (my next dev release), which is based on Ubuntu 18.04.* * Xlog 2.0.19 * hamlib-4.0-rc2 * ICOM 7300 on /dev/ttyUSB0 * I started with a blank ~/.xlog directory. * I started Xlog and reconfigured hamlib, taking care to choose the updated rig number. * When the POWER entry is listed in the QSO entry window, it will say UNKNOWN if the rig power is set to 0, but otherwise, it reflected the rig power setting. Try ctrl-Y ctrl-K for a quick erase/update of the QSO entry window. I was able to duplicate the condition of hamlib hanging xlog, but that always happens when you turn off the rig with hamlib enabled and Xlog is still running. Xlog eventually comes out of it. This isn't ideal, but it is nothing new for Xlog, either. Turning the rig on again causes the software to be happy again. Let me know if you continue to have issues. 73, Andy -- Andy Stewart (KB1OIQ) Vice President: PART of Westford, MA (WB1GOF)
