Hello all,
I have upgraded from Ubuntu 22.04 to Ubuntu 24.04. The upgrade process uninstalls CQRLOG so I have to install it again.
The CQRLOG program can be installed, but when I try to install MariaDB I get always errors related with the package "mysql-server-8.0".
It says that MySQL is frozen and I cannot do any operation. I've tried to uninstall the complete MySQL and I cannot do it.
When remote wsjtx/jtdx is on I am not happy when it is closed because wsjtx/jtdx is closed. It should be my decision when switch off.
Best regards, Mirek so5wd
Hi
I install cqrlog on Fedora 43 recently and it can't access the mariadb to load or use the log on the machine and not online somewhere else.
Here is the recent log.
I started it up and the error showed up. I uninstalled through software app and updated the machine. I then installed cqrlog and still had a failure. I uninstalled this time using dnf remove and reinstalled using dnf install.
Same error.
First: I have been having problems uploading log's to LoTW with TQSL. I noticed that there were two entries in the program listing. Thinking that that may be the problem, I removed one. That removed both from the listing. I used program manager to reinstall tqsl, and both listing were returned. What is the purpose of having two TQSL options?
Second: The problem trying to upload to LoTW occurs with the failure report:
TQSL Version 2.7.2 [unknown]
Signing using Callsign KE5WCT, DXCC Entity UNITED STATES OF AMERICA
Linux Mint 22.1 uses Ubuntu 24.04 packages. The CQRLOG PPA does not support Ubuntu 22.04/Noble. I am using MariaDB for local web site development with Wordpress and for phpmyadmin. Who knows what else I might use it for. If I try to install or need to reinstall CQRLOG, I cannot without my MariaDB being uninstalled.
How can I install CQRLOG to avoid this problem?
And I wish the Ubuntu package would check for a valid DB, either MariaDB or Mysql, before installing one or the other.
Bill Beal W5OXL ex WD5HHH
I still can't start FLDigi remote from latest cqrlog.
If I try, I got a Error Box from cqrlog with "No timers available" and Abort and Okay Buttons.
Abort kills cqrlog, and OK does nothing.
I can start FLDigi and the TRX Connection is working, changing Freq in FLDigi changes Freq in cqrlog, both ways are working.
No Mode change in cqrlog in New QSO Window. Stays at SSB.
But there is no logging from FLDigi to cqrlog.
Hi all,
in the frequency tables there is an option to add RX and TX offset. Is there anyone using this possibility?
My idea is to use it for Transverters. I thought it was going to work like this, that in the NewQSO window if yo enter a (uW)band like 5.7GHz the that is would will be saved in the log and shown in the QSO window. But the frequency sent to the rig would be the IF frequency based on the TX / RX offset for that band.
Is there anyone using it? Does someone have some clues how to set it up???
Many Thanks in Advance!
/Thomas, SM0KBD
Playing with a Linux for for a few things. Went to install CQRLog again.
here is what I got:
The following packages have unmet dependencies:
cqrlog: Depends: libgdk-pixbuf2.0-0 (>= 2.22.0) but it is not installable
Depends: libhamlib2 (>= 1.2.10) but it is not installable
Depends: libmariadbclient-dev but it is not installable
libgdk-pixbuf-2.0-0 is already the newest version (2.42.12+dfsg-4)
libhamlib-utils is already the newest version (4.6.2-1+b1).
I recently changed MySQL servers and exported (mysqldump) cqrlog_common and cqrlog001 databases. All the data came over fine. I can query the cqrlog_main table and everything is in there. Even custom views I created were imported successfully on the new server.
The issue is when I connect the cqrlog application to it, the QSO List window is blank. The data are not missing. The QSO List window shows "QSO in log" and "DXCC CFM" correctly, and all the contacts are in the Statistics window. Just no rows in the main window.
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.
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.
Recent comments