A couple of years ago I entered a note in a particular station's "Comment to Callsign" field (I normally use only "Comment to QSO") that I now realize was incorrect. It keeps popping up whenever I work him, though. Of course I can manually delete it each new time it appears, but is there a way to keep it from autofilling whenever I work this station?

I've been having this problem since 2013. I start rigctld at boot, it works fine with fldigi, gMFSK, and Xlog. Repeated program starts and stops have no effect, rigctld survives. With CQRLOG, the first time the program starts, it connects to rigctld, and works normally. When I close CQRLOG, rigctld crashes with the message broken pipe.

Here is a snippet from the terminal window where I ran rigctld.

I need help setting up CQRLOG to connect to my Icom 706 MKIIG. I am very new to Linux so be patient with me. It took me about a month and a half just to get the program installed and working. I installed it through Package Manager initially, but I had broken packages that defied being fixed because it was an older version, and the missing files seem to not be available anywhere. Any help I found on line to attempt to rectify that was either incomplete or wrong. No amount of updating helped. Eventually I deleted the old version and figured out how to install the latest stable version.

I have created a built (my first on linux, hope it works!) of CQRLog 2.0.4 for raspbian.

Please use this test and enjoy!

Let me know if there are any issues.

https://www.dropbox.com/sh/x5336lhuszdla0y/AAB77S1iqqY0OFX2ch-eRN9Da?dl=0

Hi,

sorry, i think I've used the wrong subforum so far. Please delete the entry under "open discussion ".

----

In my installation (CQRLOG 2.0.4, Linux Mint 18 KDE) I have a problem with the Clublog upload.

After selecting "Upload all changes", this error message appears in the status window.

Is the summary line data above the log an aggregate of all of the QTH profiles?

i.e., QSO in log, DXCC, DXCC confirmed.

If not, how is it determined or selected?

Thanks and 73,
John W4JKL

At the moment the preset date in "create filter" depends on local time. It would be nice if it could depend on UTC.

vy 73

Olaf, DL4DZ

I recently installed (upgraded from 1.9.0) to v 2.0.4 and have been using the WSJT-X Remote Mode. One thing that I would like to see is to have the Name and QTH populated into the QSO database when the QSO is finished and the QSO is logged. Presently that data is showing up in the New QSO panel along with all the other information (Call, Mode, etc.). However, when the QSO is saved to the database, that information is not brought over as it is with non-remote operating, like CW or SSB.

Hi all
I enjoy the new release 2.04 (001) but.... it is possible to change the icon back to the feather?
I like the old icon, but not the new so much.. Sorry. if it not possible them ok... I know to change icon in the "old" windows... but now i works with Linux Mint 18 32 bit Sarah and there I only a big novice..and only know to press buttons in graphic... Thanks for reading, and sorry for gramatics and spelling. OZ1HYi/5P1W Willy

Hi,

in my installation (CQRLOG 2.0.4, Linux Mint 18 KDE) I have a problem with the Clublog upload.

After selecting "Upload all changes", this error message appears in the status window.

If I use the menu /QSL/LoTW/Import/Download and process data from LoTW website the following message occurs:
"Something is wrong because LoTW server returned invalid adif file header. Yout LoTW username/password could be wrong or LoTW server is down.
Do you want to show the file?"
My access credentials are definitely right and the LoTW server isn't down.
But if I check the returned file from LoTW, I see that this isn't an ADIF file.
So the message "invalid adif file header" seems to be right, because of the non-ADIF-file.

i had the 'access violation' issue with Mint 18, and since i only had 1 QSL since my last system backup (Clonezilla) on Jan 5th, i decided to restore from backup, import log backup, and delete dupes. Worked fine and now i say no to Update DXCC list.
 
However this morning when i fired up the system, my window placement was messed up. All the windows were in the top left corner of the monitor on top of each other. Any way to restore previous behavior of the system remembering the established window positions?