Ubuntu 16.04 LTS

25 posts / 0 new
Last post
Ubuntu 16.04 LTS


Has anyone tested CQRLOG with any of the Alpha / Beta releases of Ubuntu 16.04 yet? Does anyone know if the official CQRLOG PPA will be updated once the LTS final has been released?

I'm running 15.10 here but plan to move over to 16.04 once it's released in a couple of weeks.

73 Dave G7VGY

ok2cqr's picture
Re: Ubuntu 16.04 LTS

Hi Dave,

next version of CQRLOG will have packages also for Ubuntu 16.04. I hope it will be released this or next weekend. It's almost complete and I'm waiting for feedback to latest beta release.

73 Petr, OK2CQR

Re: Ubuntu 16.04 LTS

Hi Petr,

Many thanks for taking the time to reply! That's great news too, I'm looking forward to installing 16.04 LTS, as well as CQRLOG.

If I can help in anyway, please let me know.

Kind regards,

ok2cqr's picture
Re: Ubuntu 16.04 LTS

Thank you Dave!

CQRLOG stopped working on Ubuntu 16.04 after one of many updates of MySQL. It seems that the version of MySQL is affected by this bug: https://bugs.mysql.com/bug.php?id=80488

CQRLOG didn't work because of one deprecated option in mysql.cnf. I fixed it, CQRLOG created new database and worked fine. But when you try it again, it won't run and in mysql.err is this:

2016-04-08T06:42:40.236224Z 0 [Warning] The syntax '--log_warnings/-W' is deprecated and will be removed in a future release. Please use '--log_error_verbosity' instead.
2016-04-08T06:42:40.236302Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2016-04-08T06:42:40.237260Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.11-0ubuntu5) starting as process 4745 ...
2016-04-08T06:42:40.249367Z 0 [ERROR] Plugin keyring_file reported: 'keyring_file initialization failure. Please check if the keyring_file_data points to readable keyring file or keyring file can be created in the specified location. The keyring_file will stay unusable until correct path to the keyring file gets provided'
2016-04-08T06:42:40.250325Z 0 [Note] InnoDB: PUNCH HOLE support available
2016-04-08T06:42:40.250377Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2016-04-08T06:42:40.250389Z 0 [Note] InnoDB: Uses event mutexes
2016-04-08T06:42:40.250401Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2016-04-08T06:42:40.250412Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.8
2016-04-08T06:42:40.250424Z 0 [Note] InnoDB: Using Linux native AIO
2016-04-08T06:42:40.251114Z 0 [Note] InnoDB: Number of pools: 1
2016-04-08T06:42:40.251321Z 0 [Note] InnoDB: Not using CPU crc32 instructions
2016-04-08T06:42:40.271662Z 0 [Note] InnoDB: Initializing buffer pool, total size = 80M, instances = 1, chunk size = 80M
2016-04-08T06:42:40.283563Z 0 [Note] InnoDB: Completed initialization of buffer pool
2016-04-08T06:42:40.291142Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2016-04-08T06:42:40.346758Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2016-04-08T06:42:40.346967Z 0 [ERROR] InnoDB: Operating system error number 13 in a file operation.
2016-04-08T06:42:40.346998Z 0 [ERROR] InnoDB: The error means mysqld does not have the access rights to the directory.
2016-04-08T06:42:40.347013Z 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
2016-04-08T06:42:40.955714Z 0 [ERROR] Plugin 'InnoDB' init function returned error.
2016-04-08T06:42:40.955774Z 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2016-04-08T06:42:40.955792Z 0 [ERROR] Failed to initialize plugins.
2016-04-08T06:42:40.955806Z 0 [ERROR] Aborting

2016-04-08T06:42:40.955846Z 0 [Note] Binlog end
2016-04-08T06:42:40.955890Z 0 [Note] Shutting down plugin 'MyISAM'
2016-04-08T06:42:40.955929Z 0 [Note] Shutting down plugin 'CSV'
2016-04-08T06:42:40.955945Z 0 [Note] Shutting down plugin 'keyring_file'
2016-04-08T06:42:40.956431Z 0 [Note] /usr/sbin/mysqld: Shutdown complete

