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

I had Cqrlog working on mint 18.2 then switched to Ubuntu 18.04 bionic beaver to see if I could correct another problem and reloaded Cqrlog and my data just fine. I could not get digital working with fldigi for some reason so went to go back to mint and seemed ok but it won't let me open Cqrlog and the pop up says it can't connect to DB and to put last 20 lines of the err file here. Any ideas what I am missing ? thanks for any help, and feel free to email me direct too. Tom WD0BFO@WD0BFO.COM

I somehow ended up in a situation where upload stopped working and cqrlog complains

Clublog: All QSO already uploaded

I tried the old trick uploading an adif; but when I try to mark All qso's uploaded, I got another complaint. See attachment.

I have seen several reports here of instability, mainly with Yaesu rigs. My problem is with Kenwood but the symptoms are nearly identical. Let me also state right here that FLDIGI operates flawlessly with my rigs. I have

* TS-140S with IF-10C and IF-232C
* TS-440SAT with IC-10 and IF-232C
* Computer is i5 with 8GB RAM
* OS is Xubuntu 16.04.03LTS
* CQRLOG version 2.2.0 (001)
* Hamlib v3.1

As a very elderly absolute newby to Linux, I would appreciate some help.
I am running Linux Mint 17.3 - 64bit version.with all updates installed. I have installed the latest version of Cqrlog and am trying to configure my Icom 746 com ports. I have tried all the sugestions made in the help files without success. Could someone please advise me how to setup the above. Any assistance would be appreciated.
Thanks in advance - Bill

Hello,

I have CQRLOG 2.2.0 and WSJT-X 1.9.0-rc3 working well together on Ubuntu 16.04.

Let's say I see a particular call sign appear on the WSJT-X decode list and I'm interested in working him. Before I do that I want to check my log to see if I've worked him before. Because CQRLOG is in Offline mode for wsjt remote operation, I can't enter the call sign in the New QSO window and press Tab to see what appears in the table above.

Is there another way to search previous QSOs in this scenario?

Please help, I get an error -2 when I try to upload to LOTW webpage.

I ran CQRLOG from the terminal with debug=1 and this is the output:

**** DEBUG LEVEL 1 ****

SSL libraries:

I have been creating a new log each year (though I'm still using Log17 here in April 2018...). When I try to "Open new log" (from the "new QSO" window) and select, say, Log14 to see my 2014 QSOs, the "new QSO" window shows Log14 at the top but, as expected, the QSO list window is blank. I used to open these previous-years' QSO lists, though I don't remember the method, but am now finding that choosing either "Show QSO list" from the "New QSO" window, or "Refresh data" from the blank QSO-list screen, produces this error message:

Hi Petr,
When I run the import from LoTW with CQRLOG, I realized, reading the ~ / .config / cqrlog / lotw / files.adi, that when I do two QSOs with the same OM on the same band and on the same day, but with different ways (example: CW and FT8), the second QSO (FT8) is seen as a duplicate and CQRLOG does not record the relative confirmation. So I am obliged to use "Edit details" and manually insert the second QSO in "LoTW QSL rcvd date". Obviously, as mentioned above, the two QSOs are regularly reported in the file downloaded from LoTW.

There are many changes since last CQRLOG release. The list of all changes is here: https://github.com/ok2cqr/cqrlog/commits/master
The changelog is really long, most of the changes done by Saku, OH1KH.

I've created both 32bit and 64bit versions.

I picked up a RIgExpert to play with. I also have an IC-706MKIIG radio. I know the complete setup under Windows. I have not been able to get the system to work under OpenSuse 42.3.

The Audio Sound card shows up....
ls /dev/ttyUSB* shows nothing
ls /dev/ttyS* shows a list, not just active ports
Any ideas on what I need to get it working?

TNX Will WC2L