Hi all,
I am new to both Linux and CQRlog and am using Linux Mint 18.2 Cinnamon 64-bit.
I tried to install CQRlog from the Archive Manager butr when starting it I got two messages.
“Information… It looks like apparmor is running in yout system. CQRlog needs to add this: ...”
“Error during connection to database. Can not load default MySQL library ...”
I was advised to remove apparmor and did so by
#sudo apt-get remove apparmor
Hi Petr,
i would like to use another program with CAT in addition to CQRLOG.
With "socat" I had so far no success. Access to "/dev/pts/x" is obviously not possible. Do you know another solution.
73, Wolfgang
DL2KI
Hi Petr
Is it huge job to add preferences option box, if marked
all EQSLs received, goes direct into log marked as Q?
I'm not collecting any awards and all qsl's are equal,
despite what ARRL says.
Hi Petr,
having trouble starting CQRLOG on a fresh install of debian 9 64 bit.
First I had to install libmariadb-dev-compat package but after that I now get:
Error during connection to database: TMySQL56Connection can not work with the installed MySQL client version: Expected (5.6), got (5.5.1).
Any ideas?
Thanks & 73
Log follows:
vittorio@ik1rac:~$ cqrlog --debug-1
(cqrlog:4127): Gtk-WARNING **: Impossibile trovare il motore del tema in module_path: «adwaita»,
I notice on some contacts the ITU zone / CQ zone are already filled in correctly (from the country file in either cqrlog itself or in fldigi) but when I try to update the rest of the information from qrz.com those fields sometimes get blanked (I guess those weren't filled in at qrz). Updating the record after downloading from qrz will reset ITU zone / CQ zone to 0, later showing up as blank.
Would be nice if the zone information was kept as is when there is no valid information from qrz. Sample callsign which shows this is MI6JVC (no offense to said amateur).
If you want to be alert when a desired callsign appears in cluster, add this command (Linux) in Preferences -> DXCluster.
You should install zenity first.
zenity --info --text='Callsign $CALLSIGN detected at $FREQ $MODE' --title=Info
Also you may set display duration in 5 seconds (Thanks DL2KI). After the window closes automatically.
KDE
kdialog --title=Spot-Info --passivepopup "Callsign $CALLSIGN detected at $FREQ $MODE" 5
There are many changes since last beta release. The list of all changes is here: https://github.com/ok2cqr/cqrlog/commits/master
In short:
- improved CQ monitor window
- adif export fixes
- contest window fixes
- spelling fixes
I've created both 32bit and 64bit versions.
Right after starting to accept FT8 eQSL decided to upgrade their mode definitions to those of ADIF 3.0.4, so the mode is now "PSK (PSK31)" and not PSK31.
eQSL offers the option to upgrade your outbox, but it seems cqrlog currently is not ready for this change as it does not recognize new PSK (PSK31) contacts at the moment. I saw no announcements from eQSL so I guess they surprised all software developers.
From the eQSL_error.txt file:
As a very anoying "feature" after upgrade of my Ubuntu to 17.04 (zesty) appeared a new bug - when I want to overwrite the default RST 599 to, say, 579 I get 597 instead. Usually the S value is highlighted, ready to be overwritten with a single keystroke (if needed to give 579, normally is enough to press "7" key). Now it seems that overwritten is not the highlighted character but the following one. This bug applies not to RST fields only but in all fields, no matter whether "Use spacebar to move between fields" option is checked or not.
I have had intermittent problems in getting CRQLog to talk to my FT2000 for quite some time now, it's always been a battle. I have periods of it working then periods when it wont.
I have recently rebuilt my PC and now run Linux Mind KDE.
Reinstalling CQRLOg onto my new environment saw a brief period where CQRLog would talk to my FT2000, but now it persistently refuses.
I recently installed TR4W contesting software on my KDE PC and even though its running under WINE, per performs flawlessly connecting to my FT2000 every time!
Hallo, I need help...
On the start of CQRLOG 2.05 cams the following Error:
Error during connection to database:
TMySQL55Connection : Server connect failed.
73 de
Gerhard
DG1BOR
I have a problem with my cqrlog version 1.7.4 making it unwilling to start as you can see from the terminal listing below.
Can anyone advise how I can save the database and move it to the latest cqrlog version 2.0.5?
bjorn@sa0bxi:~$ cqrlog
**** DEBUG LEVEL 0 ****
**** CHANGE WITH --debug=1 PARAMETER ****
Segmentation fault (core dumped)
bjorn@sa0bxi:~$ cqrlog
**** DEBUG LEVEL 0 ****
**** CHANGE WITH --debug=1 PARAMETER ****
Segmentation fault (core dumped)
bjorn@sa0bxi:~$
During last week a new mode FT8 is introduced as a part of wsjt-x. FT8 is faster. TX periods only 15sec, but also that's why it is a bit less sensitive mode mainly planned for ES openings on 6m and up, but it is usable also in HF. too. It is a bit wider than JT9, but narrower than JT65.
You can get this wsjt-x 1.7.1-devel only by compile it from source at the moment.
There was some growing activity yesterday on 14.079Mhz .
System is Ubuntu 16.04, CQRLOG and rigctld to my FT1000MP MKV seems to be working.
The issue I have is with the winkeyer_server interface.
The winkeyer_server is running, but when I attempt to open the keyer I receive the following error:
Winkeyer USB
port 6789
/dev/ttyUSB0
------------------------------------------
Keyer is NOT online
Error: (9) Bad file number
I found this error in an earlier post here and grabbed the bash shell script devcheck.sh output enclosed:
I've done it again - and this time without a recent ADIF back-up Grrrr.
I have the ~/.config/cqrlog folder with all content up to date, but when I try to start cqrlog I get:
Error during connection to database:
TMySQL57Connection: Server connect failed
Any way to fix this with creating a new database?
Running Mint 64-bit 18.1 Cinnamon for the record.
I was "just" reinstalling the system to clean up a couple of unrelated problems, did a full back-up of my "home" folder, and plain forgot this problem which I've run into before.
I'm getting errors trying to upload a contact to HamQTH. I ran cqrlog with a --debug=1, and here's what I got. Any help would be appreciated. I expect I have invalid data, but I'm not sure what data is invalid.
============================================
data.Text:
u=VE3YDK
p=**redacted**
prg=CQRLOG
adif=201703222337WV6NSSB71672337599599ChristianWVNNFN23FL10085NCDurhamNNNAY20170621
cmd=INSERT
-----------
Response :When uploading a QSO, at least qso_date, time_on, call, band and mode fields must be specified!
Hi, I'm trying to build cqrlog 2.0.5 from source and i get the following error:
lazbuild --ws=gtk2 --pcp=/tmp/.lazarus src/cqrlog.lpi
SetPrimaryConfigPath NewValue="/tmp/.lazarus" -> "/tmp/.lazarus"
Error: (lazarus) invalid Lazarus directory "": directory lcl not found
Error: (lazarus) Building failed: src/cqrlog.lpi
Makefile:9: recipe for target 'cqrlog' failed
make: *** [cqrlog] Error 2
I have no experience with lazarus and I can't find the problem.
My system is running Slackware 14.2 (kernel 4.4.3.8-smp) and FPC 3.0.2.
Lots of people are having problems with TRX control, Rigctld, But after 4 years of reporting bugs it still not fixed.
repost from earlier
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.
Wish you would fix it.
Hi Om,
my problem is the trx-control is unstable. Sometimes it works, sometimes it doesn't work. My software:
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=17.04
DISTRIB_CODENAME=zesty
DISTRIB_DESCRIPTION="Ubuntu 17.04"
Kernel 4.10.0-22-generic
-------------
cqrlog --debug=1 >>cqrl.txt :
**** DEBUG LEVEL 1 ****
Hi,
I recently expirienced, that not always multiple QSOs are collected to one label.
View "QSO List" -> "Create Filter" (by date) -> "Export for Label Printing"
my export fields are
Date, Time on, Callsign, Mode, RST sent, Band, QSL Manager, Comment, QSL Message (PSE/TNX)
Hi,
first, i have exported all QSO's and then imported into Clublog via the webinterface.
In CQRLOG, after selecting "Online log - Clublog - Mark all QSO as uploaded", a window with this error message appears
-----------------------------------------------------------------------------------------
Could not mark QSO as uploaded: TMySQL57Connection:
Error executing querry: Data to long for clolumn 'cmd' at row 1
-----------------------------------------------------------------------------------------
Hello
how to insert old qso in cqrlog ?
I found a qsl card that I have not encoded, how to add it with the right date (2014-06-21) .... I tried but the program resets to 2017 ???
Thank you
JeanMa
Hi,
I just got my hand on an old and big log that I had to import for a friend and the adif export of that had to be imported to clublog again.
We got the following feedback (beside lots of old and wrongly detected dxccs from old dxpeditions that I will have to ask the friend for before I bother you with that...) from the clublog robot such as:
Callsign: S59/OK1CZ Date: 2004-10-...
Your log claims CZECH REPUBLIC. Overriding your choice and using SLOVENIA.
Recent comments