During a thunderstorm, the power supply of my computer was damaged. After replacing the power supply, I was having problems with the HD my Ubuntu 22.04 Linux is on. Finally, I could only boot to an emergency command line prompt. And that didn't work. I had a screwed up alternate copy of Ubuntu 22.04 on another drive which I used for some purposed but not for CQRLOG. I moved to Windows for my digital work which is where I have contacts logged.
Advanced Forum Search
cqrlog is attempting to use the 'realtime' single QSO upload method to do bulk uploads to Clublog.
This is explicitly banned by Clublog because it causes too much traffic.
An example:
I enter a contest and make 140 QSOs. As I make each QSO it is uploaded to Clublog - this is okay.
After the contest I upload the QSOs to LotW - this causes the QSOs in cqrlog to be marked as updated.
Hello,
I was using the version 2.5.2 and finally I have moved to the VersionAlpha.
In general it seems to work with the exception of the DXCluster Web and the Callbook check.
For the DXCluster, it says, in the status line at the botton, "Downloading spots...", but any spot is shown. I have checked that the DXCluster in his web is showing spots (I think it is using the HamQTH one). Any idea? Maybe I have something missconfigured.
CQRLOG is working perfectly with LoTW, eQSL, QRZ and ClubLog. Fine work Saku and team!
I'm receiving many "QSL World" confirmation emails, and would like to know if there are plans to include an automatic or scripted upload of QSOs to this service too?
I think that "QSL World" support would be welcome, but as far as I know, confirmed contacts there do not count towards awards in the same way as LoTW. -So maybe not so important?
Please pardon this post if the topic / question has already been posted, but I really did "Search first". :(
78, John KX4QC
CQRLOG is amazing and still my favorite! Thank you Saku and friends.
Running ver 2.6.0_(119)_Gtk2 Date:2023-10-03 on Arch Linux. All very good.
CQRLOG scales without problem on all 100% display resolutions, but now display settings commonly include "User Interface Scaling" 100% (all good), but 200% and 300% corrupt text layout. Also, "fractional scaling" does not display correctly.
As these display options become more commonly the default, maybe CQRLOG should work with modern display scaling?
With the latest Alpha Branch (140) the Online Log Upload to HamQTH fails.
The Site is Online but the Upload gives a 404.
I've been using the Alpha version for a while now and I've found that if "UDP Accept" is switched on in WSJTx and "remote mode for wsjt" is switched on in CQRlog Alpha then the following things occur...
In FT4 mode RX frequency gets set to 5000 # thankfully FT4 doesn't care.
In FT8 mode RX frequency gets set to 5000 # thankfully FT8 doesn't care.
In JT4 mode RX frequency gets set to 5000 # JT4 complains that RX frequency is outside operational parameters
This is something I typed in another topic before but may have been missed. So a new topic.
Saku,
I see that Alpha 139 is out as of a couple of days ago.
I'm running an 'early' 139 from a few weeks ago that you sent me to fix the PSK adif output problem.
Is there anything that is critical in the new 139 which would make it important to upgrade?
73 Colin
Just updated from previous Version to 130 via the update script.
Now CQRLOG doesn't connect to my RIG anymore (Yaesu FT-DX10)
From the Terminal:
Cqrlog Ver:Alpha_(139)_Gtk2 Build:1 Date:2026-01-01
Cqrlog Ver:Alpha_(139)_Gtk2 Date:2026-01-01
**** DEBUG LEVEL 0 ****
**** CHANGE WITH --debug=NR PARAMETER ****
*** Parameter -h or --help for details ***
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.
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
Recent comments