CQRLOG - bugs

Can't enter any data

Submitted by sq7iqi on

In entry field i cant write anything or letter writes dubble.
 
Lubuntu 12.04
CQRlog 1.7.4-1
 
<code>
**** DEBUG LEVEL 0 ****
**** CHANGE WITH --debug=1 PARAMETER ****
 
140701 22:08:59 InnoDB: The InnoDB memory heap is disabled
140701 22:08:59 InnoDB: Mutexes and rw_locks use GCC atomic builtins
140701 22:08:59 InnoDB: Compressed tables use zlib 1.2.8
140701 22:08:59 InnoDB: Using Linux native AIO
140701 22:08:59 InnoDB: Initializing buffer pool, size = 128.0M

Forums: 

CW message macro max length

Submitted by yu1sx on

Hello!
 
Is there a maximum length for CW macro? It seems that more than 151 characters in the macro introduces problems. Here's an example that you can use to test and confirm this bug. I'm using K1EL Winkeyer WKUSB-SMT.
 
Defined CW macros:
 
F1:
cq cq cq de %mc %mc cq cq cq de %mc %mc pse k
 
F2:
%c de %mc %mc pse k
 
F3:
%c de %mc = gd dr om es tnx fer call = ur rst %r %r = my name is   s i n i s a   s i n i s a  es my qth is  i n d j i j a   i n d j i j a  = so hw? %c de %mc pse k
 

Forums: 

Random DXCC reference after DXCC-rebuild?

Submitted by sm6vja on

Hi!
I have noticed that sometimes a QSO has the wrong DXCC reference. In those cases I have just opened the QSO , edited the DXCC ref and saved it just thinking I may have messed something up when entering the QSO.
But now I noticed that 2 or 3 QSOs in the QSO list had wrong DXCC-refs. I re-built the statisticts and suddenly there the references changed, but to other wrong references. I corrected two of them, saved the QSOs and run the re-build of stats and one corrected QSO turned to the wrong DXCC again.

Forums: 

Losing connection to mysql server

Submitted by w1wra on

I have been starting to see this problem with 1.7.4. When I try to up/download log files to eqsl or lotw (this last time it was lotw) I get an error that cqrlog has lost connection to the mysql server. I am running a fairly stock Ubuntu 14.04. Becuase I am paranoid I tend to just hit the cancel button which casues cqrlog to close. 
Is this a known issue? When it happens again, is there particular data I should be collecting?
 
 
 

Forums: 

Pages

Subscribe to RSS - CQRLOG - bugs