CQRLOG - bugs

Switching databases leaves QTH profile at previous DB

Submitted by N0NB on

I hate to add to your already long TODO list. ;-) I have several databases, each for a specific callsign I've used and am using QTH profiles to manage my operating locations. So far, so good.

I have found that when I open CQRlog anew and select a DB, work in it a while, and then select 'File|Open or Create New Log' that after opening the second DB (or any subsequent DB) the profiles remain from the first DB open. Closing CQRlog and then selecting the desired DB at the program's start results in the proper QTH profiles being available.

Forums: 

ADIF import -- Region 2 2m frequency rejected

Submitted by N0NB on

I'm importing the logs from the 0.9.x installations (yeah, I'm late) into 1.2.1 on Debian Sid. In one log I have four frequency errors I cannot resolve. I noticed that all four of the frequencies are in the upper part of the 2m band which is legal here in the USA. I went into the preferences adjusted the band limits for Region 2, USA. I tried the import of the four errors (after edting out the ERROR: lines) and received rejection of all four records.

Forums: 

Not all QSO's exported for QSL label printing

Submitted by do4nw on

Since CQRLOG 1.x, only the first few hundred QSO's or so are shown in the QSO list instead of all QSO's. Is there a way to show all QSO's again?

It's troublesome because of this issue: When i click on "Export for label printing", only those QSO's that can be seen in the QSO list are exported, but not the complete logbook.

Forums: 

TX Control sometimes does not work

Submitted by do4nw on

Every third program start or so the TRX control shows the frequency 0.0000 and CAT does not seem to work.

I'm using Ubuntu 10.04 with a Yaesu FT-847 and CQRLOG 1.2.1.

Here is the console output when TRX does not work:

test@shack:~$ cqrlog
Loading libssl: /usr/lib64/libssl.so
Loading libcrypto: /usr/lib64/libcrypto.so.0.9.8
Loading libmysqlclient: /usr/lib64/libmysqlclient.so.16
*
User home directory: /home/test/
Program home directory: /home/test/.config/cqrlog/
Data directory: /home/test/.config/cqrlog/database/

Forums: 

dxclusters table corrupted

Submitted by AB1KW on

For unknown reasons, sometimes cqrlog corrupts the dxclusters table. After that happens, clicking the "Select" button in the dx cluster window results in a "Operation cannot be performed on an inactive dataset." pop-up, asking me to either kill cqrlog or risk data corruption.

Other windows still work fine, for example the QSO list.

Running myisamchk -r on the dxclusters table (after quitting cqrlog!) does not seem to fix the issue...

Forums: 

DXCluster window doesn't show calls anymore

Submitted by oh2bsc on

A strange thing happened today. DXCluster window stopped showing calls. I normally use web option, and noticed it first there. On telnet side the connection is taking place normally, but then, no calls are shown. On the same PC xdx works normally, so it doesn't seem to be related to any firewall, IP or other settings.

Any ideas?

Pekka OH2BSC

Forums: 

CTRL-F2 doesnt work when New QSO window is focused (active)

Submitted by om0xa on

CTRL-F2 doesnt work when New QSO window is focused (active). I must click on some other window and then hit CTRL-F2 to clear all fields in New QSO window.
This issue is present in Version 1.1.0 and also in old 0.9.6

I am using Ubuntu 10.10 for i386.

Duro, OM0XA

Forums: 

DXCC Statistics - LOTW only does not count LOTW statistics

Submitted by AB1KW on

When looking at the "DXCC Statistics - LOTW only" window, I see a large number of Ls all over the screen, indicating confirmed band countries.

However, the statistics show 0 confirmed on any band, any mode. For some reason LOTW statistics are not counted in the DXCC Statistics LOTW only window.

Forums: 

ADIF Import Error Detection fault

Submitted by AC7PN on

I just finished importing 2250 QSOs using the ADIF format. The error detection found some errors in my import file which I fixed one by one.

However I had one error on one record of the ADIF file which was not caught or displayed as an error. Instead the import process just halted at the bad record and it reported a successful import but with many of the records missing. This could be a problem for someone doing an import if they don't catch the fact that the number if records imported is wrong.

Forums: 

Pages

Subscribe to RSS - CQRLOG - bugs