CQRLOG - bugs

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: 

Manjaro 18.10 [CQRLOG 2.3.0 + mariadb 15.1]

Submitted by W3JDG on

Hello,

I just switched from Ubuntu to Manjaro 18.10 (XFCE). I installed and configured MariaDB first, and then I installed the package cqrlog-bin (https://aur.archlinux.org/packages/cqrlog-bin/) from AUR.

The installation goes well, but when I run CQRLOG for the first time I get this error:

Forums: 

WSJT-X Window Falls Behind

Submitted by KK6KC on

My system runs on a Raspberry Pi 3. I usually have three programs running, CQRLOG 2.3.0 (001), WSJT-X 2.1.0, and a terminal window with cgps running to keep my clock aligned.

Things go well for some time, but after several days of constant use, it seems that the CQRLOG WSJT-X monitor window falls behind. If I quit WSJT-X, the monitor window stays up for a long time. Adding updates even when WSJT-X is no longer running. If I wait long enough, it eventually goes away. While it is up and changing it's display, I cannot get menus to respond in the rest of CQRLOG.

Forums: 

TMySQL56Connection : Error executing query: Can't create database 'cqrlog_common' (errno: 2 "No such file or directory").

Submitted by M7LPD on

When trying to open cqrlog for the first time i get the error.

TMySQL56Connection : Error executing query: Can't create database 'cqrlog_common' (errno: 2 "No such file or directory").

here is the debug output.


Cqrlog Ver:2.3.0 (001) Date:2018-06-17
**** DEBUG LEVEL 1 ****

Forums: 

TMySQL56Connection : Server connect failed.

Submitted by ke5dfk on

TMySQL56Connection : Server connect failed.

Ubuntu Mint
CRQLOG 2.3.0(001)

I can't launch the program I get ...
TMySQL56Connection : Server connect failed....
error when trying to load the database.
The database connection is empty.

What is the fix?
Where is the log database location and file name?
If I update CRQLOG will I lose my logbook?

Thanks
Carlos
KE5DFK

Forums: 

Cannot mark all QSO as uploaded to ClubLog

Submitted by OE3SPR on

Hi!

I couldn't upload a QSO with 4Y1A to ClubLog, because they reject 4Y as entity. Since one edit to that QSO, no further QSO can be uploaded to ClubLog, because it always stops here:

ClubLog: Deleting original 4Y1A
ClubLog: Could not delete original QSO data!

So, I tried to mark all QSO as uploaded to ClubLog to be able to move on. But I get a message box, saying:

Could not mark QSO as uploaded:TMySQL56Connection : Error executing query: Data too long for column 'cmd' at row 1

Forums: 

Pages

Subscribe to RSS - CQRLOG - bugs