Hi,
After a break, I am back online with cqrlog. Unfortunately, I have to report that there are now some (significant) problems.
1. German umlauts öäüß are not saved correctly and become more corrupted each time. For example, for QTH “Königswinter,” the first time it is saved, it becomes “Königswinter,” then “Königswinter,” etc.
Advanced Forum Search
It appears that my CW keyer (K3NG on /dev/ttyACM0 on a RPi5) wasn't working.
**** DEBUG LEVEL -8 ****
OS:
Linux version 6.12.47+rpt-rpi-2712 (serge@raspberrypi.com) (aarch64-linux-gnu-gc
/usr/local/bin/mysqld
Radio1 CW settings:
CW init keyer type:3
Device:
Last error nr: 9
Last error desc:Bad file number
18
CW keyer reloaded by TRControl radio1 change
Refreshing some of my very ancient PASCAL skills I found cause, and got it to work with this change:
Hi , after installation of cqrlog when import adif file from logger 32 with nearly 150 000 qso
The install go to normal way on import i had checked
More 10 000 qso in the interface .
When i look in the log is seen many qso are not un log
All say was ok and completed a import .
Finaly i found that ~ 49000 qso missed
I returned in logger 32 export partial log to complet it
All is ok now but just surprise about nothing notified about incomplète import bug or not ?
73 Chris
hi for all .
have probleme to run cat controle !
config in panel control :
FTDX101D
/dev/ttyUSB0 or /dev/ttyUSB1
speed 38400 8 N 1
RTS ON DTR OFF hansshack OFF
I use LINUX MINT ZARA
thank you for help
73
This is more of a question of interaction with CQRlog, but I think still valid. I am moving into the ranks of remote users, so I often switch profiles in CQRlog, depending on which radio I am using. I do use both at the same time because they are separated by 800 km.
/usr/bin/tqsl -d -l "Woodbury" %f -x
/usr/bin/tqsl -d -l "Louisburg" %f -x
Typically I use these commands to upload to LOTW. What would happen if I merely used
/usr/bin/tqsl -d -l "" %f -x
In Alpha 138 (and maybe earlier versions) Data mode QSOs are exported to ADIF *incorrectly*
If a QSO is logged as PSK31 then it should be exported to ADIF as PSK31 and *NOT* as PSK which is what currently happens.
This results in LotW setting the mode of the QSO to DATA because PSK is *NOT* a valid complete mode!
When the QSL happens and is downloaded into CQRLOG then you get an Error because the QSO log entry does not match because the MODEs don't match.
There were no errors during the update process.
But when I try to start the new version I get the following error message:
colin@doombar:~$ cqrlog
cqrlog: symbol lookup error: cqrlog: undefined symbol: QGuiApplication_setFallbackSessionManagementEnabled
My System is Debian GNU/Linux 12 (bookworm) with KDE as the desktop, it is up-to-date.
73 Colin
Today I made some QSO's and after uploading to HAMQTH it normally uploads to Clublog.
For some reason I got "Acces denied" back from Clublog.
This was still the case after a couple of hours.
I solved it by changing https:// to http:// in both lines in preferences > Online log.
Not sure why this works but it may just be temporary.
Just to let you guys and girls know.
Tjalling
I am currently using CQRLog Alpha 138. I love this logger for Linux! But I have the following enhancement request, all related to the DXCC Statistics window:
1. Default behavior displays ALL DXCC entities (as opposed to just those entities worked).
2. Add checkbox to only display Not Worked entities.
3. Add checkbox to only display Not Confirmed entities.
I just installed CQRlog and I worked my first QSO today using the software. I have CAT control working correctly with my Yaesu FTdx101D and the QSO logged correctly. Is it possible for me to upload QSOs automatically directly to my QRZ log?
Also, is it possibly to keep the DX Cluster open on the screen without it minimizing when I select a station from the list of stations?
Many thanks.
73,
Bob.
M0BOB.
when i open cqrlog its nothing like the pictures in the screenshots
I'm running CQRLOG under Fedora Linux with KDE.
When I have KDE in dark mode (Using Breeze / Breeze Dark), The window and label text are dark background / light text. However, all the buttons and text entry fields have a light grey background and white text.
See here for how the main window, log window and the settings look: https://imgur.com/a/DKKMcWx
This makes it difficult to use. I've been looking thru posts on this, but haven't managed to get it fixed. Any ideas would be appreciated.
WHAT I LEARNED THE HARD WAY IS WHEN YOU CLICK THE EXPORT TO LOTW ICON, THE QUOTES IN THE TQSL COMMAND LINE ARGUMENTS:
/usr/local/bin/tqsl -d -l "STAR, TX" %f -x
MUST BE ON EACH SIDE OF YOUR LOCATION. WHEN LEFT OFF, YOU GET THIS TYPE OF ERROR MESSAGE.
Unexpected parameter
'/home/benny/.config/cqrlog/lotw/2025-11-09_09-04-45.adi'
TQSL Version 2.8.2 [pkg-v2.8.2]
THERE WAS NO PROBLEM WITH THE INDICATED ADI FILE AFTER ALL.
I HOPE THIS HELPS SOMEONE ELSE SOMEDAY.
73
BENNY K5KV
WHEN UPLOADING TO LOTW, AN "UNEXPECTED PARAMETER" IS ENCOUNTERED. THE RESULT BELOW:
My understanding from a few years ago is that CQRlog cannot be used with the same callsign on separate computers. I have two different shacks in different rooms - one for my modern gear one for my boat anchor gear. I would prefer to use CQRlog in both shacks on different computers. Is it still not possible to use CQRlog on two computers?
73, Bill NZ0T
I GOT THIS MESSAGE:
Hello all,
I have updated my working CQRLOG according to the description of Saku OH1KH to 'Alpha_138_(Gk2)' from his github.
The update process went without problems, but when starting CQRLOG I get the following error message:
Hi,
I have a very strange problem here, were CQRLOG hangs during many operations like upload/download from LotW / EQSL and also during updates of log-entries in contest mode. (this is not yet confirmed to be the same issue, though, but shows the same locking) The last working import / export I did was on 2025-07-08.
I am using / have tried the following:
Mint 22.2, Lazarus 3.0 (from official Mint distribution repositories), cqrlog 138 (compiled by me) / 138 (compiled by OH1KH) / 139 (Compiled by me)
Hi,
Some time ago I built Alpha 137 on my RPi5, and it's behaving itself relatively nicely!
Over recent weeks I started to get a pop up telling me that Alpha 138 is available for download, when starting cqrlog alpha 137.
This weekend I decided to build alpha 138 to see how it's working on my Raspberry Pi 5.
Last commit I got from git was:
commit d5706439326dbc211e30210ce3f253c4c50376da (HEAD -> main, origin/main, origin/HEAD)
Merge: ee16ac6 f6e787b
Author: OH1KH
Date: Tue Sep 30 20:34:29 2025 +0300
Version Alpha_(138)_
Hello Guys,
I haven't been on here in a while, in fact I have been off the air about a year.
My old version of Linux Mint stopped working. I never did get CQRLOG to work so I am asking again if someone could help. I am using a IC-7610 and a Lenova Desktop.
73
Bog
W7ZDX
Hi all,
I'm running a quite old version of cqrlog Qt5 version: 2.6.0
I guess it was Saku OH1KH who provided me that version, because all attempts to get cqrlog running under Linux Mint 21.3 the normal way were not successful. I even tried it today: I removed everything and made clean fresh install. No luck with original /usr/bin/cqrlog and no cqrlog folder in ~/.config/ ...
So I moved back my original ~/.config/cqrlog/ and that old Qt5 version of /usr/bin/cqrlog and it runs again (with the rest of the clean fresh install untouched).
Recently upgrade my RPi 4 -> 5.
Decided to move from cqrlog 2.5.2 to "latest": Version Alpha_(137)_
After fixing dependencies, building went smooth and as expected.
I like all new functionality, and I can appreciate all the good work that has gone into this!!!
Detail that is not working: CW interface to my K3NG keyer which is used for both configured radios (FT991/FTDX10).
Hello to all.
I'm using Open Suse Tumbleweed (fresh install)
I have installed CQRLOG from repos (last version), when i try to connect to database (i have my database in a server in my LAN...) i always obtain the same error:
Error during connection to database: TMySQL57Connection : Server connect failed.
If i try to start the program with a local database, it works fine, create the new database and starts the program normal.
I leave here some debug info:
abraham@localhost:/usr/bin> ./cqrlog --debug=1
Recent comments