I have to find out what to do with that.

73 Petr

I use CQRLog 1.9.0 version

I use CQRLog 1.9.0 version and it works in Ubuntu 16.04 LTS 64-bit. Ubuntu have the lastest updates (2016-04-08). I do not use CQRLog 1.9.0-5 version. 73 Timo OH7JHA

ok2cqr's picture
Re: I use CQRLog 1.9.0 version

Hi Timo,

are you using mysql or MariaDB? I have no luck with cqrlog and mysql in Ubuntu 16.04 32bit. It seems something is with MySQL because when I start program for the first time, it works, even import data, I can log a QSO. But when I close it, it won't start anymore. Even when I try to run mysql itself, it won't work and ends with permission error :(.

73 Petr


Hi Petr,
I checked from Synaptic:
mysql-common 5.7.11-0ubuntu5
libmysqlclient18 5.6.28-1ubuntu3
73 Timo OH7JHA

CQRLog 2.0.0

Nice! CQRLog 2.0.0 works in Ubuntu (Mate) 16.04 64-bit. No problem to install via Gdebi. Good job Petr! 73 Timo OH7JHA

Installing LTS Now...!

I'm currently installing 16.04 LTS on my shack PC, once that has finished I'll install the latest version of CQRLOG via the PPA and will report back on progress.

73 Dave G7VGY

problem with update to 16.04

hi to all, i've updated my ubuntu to 16.04. that was not a good idea : i can't run cqrlog, a window tell me there's a problem with apparmor.....
looking for solution

Best regards

ok2cqr's picture
Re: problem with update to 16.04

Hi Emma,

did you use CQRLOG from my ppa repository? Version in Ubuntu repositories doesn't work at all. There is a script that can fix the apparmor problem, it's in /usr/share/cqrlog/cqrlog-apparmor-fix

73 Petr, OK2CQR

Hi dear Petr,

Hi dear Petr,
in first, i have used CQRlog with Debian, but the soft don't update. HB9HLI tell me that was better use Ubuntu... ok, i use now ubuntu, the soft update automatically. Ubuntu tell me there is an update...with LTS 16.04.... ok, go.... and the problem...

I have used cqrlog-apparmor-fix, the system send : "usr.sbin.mysqld was already modified, no changes needed"

when i run cqrlog, the window to choose the log is empty : i don't see any log !!!
So, i look into mysql : #mysql -u root -p
show databases;
- information_schema
- mysql
- performance_schema
- sys

Many tks fer help

ok2cqr's picture
Re: Hi dear Petr,

Do you have "Save log data to local machine" option enabled? CQRLOG saves data to ~/.config/cqrlog directory and runs it's own instance of mysqld on different port.

Did CQRLOG show any error?


yes the option was enabled.
i've also done a save on a second drive.

i'am testing installation of optional "mariaDB database server"... perhaps....

so, after install "MariaDB...

so, after install "MariaDB...", CQRlog is not present on the system... why ?
i install it back
then, i launch CQrlog, the system display this capture :

what can i do ?

Thanks to help


problem with 16.04

i've installed 16.04 LTS (64 arch) and the problem is already here :
CQRLOG have been installed through the ubuntu software center. But now, when i launch the program, a window tell me "can not loadMySQL library "/usr/lib/i386-linux-gnu/libmysqlclient.so.20" Please check your installation.
So what can i do ?
I've found the file "libmysqlclient.so.20" in the repertory /usr/lib/i386-linux-gnu. so why it doesn't load it ???

Perhaps the "ubuntu software center" don't load the version ???

tks fer help

one more...

Perhaps the "ubuntu software center" don't load the version ???

i want to say it was not the good version for the LTS 16.04

Install synaptic and try to

Install synaptic and try to install with it. Ubuntu software center is not best installer. 73 Timo OH7JHA


Ok Timo,
many thanks for information.

For now, i got two hard drives : using Ubuntu 16.04 on the first, with CQRlog.
The second hard drive is a spare, with debian on it (and also CQRlog).

Good job !
have a nice evening and good trafic on the air....cw sure !

73, Emma

Linux Mint 18 (64-bit) install fails

I have just reinstalled Linux Mint, going from 17.3 (32-bit) to 18 (64-bit), retaining my home directory and reinstalling all applications.
Mostly it has been a very clean and trouble free process, but CQRlog is giving me serious trouble. after install (from Ubuntu 16.04 PPA) it wouldn't start the db, and now I cannot clean it up to try again; dpkg --remove returns a code 1 and leaves depencies with mariadb and mysql.
How do I clean up this mess and what do I install from the ground up?

73, Peter-OZ1PIF

Hey Peter, I am lazy to use

Hey Peter, I am lazy to use Terminal. Install Synaptic. With synaptic remove CQRLog. You have to select "Remove all" not just "Remove".

If you want to remove CQRLog PPA. You have to select Setup >>"Software sources" >> Other software >> Delete CQRlog PPA. My Synaptic is Finnish language so my translation maybe bad.

I have installed CQRLog via Gdebi installer with no any problem. 73 Timo OH7JHA

Install on Linux Mint 18

Hi Timo,
I have now reinstalled Mint! I couldn't clean up the mess!
Which version did you choose? The Debian Package? Did you install mysql or mariadb first? or did you let the cqrlog installation take care of the dependencies?

73 Peter OZ1PIF

Hello Peter, I have Ubuntu 16

Hello Peter, I have Ubuntu 16.04 64bit version. So I use 64-bit version of CQRLog 2.0.1. Downloaded from CQRLog "Download" page https://www.cqrlog.com/files/cqrlog_2.0.1/cqrlog_2.0.1-1_amd64.deb. Used just Gdebi installer. Nothing to install separately, nothing. Just 45 minutes ago clean install CQRLog, no problem. 73 Timo OH7JHA

There must be some difference

I have Linux Mint Mate 18 64-bit, built on top of Ubuntu 16.04, but this is what happens here, when I try starting cqrlog:
Error during connection to database: TMySQL57Connection : Server connect failed.

This is what I find in mysql.err file
160707 19:22:48 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_thread_by_event_name' has the wrong structure
160707 19:22:48 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_instance' has the wrong structure
160707 19:22:48 [ERROR] Native table 'performance_schema'.'events_waits_summary_global_by_event_name' has the wrong structure
160707 19:22:48 [ERROR] Native table 'performance_schema'.'file_summary_by_event_name' has the wrong structure
160707 19:22:48 [ERROR] Native table 'performance_schema'.'file_summary_by_instance' has the wrong structure
160707 19:22:48 [ERROR] Native table 'performance_schema'.'mutex_instances' has the wrong structure
160707 19:22:48 [ERROR] Native table 'performance_schema'.'rwlock_instances' has the wrong structure
160707 19:22:48 [ERROR] Native table 'performance_schema'.'cond_instances' has the wrong structure
160707 19:22:48 [ERROR] Native table 'performance_schema'.'file_instances' has the wrong structure
160707 19:22:48 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.49-0ubuntu0.14.04.1' socket: '/home/pif/.config/cqrlog/database/sock' port: 64000 (Ubuntu)
160707 23:18:29 [Note] /usr/sbin/mysqld: Normal shutdown

160707 23:18:29 InnoDB: Starting shutdown...
160707 23:18:31 InnoDB: Shutdown completed; log sequence number 3150464
160707 23:18:31 [Note] /usr/sbin/mysqld: Shutdown complete

i.e. nothing from today!

I have attached the gdebi output (partially in danish I'm afraid). The only thing I can hitch on to is the fact that it seems to link up to mariadb and not mysql!

73, Peter OZ1PIF


Linux Mint 18 migration voes [SOLVED]

It seems I have found what was wrong (not why). I have, on several occasions reused the ~/.config/cqrlog information after a system reinstall followed by a virgin install of cqrlog with no problems whatsoever.

This time it simply didn't work, with the results as described above.

Luckily I also do an automatic back-up on shutdown to my dropbox, so all QSO data are safe.

I then removed the cqrlog config folder and performed a virgin install and configuration of cqrlog, followed by an import of all QSO data from the back-up file - a lot of work, but, most importantly my logs are available, and cqrlog is running.

73 Peter OZ1PIF