On 08/02/2021 20:00, Andy Stewart wrote:
On 2/7/21 7:00 PM, Barry Jackson wrote:
On 07/02/2021 17:04, Dr. Karsten Schmidt wrote:
Hi Barry,
yes I have a similar problem. A "2" in the GUI ist stored as "1" in the
config file.
-K
73 de dg1vs
Gentlemen,
Please do not
On 07/02/2021 17:04, Dr. Karsten Schmidt wrote:
Hi Barry,
yes I have a similar problem. A "2" in the GUI ist stored as "1" in the
config file.
-K
73 de dg1vs
Am 07.02.2021 um 12:37 schrieb Barry Jackson:
On 02/02/2021 22:14, Dr. Karsten Schmidt wrote:
Hi Graeme,
I
On 07/02/2021 19:28, Andy Stewart wrote:
Hi Andy,
I hope you get this :)
No special steps to duplicate this - exactly as I described to Karsten.
If I put my correct Model ID for TS-450S in the config file as 2003
then run xlog it works OK but the GUI in the
Settings->Preferences->hamlib
On 07/02/2021 17:14, Andy Stewart wrote:
I have been trying to report issues with xlog and hamlib-4.x for a
while now, but have problems with my mails being bounced, or ignored.
I find that if the hamlib model number is correct in the config file
then it works, but the the hamlib setup
On 02/02/2021 22:14, Dr. Karsten Schmidt wrote:
Hi Graeme,
I have the same client... Quisk.
Btw. I'm using hamlib 4.0
73, Karsten dg1vs
On Wed, 2021-02-03 at 11:00 +1300, Graeme Jury wrote:
Hello Karsten,
It will be no consolation but I get the same error. I am using an
SDR
client called
On 27/11/2020 02:40, Andy Stewart wrote:
On 11/26/20 6:36 PM, Barry Jackson wrote:
On 31/10/2020 02:55, Andy Stewart wrote:
HI Barry,
--
Let me know if you continue to have issues.
Hi Andy,
OK I finally found time to have another look at this.
I started by rebuilding against
With 2003 (TS-450S correct code) in the config file all is working fine,
except for "2002" shown in the Hamlib settings dialogue and the crash on
hitting the 'Select a Radio' button.
Here is the tail of strace after hitting the Settings > Preferences >
Hamlib > Select a Radio Button.
On 27/11/2020 02:40, Andy Stewart wrote:
On 11/26/20 6:36 PM, Barry Jackson wrote:
On 31/10/2020 02:55, Andy Stewart wrote:
HI Barry,
--
Let me know if you continue to have issues.
Hi Andy,
OK I finally found time to have another look at this.
I started by rebuilding against
On 31/10/2020 02:55, Andy Stewart wrote:
HI Barry,
--
Let me know if you continue to have issues.
Hi Andy,
OK I finally found time to have another look at this.
I started by rebuilding against a recent hamlib snapshot.
I then was going to delete the .xlog, but instead looked
On 31/10/2020 02:55, Andy Stewart wrote:
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.
*
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
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.
I have narrowed this down (I think) to the fact that the new system has
hamlib-4.0.0.
I filed a bug report about this but have had no
12 matches
Mail list logo
