system Linux Mint 18.3 cinnamon 64-bit
cinnamon 3.6.6
4.13.0-45-generic

All was ok before I update to cqrlog-2.3.0. Now the log shows the qso done before but when I want to log a new qso these messages appear :

"Database upgrade crashed with this error:
TMySQL57Connection : Error executing query: Duplicate column name 'rxfreq'

TMySQL57Connection : Error executing query: Unknown column 'prop_mode' in 'field list'. "

And when I want to close the program there is this message :

"Q : Field not found : "RxFreq".

I get the following error when I try to launch:

Error during connection to database: TMySQL56Connection can not work with the installed MySQL client version: Expected (5.6), got (5.7).

I fixed it by removing libmysqlclient-dev. Cqrlog now starts & works fine (2.3).

Synaptic wont't let me remove it because Cqrlog depends on it. I went to the terminal and ran the following command:
sudo apt-get install libmariadbclient-dev-compat

It executed with some errors but removed libmysqlclient-dev.

I am running on Raspberry Pi 3+
I am having trouble with downloading and uploading to LOTW.

LOTW software is already installed and works fine directly.

I tried a filter to see what I could come up with on the DXCC entities I've worked and sent a QSL to but haven't received one back. With the goal being to re-work the ones I need in order to get closer to making Challenge.

What column/field in cqrlog_main is dxcc_ref? I tried this from the SQL console and it fails since there is no column/field named dxcc_ref

select qsodate,time_on,callsign,band, dxcc_ref, lotw_qsls, lotw_qslr from cqrlog_main where lotw_qslr=""

same error as on raspbian.
in rasbian deleting the file called lotw solves the problem ( until cqrlog creates that map again )....

sadly in debian 8 it looks that cqrlog on startup first recreates the map i delete and then servers me the same error again...

seems this software is all but happy to run on more than one linux distro.
if it stays as unstable i guess i will be better using a maybe not that complete software that is multiplatform ready or at least is willing to run decent on debian as i am no hero with linux and shure not a programmer.

I am using Slackware64-Current. I tried to compile carlog, 2.3.0, &, even though I had all the listed dependencies, the make died very quickly. I then repackaged your binary into a Slackware package & it seemed to work fine. But when I used it in remote mode for wsjtx, & it imported a contact, a window appeared announcing that the date was not formatted correctly. When I pressed the OK button in the warning window, the contact was erased from cqrlog, without giving the opportunity to fix the date. Packaging 2.2.0 & "upgrading" 2.3.0 with it solved the problem.

Hello everyone.

I tried to update version 2.3 on 2.1 my raspberry pi 2B but the result has been catastrophic.

When trying to reinstall version 2.1, I no longer recognize the database or allow me to start the program.

Does anyone have a solution?

cqrlog --debug=1

**** DEBUG LEVEL 1 ****

SSL libraries:

I would like to make a new log that covers just this month, June. So this is what I did.

Hi Petr!
I state that i use debian "buster".
With the previous version 2.2.0-1 the remote mode for wsjt worked well with CQRLog. With the new version 2.3.0-1, when I register the QSO in FT8 a pop-up of CQRLog opens with the warning of an access violation and I have two options: "CANCEL" or "SAVE". if I click on "SAVE" I run the risk of corrupting my data, if I click on "CANCEL" CQRLog disappears and only WSJT-X (1.9.1) remains active, however the contact is registered on CQRLog, as well as automatically it is uploaded on CLUB LOG and HAMQTH.

In case anybody is upgrading to Fedora 28:

I'm running CQRLOG on Fedora 28. It's working great now, but I had to add an extra package, mariadb-connector-c-devel to get it working. Without that devel package, CQRLOG gives this error:

. . . . Can not load default MySQL library ("libmysqlclient.so.16" or "libmysqlclient.so").

Installing that devel package provides the libmysqlclient.so library, and happiness ensues.

CQRLOG ONLINE LOG UPDATE TAKES A LONG TIME TO UPLOAD HALF A DOZEN NEW QSOS TO CLUBLOG . IT UPLOADS A CALL, THEN LATER DELETES IT AND THEN DOES AN UPDATED UPLOAD FOR SAME CALL. IT UPLOADS EACH CALL TWICE AND DELETES EACH CALL ONCE. ANYONE KNOW IF THIS IS CORRECT BEHAVIOUR? IS DELETING ANYTHING CORRECT? A MANUAL UPLOAD TO CLUBLOG WITH AN ADIF FILE SEEMS TO WORK MUCH FASTER.
A RECENT UPDATE WITH THE ONLILNE LOG FEATURE OF CQRLOG GAVE THE FOLLOWING RESULT IN THE STATUS BOX. ALL THIS FOR NINE QSOS.