Hello,

I casually participate in contests, but I especially miss these two functions:

1) It should be possible to cancel the currently keyed CW message with e.g. the Esc button. The help file says that this should work anyway: "1x ESC returns cursor back to Call-field [...] It also halts CW memory output if it is just running." But the latter is not or no longer the case. I'm using CQRLOG 2.5.2 from Ubuntu 23.10 and control my rig using hamlib.

HI!
At the moment 2023-11-27 11:41 there is now new dxcc update available when starting cqrlog.
It produces ~/.config/cqrlog/ctyfiles/cqrlog-cty.tar.gz with date 2023-11-27 and Cqrlog seems to start ok also on next start after update (Alhpa 2.6.0(120) here).

If you have problems to start Cqrlog after yesterdays dxcc update read this topic https://www.cqrlog.com/comment/11598#comment-11598

Hi Saku!

So far I have had no problems with the test version of cqrlog. Today after starting cqrlog, the popup for "new qsl manager database" and "new DXCC table" update opened and I gave the ok to run it and finally I closed cqrlog. Now when I restart cqrlog it gives me the following error:

Cqrlog Ver:2.6.0_(120)_Gtk2 Date:2023-11-18
**** DEBUG LEVEL 1 ****

Hi Saku!

So far I have had no problems with the test version of cqrlog. Today after starting cqrlog, the popup for "new qsl manager database" and "new DXCC table" update opened and I gave the ok to run it and finally I closed cqrlog. Now when I restart cqrlog it gives me the following error:

Cqrlog Ver:2.6.0_(120)_Gtk2 Date:2023-11-18
**** DEBUG LEVEL 1 ****

I've been running 2.6.0_(119)Gtk2 for quite a while with no isuues until today. I have 4 rigs set up and when I changed from one to the other I had no connection so I went to TRX control to change the port. TRX control froze so I finally had to force it closed. Ever since that I am getting the access violation error. So far I have tried:

I decided it was time to update my Hamlib application to the latest version. Did a 'make uninstall' to clean out the old version and then followed Z34PEC's instructions in the Rigctl error after installing latest hamlib and wsjtx Forum post. Did the git clone https://github.com/Hamlib/Hamlib.git and then followed the installation process. Now I have $ rigctl --version
rigctl Hamlib 4.6~git 2023-11-14T16:23:14Z SHA=847836 64-bit

When I try to upload to LOTW the signed file, it stops and gives me: Uploading file... size: Error.-2
What does that indicate the problem is?
When I try to download from LOTW, it says NOT logged Errorl-2 Error. Error. ssl_openssl

What's wrong? Thanks!

Log wont import, I have 25k qso's, it stops at about 4k says complete, but not even the 4k qso's import, no problem importing into many different loggers. I have copied the Debug file first, then the error file

DEBUG:

Cqrlog Ver:2.6.0_(119)_Gtk2 Date:2023-10-03
**** DEBUG LEVEL 1 ****

Have problem to import downloaded .adif from eQSL. The file is downloaded, but CQRLOG crashed during import.

I FOUND A LOTW CONFIRMATION FROM ARRL FOR JD1YAB WITH PROPER CREDIT FOR OGASAWARA. I COULD NOT FIND THE CALL JD1YAB UNDER THE OGASAWARA PREFIX JD(O) BUT INSTEAD CQRLOG STORES THE CALL AS JA-JAPAN. IT WAS CONFUSING HOW I COULD HAVE A LOTW CONFIRMATION FOR A STATION THAT SEEMED TO NOT BE IN MY LOG. OF COURSE I TRIED AND TRIED TO EDIT THE LOG QSO AND CORRECT PREFIX BUT CQRLOG HAS THE VERY ANNOYING HABIT OF INGNORING USER INPUT AND DOING WHATEVER IT LIKES. THIS IS MY THIRD ENCOUNTER WITH THIS FORCED ERROR ON DXCC PREFIX. PLEASE ALLOW USERS TO CORRECT DXCC PREFIXES THAT ARE IN ERROR.

Hello:

I was trying to fetch loc_testing and recompile since I couldn't upload to Clublog.

Unfortunately, when I tried to compile, I got two errors about crtbegin.o and crtend.o missing and that linking would probably fail. Evidently it did. I found a post where an individual had encountered a similar problem, but never solved it. https://www.cqrlog.com/comment/8302#comment-8302. I've never used Lazarus-GUI and couldn't figure out how to make that work.

I tried the following:

Hello,

I have used CQRLOG for several years and am a great fan. Recently eqsl made a change to their download ADIF file that caused CQRLOG to freeze when trying to parse it. Saku quickly had a fix (rev 119) and was great at helping me to get a working build (albeit 32-bit) on a Raspberry Pi. Saku is a real asset to the CQRLOG community.