Hi all,

I am new to both Linux and CQRlog and am using Linux Mint 18.2 Cinnamon 64-bit.

I tried to install CQRlog from the Archive Manager butr when starting it I got two messages.
“Information… It looks like apparmor is running in yout system. CQRlog needs to add this: ...”
“Error during connection to database. Can not load default MySQL library ...”

I was advised to remove apparmor and did so by
#sudo apt-get remove apparmor

Hi Petr
Is it huge job to add preferences option box, if marked
all EQSLs received, goes direct into log marked as Q?
I'm not collecting any awards and all qsl's are equal,
despite what ARRL says.

I notice on some contacts the ITU zone / CQ zone are already filled in correctly (from the country file in either cqrlog itself or in fldigi) but when I try to update the rest of the information from qrz.com those fields sometimes get blanked (I guess those weren't filled in at qrz). Updating the record after downloading from qrz will reset ITU zone / CQ zone to 0, later showing up as blank.

Would be nice if the zone information was kept as is when there is no valid information from qrz. Sample callsign which shows this is MI6JVC (no offense to said amateur).

There are many changes since last beta release. The list of all changes is here: https://github.com/ok2cqr/cqrlog/commits/master

In short:

- improved CQ monitor window
- adif export fixes
- contest window fixes
- spelling fixes

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

As a very anoying "feature" after upgrade of my Ubuntu to 17.04 (zesty) appeared a new bug - when I want to overwrite the default RST 599 to, say, 579 I get 597 instead. Usually the S value is highlighted, ready to be overwritten with a single keystroke (if needed to give 579, normally is enough to press "7" key). Now it seems that overwritten is not the highlighted character but the following one. This bug applies not to RST fields only but in all fields, no matter whether "Use spacebar to move between fields" option is checked or not.

Hallo, I need help...

On the start of CQRLOG 2.05 cams the following Error:

Error during connection to database:
TMySQL55Connection : Server connect failed.

73 de
Gerhard
DG1BOR

I have a problem with my cqrlog version 1.7.4 making it unwilling to start as you can see from the terminal listing below.

Can anyone advise how I can save the database and move it to the latest cqrlog version 2.0.5?

bjorn@sa0bxi:~$ cqrlog

**** DEBUG LEVEL 0 ****
**** CHANGE WITH --debug=1 PARAMETER ****

Segmentation fault (core dumped)
bjorn@sa0bxi:~$ cqrlog

**** DEBUG LEVEL 0 ****
**** CHANGE WITH --debug=1 PARAMETER ****

Segmentation fault (core dumped)
bjorn@sa0bxi:~$

System is Ubuntu 16.04, CQRLOG and rigctld to my FT1000MP MKV seems to be working.

The issue I have is with the winkeyer_server interface.

The winkeyer_server is running, but when I attempt to open the keyer I receive the following error:

Winkeyer USB
port 6789
/dev/ttyUSB0
------------------------------------------
Keyer is NOT online
Error: (9) Bad file number

I found this error in an earlier post here and grabbed the bash shell script devcheck.sh output enclosed:

I'm getting errors trying to upload a contact to HamQTH. I ran cqrlog with a --debug=1, and here's what I got. Any help would be appreciated. I expect I have invalid data, but I'm not sure what data is invalid.

============================================
data.Text:
u=VE3YDK
p=**redacted**
prg=CQRLOG
adif=201703222337WV6NSSB71672337599599ChristianWVNNFN23FL10085NCDurhamNNNAY20170621
cmd=INSERT

-----------
Response :When uploading a QSO, at least qso_date, time_on, call, band and mode fields must be specified!

Lots of people are having problems with TRX control, Rigctld, But after 4 years of reporting bugs it still not fixed.

repost from earlier

I've been having this problem since 2013. I start rigctld at boot, it works fine with fldigi, gMFSK, and Xlog. Repeated program starts and stops have no effect, rigctld survives. With CQRLOG, the first time the program starts, it connects to rigctld, and works normally. When I close CQRLOG, rigctld crashes with the message broken pipe.

Here is a snippet from the terminal window where I ran rigctld.

Hi Om,
my problem is the trx-control is unstable. Sometimes it works, sometimes it doesn't work. My software:
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=17.04
DISTRIB_CODENAME=zesty
DISTRIB_DESCRIPTION="Ubuntu 17.04"
Kernel 4.10.0-22-generic
-------------
cqrlog --debug=1 >>cqrl.txt :

**** DEBUG LEVEL 1 ****