You are here

cqrlog 2.3 and 2.4 very slow to start on Ubuntu 19.10

7 posts / 0 new
Last post
HB9FGQ
cqrlog 2.3 and 2.4 very slow to start on Ubuntu 19.10

Hello,

Some information: cqrlog is very slow to start on a fresh Ubuntu 19.10 installation. It's a i9-9900K 5GHz system with 32G and an AMD RX580 so it's unlikely to be the hardware capability. DB is Mariadb and locally installed (not the native cqrlog "on this host" version), log is moderate, around 2000 QSO's.

It takes up to 30 seconds for the initial window of cqrlog to display the DB selection dialog. However, it appears to be more of an issue with GTK/gnome than cqrlog.

Syslog shows many of the following:

Oct 30 08:47:38 luna gnome-shell[12056]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Oct 30 08:47:38 luna gnome-shell[12056]: The offending signal was notify on MetaDisplay 0x55c9bab58030.
Oct 30 08:47:38 luna gnome-shell[12056]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.

Upon research, starting cqrlog from the shell as:

dbus-launch --exit-with-session cqrlog

solves the problem - cqrlog starts immediately as expected, and does not clutter up the syslog with the above warnings.

I've put:

alias cqrlog='dbus-launch --exit-with-session cqrlog'

into my .bashrc as a workaround.

Starting cqrlog from the gnome launcher also shows the delayed startup.

Modifying /usr/share/applications/cqrlog.desktop with:

Old:
Exec=cqrlog

New:
Exec=dbus-launch --exit-with-session cqrlog

also solves the problem when starting from the icon.

Interestingly, similar behavior also occurs for tqsl.

73 de Peter, HB9FGQ.

DL7OAP
Hi Peter,

Hi Peter,

i, too, using 19.10 and it works fast, as on 18.04.

Maybe have a look into this thread:
https://www.cqrlog.com/comment/7452#comment-7452

sudo apt install libgtk2.0-0 (ubuntu 19.04 and higher only have libgtk3.0-0, so you have to install libgtk2 manual)

Or did you already pay attention for this?

Bye Andreas, DL7OAP

HB9FGQ
Hi Andreas,

Hi Andreas,

Thanks for the feedback, I’d not seen that one. However, I did check and indeed libgtk2.0-0 is already installed.

Do you run CQRlog as a normal user or as root, as a matter of interest ? I find if I run it as root, it works fast as well. Interesting, worth looking further into.

73 de Peter, HB9FGQ.

DL7OAP
Hi Peter,

Hi Peter,

my main system is a ubuntu 18.04 and on a virtualbox i running ubuntu 19.04 and 19.10 for developing and testing propose. i'm running all version with the normal user, not root.

i just drop my virtualbox and download a complete new ubuntu 19.10 and set it up.
gtk2 was not there, i have to install it and now i, too, get all these mysql server errors.
so my instruction in the old thread for 19.10 just do not work with the freshest 19.10. %-)

so i totally understand all the users which "only" want to start a logging program without beeing a admin and database expert...

i am just lost and at my wits' end, how we can help Petr (and Martin) here with an good solution for the future of cqrlog.

brainstorming:
- maybe we have to switch to a docker maria-db container
- or we have to start a mob programming with a brutal force attackt to get appimage running with cqrlog in combination with a mysql and tqsl
- switching to nosql/flatfile? but many om's like to have a real database which can be run on a external server
- starting a "whiteboard"-thread were we can collect all ideas from the nerds and experts and then can verfiy each suggestion and make a proof of concept?

bye DL7OAP, Andreas

N9KT
I have this exact same issue!

I have this exact same issue! For me it's even worse because after using cqrlog for a minute, my whole computer freezes.

I tried this fix and it works perfectly!

N9KT
The "dbus-launch --exit-with

The "dbus-launch --exit-with-session cqrlog" fix worked perfectly.

I did everything in the thread that DL7OAP gave and it didn't help.

G1EUZ
Thinkpad T495 & clean Ubuntu 19.10

Same issue for me, long load time with white box on desktop environment, before finally showing the splash screen and loading.

"Modifying /usr/share/applications/cqrlog.desktop with:

Old:
Exec=cqrlog

New:
Exec=dbus-launch --exit-with-session cqrlog"

Worked for me.

Laptop Thinkpad T495 & clean 19.10 install.

Mick
G1EUZ