Hi,

I have one problems, (maybe no bug?)

today I watched "qso list" and my last entry there is 2011-12-04, but if I make new qso, that "qso in log" number will growing, but still that last day is same. If I looking for qso, I can find it.

I use different computer in my station, and there is same problem.
I import my qso's, but then in my log is double qso. And still last day is same.

Then I clear my log and import again, same thing again, but now I make again all my settings again.

I have Ubuntu 10.04 LTS.

Any idea how I will fix it?

Hi Peter,

I am not sure is this bug on CQRLOG or on TQSL SW. However when I tried to upload to LoTW some QSO's I had made with my previous version of CQR log (32-bit) Now running 1.2.1 (64bit).

I have 2 logs in my system: log001 and DL3JW. In log 001 I have strange dates on LoTW QSL S date due to invalid certificate. Certificate is now new and in DL3JW log I have got those dates correct.

I have the lotw configured and want to download the lotw log.
It would download, noting how many QSO's then sez download OK

But at this point, CQRLOG freezes, the OK tab is not available and I must close this app
then restart again. Nothing was saved or entered into log from lotw.

Help!

72
Ron, wb1hga

In my preferences I have checked:

Enable auto mark QSO QSL_S fields as: SB
Mark only the first QSO, first band QSO, first mode QSO

Now when I enter a new QSO with a station I never worked before, I check its qrz.com profile if it is ok to send QSL via bureau, and if not, I clear QSL_S to empty. When I update other fields like reports or time, QSL_S gets reset to SB again (not always but pretty often).

It would be great if the automarking would be used only for the default value of QSL_S and then the field would stay at the manually set value.

Sometime in the past few weeks an upgrade to Debian Sid seems to have broken GTK in some way that CQRlog cannot shut down. I've not been able to pinpoint the issue but with the help of Kamal, KA6MAL, I have some terminal output that may be of use. I first noticed this with CQRlog 1.2.1 and it persists with your 1.2.2 .deb installed.

Here is the crash output from 1.2.1 with my databases and configuration:

http://pastebin.com/mHHkxxUr

and 1.2.1 with a clean configuration and new databases:

http://pastebin.com/ubVZAn9N

finally, 1.2.2 with my configuration and databases: