CQRLOG - bugs

Remote mode

Submitted by CX1FK on

"remote mode for wsjt-x" doesn't work

box marked "run wsjtx after entering to remote mode for wsjt-x" entering the path manually does not work (does not start wsjtx)

the "Browse" button does not open any window to select the binary.

launching wsjtx manually works...

I don't know if it will be stable...

Debian bullseye/testing x86_64

Forums: 

Abort with xcb_io.c:263: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.

Submitted by dh9fax on

Hi,

I'm using CQRLOG with Fedora (current version Fc30) and mysql-community-common-5.7.28-1.fc30.x86_64. Today CQRLOG crashed several times, so I started from the console to get an error message. This is what I received:

$ cqrlog

Cqrlog Ver:2.4.0 (001) Date:2019-10-27
**** DEBUG LEVEL 0 ****
**** CHANGE WITH --debug=1 PARAMETER ****

Forums: 

"No such Username/Password found" error when download from eQSL

Submitted by EA4GRG on

Hi all,

I have an account in eQSL with 2 callsigns (main and secondary) corresponding to 2 locations. I have 2 logs in CQRLOG corresponding them. When I download from eQSL with my main CQRLOG log it works fine but when I try to download with my secondary CQRLOG log it shows the next error:

Size: 5182
Error: No such Username/Password found

In both cases the eQSL username and password are correct. Only QTH Nickname changes from one log to another. Here is the excerpt from debug (password are not showed in URL):

Forums: 

cqrlog+wsjt gives an "Invalid type cast." error message in Fedora 31

Submitted by AC2XM on

I have been using cqrlog with wsjt in FT8 mode for a long time, with no problems. I tried to use it today, and got an error dialog:

Invalid type cast.

Press OK to ignore and risk data corruption.
Press Abort to kill the program.

This message seems to appear as soon as wsjt sends out its UDP message containing the call signs that have been decoded during receive. If I press "OK" in the error dialog, cqrlog keeps running, but my QSOs are not logged.

Forums: 

RST r&t values are not stored

Submitted by EA4HEA on

Hi

I’m using Cqrlog 2.4.0 in Ubuntu 18. I realised since I upgraded from 2.3 that just the first QSOs done with WSJTX are properly stored although all the data are shown in the previous dialog. I push the OK button and all values are shown in the QSO list window except for both RST values.

Please help, all my QSO are being stored incomplete!

Regards

Forums: 

Weird characters at column headers of the NEW QSO window

Submitted by PG4I on

Looks like I have some garbled characters in the column headers, there is a column before 'qsodate' and after 'remarks' with this problem. I have had this problem since I started using CQRLOG, version 2.3 and 2.4 have this. Maybe something to do with uninitilialized strings?

I would like to upload a screenshot but can't seem to find a way to do this.

Forums: 

cqrlog 2.4.0 on Ubuntu 18.04 with MySQL - will not upgrade

Submitted by G4DYA on

Hi,

Upgrade is held back because it wants to remove libmysqlclient-dev

richard@blueberry:~$ sudo apt -s dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages will be REMOVED
libmysqlclient-dev
The following NEW packages will be installed
libmariadbclient-dev libmariadbclient-dev-compat libmariadbclient18
The following packages will be upgraded:
cqrlog

73,
Richard G4DYA

Forums: 

cqrlog 2.3 and 2.4 very slow to start on Ubuntu 19.10

Submitted by HB9FGQ on

Hello,

Some information: cqrlog is very slow to start on a fresh Ubuntu 19.10 installation. It's a i9-9900K 5GHz system with 32G and an AMD RX580 so it's unlikely to be the hardware capability. DB is Mariadb and locally installed (not the native cqrlog "on this host" version), log is moderate, around 2000 QSO's.

It takes up to 30 seconds for the initial window of cqrlog to display the DB selection dialog. However, it appears to be more of an issue with GTK/gnome than cqrlog.

Syslog shows many of the following:

Forums: 

TMySQL57Connection : Error executing query: Incorrect date value

Submitted by ON6MI on

Hi,

After updating to version 2.4.0 I get some errors.

When I choose to open/create new log I get the following error:

Database upgrade crashed with this error:
TMySQL57Connection : Error executing query: Incorrect date value: '0000-00-00' for column 'lotw_qslrdate' at row 1840
----------------------
After clicking on OK I get this error:

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

Forums: 

Pages

Subscribe to RSS - CQRLOG - bugs