Running V 2.3.0 (001) under Raspian V9.
Mysq ver 15.1 Distrib 10.123-MariaDB
File
Prefences
QTH Profiles
Use QTH Profiles
Define-Modify
Edit in New Window
Now if I enter for Locator IO76KT
Then Save
I get the following error.
TMYSQL56CONNECTION error executing Querie
Error in SQL Syntax.
Now as SQL Syntax is a well defined standard it should work with any SQL Database. Mysql or MariaDB should have the same SQL Syntax.
In the previous QSO list appearing at the top of the logging screen is no MODE field.
I have checked the box in Preferences/Visible columns, but the screen shows no MODE field. Can switch on and off other columns, but no effect on MODE.
I'm using Ver. 2.3.0(101)
Did I miss any checkbox in preferences?
Thanks for your ideas.
vy 73 de Helge, DL3SDN
I'm stilll trying to install CQRLOG 2.3.0-1 on my Raspberry Pi 3B ver. 1.2, as I reported in post https://www.cqrlog.com/node/2084. I'm using the
Raspberry Pi .deb package at https://www.cqrlog.com/download. I'm using Raspian 8.0 (jessie).
I am getting a program hang while using CQRLOG 2.3.0(001) 2018-06-17. The exception below prints in console. On the GUI I get a blank dialog box and nothing responds to mouse clicks and I have to kill -9 the program. Here are the steps. I am using Ubuntu 16.04 LTS.
Open CQRLOG
Press CTRL-O in new QSO window
Select Sort -> Date_time Ascending then close
Drag scrollbar to last record
Click downarrow at bottom of scrollbar once
Click downarrow on keyboard
This causes program to hang and blank dialog box to display
Hi There
This refers to a discussion I started in New OS/CQRLOG Install and now Mysql Problems but copied to new topic here
Problems installing CQRLog on Ubuntu 16.04
Apologies for the copy paste. I am new to linux and tried to install CQRlog but do not know what direction anymore.
CQRlog mysql.err. Any assistance will be greatly appreciated.
Pierre
171126 13:10:25 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.
By accident I entered 2 wrong QSOs with the same call back-to-back in cqrlog, which were automatically uploaded to clublog.
I deleted these QSOs in cqrlog.
Now, when a new QSO is being uploaded to clublog, it stops at one of the deleted QSOs. Here is the output of the log upload window:
Uploaded wrong QSOs:
ClubLog: Uploading V6J ... OK
ClubLog: Done ...
ClubLog: Uploading V6J ... OK
ClubLog: Done ...
Trying to upload new QSO:
ClubLog: Deleting V6J ... OK
ClubLog: Deleting V6J
ClubLog: QSO Details Not Matched
Debian 9 testing (unstable), CQRlog 2.3.0, WSJT-X 1.9.1
A problem encountered while logging FT8 QSO:
Cqrlog Ver:2.3.0 (001) Date:2018-06-17
**** DEBUG LEVEL 0 ****
**** CHANGE WITH --debug=1 PARAMETER ****
Good evening,
after spending some time going through the forum I didn't find the answer, so I hope someone could help me here: how can I set frequencies in the bandmap, e.g. "display only spots from a to b" or something like that. Or how can I sort the spots on the bandmap, ascending or descending, for example?
Thanks in advance,
73
Andre, DL4UNY
Hi All,
I know there is some controversy on whether or not Kosovo is a new DXCC entity. Sounds like it's not, but I worked them on 2 bands today using FT8 DXpedition mode. Looks like I can't attach a screen shot or I'd show you what I see, On 40 meters the QSO list shows Kosovo as an unknown country, but on 30 meters it shows as the Republic of Kosovo. Why is that happening?
73
Stan
KM4HQE
Hello,
I had CQRLOG working under Kubuntu 18.04 and then I messed up my OS by removing a package unrelated to CQRLOG. I decided to do a clean re-install of the OS and applications. Now when I try to start CQRLOG, it does not connect to the database. Here is the console output when I try to start in debug mode:
terry@TERRYSPC8:~$ cqrlog -debug=1
(cqrlog:2807): Gtk-WARNING **: 09:40:22.867: Unable to locate theme engine in module_path: "adwaita",
(cqrlog:2807): Gtk-WARNING **: 09:40:22.870: Unable to locate theme engine in module_path: "adwaita",
As far as I understand, each time I delete the call, all fields of the "new QSO" window are reset to the value of the last QSO previously completed (in a situation without any CAT). In my opinion, that makes little sense. The frequency field should not auto-change back. And, once at it, the mode, both RSTs, and pwr are also better left alone, at least in my opinion.
Here is a story that actually happened to me last Saturday:
Hi!
After worked some qsos in IARU HF World Championship contest from portable location and laptop I now moved those qsos to main PC.
I was wondering a while why I lost all contest specific reports.
First thought that ADIF export has something wrong but noticed that it works as should. At same look I remembered that export does split report and contest message (number,message) to different tags than rstr and rsts where they show up in cqrlog's qso list.
Hi All,
Hello
I suddenly get this error when I try to start the program. I have it set up in two computers, connected to remote database in my server. Only use one computer at a time, and stop the program before I start it in the other computer. This just now comes up with error when I try to start on both computers.
"" is an invalid integer.
Press OK to ignore and risk data corruption.
Press Abort to kill the program.
This is the debug data:
Cqrlog Ver:2.3.0 (001) Date:2018-06-17
**** DEBUG LEVEL 1 ****
I realize that openSUSE isn't supported, but any help would be appreciated. On LEAP 42.3 and older I've had no problems with CQRLOG, but this time I did a clean install instead of an update.
What did I not do correctly?
73, KT5TE
Error during connection to database: Can not load default MySQL library ("libmysqlclient.so.16" or "libmysqlclient.so"). Check your installation.
Error:
Greetings,
Due to a SNAFU on my part I managed to hork my radio box (Ubuntu 16.04.4) with a messed up kernel upgrade/downgrade and secure booting EFI (yuck). Anyways, backups and all that made it just a couple hours.
However, when reinstalling CQRLOG I had a hell of a time, throwing the dreaded SQL warning that I'm breaking things (even with 101 patch) and looking at the logs was confusing. Reinstalled MySQL, reinstalled CQRLOG, blew away DB, restored from ADIF, etc.
Good Day!
Thanks for such awesome Linux software. I am having my first major issue after many years of use and am requesting your assistance to get my DB back in use. When I go to the QSO List window, I get the following error message:
"TMySQL57Connection : Error executing query: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '))) as foo' at line 1."
I am currently on Linux Mint 19, CQRLOG 2.3.0, and MySQL 5.7.22-0ubuntu18.04.1
Just completed a rather fun day with WSJTX on FT-8.
Exited and requested a QSO list from CQRLOG.
Received the error in the attached image.
Ubuntu Version 18.04
CQRLOG 2.3.0 (101) 2018-06-19
Just of a sudden, CQRLOG gives this message when I open the QSO list:
TMySQL57Connection : Error executing query: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '))) as foo' at line 1.
Press OK to ignore and risk data corruption
Press Abort to kill the program.
I started cqrlog in the console woth --debug=1 and get the attached log.
I am running Kubuntu 18.04 and I'm not aware of any changes.
Disregard!
Hi,
Could/would you add some new modes to the preference-band-frequencies tab? With the newer digital mode, like FT8, it seems impossible for the DX Cluster and DXCC statistics to properly recognize when you have worked an entity on a given band using a digital mode other than RTTY. For example, I have worked an entity on a given band using FT8, but the program sees that segment of the band as RTTY and any spot in DX Cluster on the normal FT8 segment of the band gets flagged as unworked/needed. Seems like FT8 would fall in the DIGI mode, but it doesn't seem to do that.
I am running my ham related software on a Linux system (Kubuntu 18.04).
I have a quite complex setup with a number of programs communicating with the rig either via rigctld if a program supports it or directly via a virtual serial multiplexer written in python.
In this setup cqrlog is not always running so I start rigctld independently and configure cqrlog not to start rigctld at start up. This is working fine a long as rigctld is not restarted while cqrlog is running or cqrlog is started before rigctld is running.
From this situation comes my wish:
Hello all,
As a great fan of linuxmint , i jumped on the LM19 train quick.....
I did a fresh install of LM19 on my main HAM pc, and after all the normal stuff I usually install, I installed CQRlog.
I used the install instructions on this site, adding the repository, updating and then installing CQRlog.
And i am happy to report that at least the basic functions seem to work out of the box :)
(will test some more, but i do not see anything going wrong, most software versions used, are the same as in LM18.3)
regards,
Alex
PA1SBM
Why does CQ monitor show NA:QSL needed!! for Canada when the DXCC statistics in new QSO shows QLE on nearly every band I've worked Canada on?
I would also like to know what SQL statement is used for that DXCC statistic.
73
Stan
KM4HQE
Recent comments