I am using Slackware64-Current. I tried to compile carlog, 2.3.0, &, even though I had all the listed dependencies, the make died very quickly. I then repackaged your binary into a Slackware package & it seemed to work fine. But when I used it in remote mode for wsjtx, & it imported a contact, a window appeared announcing that the date was not formatted correctly. When I pressed the OK button in the warning window, the contact was erased from cqrlog, without giving the opportunity to fix the date. Packaging 2.2.0 & "upgrading" 2.3.0 with it solved the problem.

HI!

Just noticed that Window/QSO list/Filter/SQL console has again double key syndrome.
Every keypress produces 2 characters to console: hheellpp!!

At least when cqrlog is run with Fedora 28/LXDE

Quickly tested some other inputs, but did not find any other place than SQL console with this bug.
This is not the first time and playing with "input mode selector" and Ibus solved this last time. Now I just have to dig out what was done at that time.

Any other distro having same issue?

Hi Petr!
I state that i use debian "buster".
With the previous version 2.2.0-1 the remote mode for wsjt worked well with CQRLog. With the new version 2.3.0-1, when I register the QSO in FT8 a pop-up of CQRLog opens with the warning of an access violation and I have two options: "CANCEL" or "SAVE". if I click on "SAVE" I run the risk of corrupting my data, if I click on "CANCEL" CQRLog disappears and only WSJT-X (1.9.1) remains active, however the contact is registered on CQRLog, as well as automatically it is uploaded on CLUB LOG and HAMQTH.

I am trying to run CQRLOG on my Raspberry Pi 3 B+. I have installed the beta version and when I run it I get a misaligned data access error.

What can I do to fix this?

Here is the debug file from the testing method:

**** DEBUG LEVEL 1 ****

Country is listed as Marion island ZS8. It should be South Africa.
Call seen on 17m FT8.