Hello everyone,
untill now, I have always used CQRLOG on my RaspberryPI with ARM64 (installed from tarball) without any issue.
Good job, indeed.
A few days ago I tried to install it on a new machine with Debian, but without success.
1) Linux 6.1.0-37-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.140-1 (2025-05-22) x86_64 GNU/Linux up to date
2) mariadb apparently up and running :
sudo mariadb
Welcome to the MariaDB monitor. Commands end with ; or \g.
Your MariaDB connection id is 44
Server version: 10.11.11-MariaDB-0+deb12u1 Debian 12
3) hamlib installed from source :
rigctl --version
rigctl Hamlib 4.7~git 2025-06-24T12:43:37Z SHA=0ddc6b 64-bit
4) but, trying to install :
dpkg -i cqrlog_2.5.2-1_amd64.deb
still gives dependency error :
cqrlog : Dipende: libhamlib2 (>= 1.2.10) ma non è installabile
Dipende: libmariadbclient-dev ma non è installabile
Dipende: libmariadbclient-dev-compat
In any case, libmariadbclient-dev in not available on Bookworm.
Same result trying to install from tarball.
Can someone help ?
Thank-you
IU1IPB Ugo
Hi Ugo!
Check that you have dependency packets installed:
Dipende: libmariadbclient-dev-compat
Can this be installed?
With Ubuntu 22.04 you need these packages:
sudo apt install libhamlib-utils libhamlib4 libmariadb-dev-compat libatk1.0-0 libcairo2 libgdk-pixbuf-2.0-0 libglib2.0-0 libgtk2.0-0 libpango-1.0-0 libx11-6 xplanet mariadb-client mariadb-server mariadb-common trustedqsl libssl-dev libqt5pas1
Try to find corresponding package names for Debian. Should be near by same.
Then you can download the tar file "Complete application directory for other distributions" from cqrlog.com/downloads (actually links to GitHub).
Change to root directory
cd /
and extract downloaded tar (assume it is downloaded to /tmp ) with:
sudo tar -vxf /tmp/cqrlog_2.5.2_amd64.tar.gz --strip-components=1
That should do it.
You can see how I have done install with script by downloading zip from:
https://github.com/OH1KH/CqrlogAlpha/blob/main/compiled/install_Ubuntu22...
There are explaining comments and prints included.
--
Saku
OH1KH
Thank-you Saku for your job and so fast answer,
I have added two dependecies libqt5pas1 libmariadb-dev-compat more, following your indications, and Installed in /tmp.
I have not copied the database from the pi (.config/cqrlog not present).
cqrlog started from /tmp/usr/bin.
cqrlog asks for the "first database creation" as usual, but the creation fails with : TMySQL57Connection : Error executing query: Can't create database 'cqrlog_common' (errno: 2 "No such file or directory").
any suggestion ?
Thank-you
Ugo
Hi!
Have you tried to remove ~/.config/cqrlog if it exist from your earlier tries?
If that does not help the error might be in the mysql (MariaDB) running at port 3306.
Saving log data to local machine uses ~/.config/cqrlog/database folder and starts a new sql server that Cqrlog uses via ~/.config/cqrlog/database/sock socket.
Creating that second sql server affects also to ("main") sql server's (running at 3306) database tables somehow.
I am not SQL guru and I do not know what happens but I have once had a situation where all needed was installed and ~/.config/cqrlog removed but still Cqrlog refused to start with same kind of error like you have (I do not remember it exactly any more).
After the main SQL server (MariaDB at 3306 port) was removed and the folder that it uses (with Fedora it is /var/lib/mysql ) was totally cleaned and then MariaDB reinstalled also Cqrlog started ok (even it starts it's own sql server).
If I remember right it had something to do with databases "information_schema" or "mysql" or "performance_schema" of the "main" sql server.
If you do not have any other use for SQL server at 3306 then you could try to reinstall MariaDB removing packages , checking that folder they used is empty and reinstalling them.
More clever way would be to find out does the main SQL server make something to it's tables when Cqrlog starts the second SQL server of it's own and fix that.
--
Saku
OH1KH
Hi Saku,
I deleted at each attempt .config/cqrlog folder.
In any case I was finally able to install from the debian repository (via apt-get), also if it's perhaps an older version (2.5.2) at the moment.
For doing it was also necessary to start and stop again mariadb service.
In any case up and running : thank-you for your valuated job and for your support
73
Ugo