Problems with new 2.1.0 WSJT window

6 posts / 0 new
Last post
kk5ni
Problems with new 2.1.0 WSJT window

Been using 2.0.5, upgraded to 2.1.0, but it errors out most of the time when "Remote mode for wsjt" is enabled.
Only occasionally does it successfully open the new activity window. Most of the time the program crashes.

2.1.0 from tar.gz, Centos 6.9
--debug=1
...
LoadForm: frmNewQSO
Socket created!
Bind issued 127.0.0.1:2238

(cqrlog:13870): Gtk-CRITICAL **: IA__gtk_text_iter_get_buffer: assertion `iter != NULL' failed

(cqrlog:13870): Gtk-CRITICAL **: IA__gtk_text_buffer_apply_tag: assertion `gtk_text_iter_get_buffer (start) == buffer' failed
TApplication.HandleException Access violation
Stack trace:
$0000000000000000
Setting UDP decode to HiSpeed
Header position:1 Schema number:2 Message type:1 Status Id:WSJT-X
...(cqrlog:14916): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
TApplication.HandleException Access violation
Stack trace:
$0000003112A601F0

or sometimes:

(cqrlog:14916): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
TApplication.HandleException Access violation
Stack trace:
$0000003112A601F0

oh1kh
Problems with new 2.1.0 WSJT window

Hi !
Seems like it is GTK issue.
Centos 6.9 is not the latest one, have you done updates lately? Specially gtk ones?

These are complicated problems as linux has so many different desktops based on different programs.

If you have x_64 cpu you could try the binary file from my devel zip from http://www.saunalahti.fi/~sakny/bin/cqrlog2/
if it acts different way.
Just copy the file cqrlog from zip to /usr/bin (you could save the old one first)

Or install fpc and lazarus and get source code from GitHub and compile it locally. Then it should fit your system perfect.
But it is a "long road". Specialy if you are not familiar with Lazarus GUI. And there may be some additional problems with fpc and lazarus installs, too.

If the 2.0.5 was running ok upgrading to 2.1.0 is just a copy of new cqrlog binary file over the old /usr/bin/carlog.
If you can roll back to 2.0.5 and it runs ok you could just try to replace the file /usr/bin/cqrlog, not install it from centos 2.10 package.
You get the binary file either from cqrlog download page. Download tgz and extract it to /tmp and pick the file.
Or get my devel binary from zip.

--
Saku
OH1KH

--
Saku
OH1KH

kk5ni
210-139 CQRlog working better for me

Thanks, Saku! I'm on gtk2-2.24.23-9.el6.x86_64, the latest version for Centos 6.x (as far as I go with Centos because of systemd in Centos 7).
The binary from 210-139 behaves a little better for me, so I think I'll stick with that for now. Same error, but not as often. Once the window is opened successfully, it is stable. I don't normally shut down CQRlog, so I can deal with it for the added feature :)

Ultimately, I'd like to build CQRLog on my Raspberry Pi 3 running Slackware ARM. I installed Lazarus IDE and fpc on the Pi to build AlarmeJT, so I understand what you're saying about additional problems. There were problems in indy as well.

kk5ni
210-001 on Slackware ARM/Raspberry Pi 3 progress

An update ... I built 210-001 from the source tar.gz with Lazarus 1.9.0 and fpc-3.0.2. I had to update a lot of deprecated UTF8Length and related things to LazUnicode in src/richmemo/*. Also had to remove src/RegExpr.pas because it interfered with synedit. Here is the problem, again with the wsjtx window:
TApplication.HandleException Invalid type cast

I will try again with the current code from git.

ok2cqr
ok2cqr's picture
Re: 210-001 on Slackware ARM/Raspberry Pi 3 progress

You can download recent deb files of Lazarus 1.8 and Freepascal 3.0.4 for armhf from https://launchpad.net/~ok2cqr/+archive/ubuntu/playground. Please do not use the repository, it's for testing only. My main repo doesn't have armhf enabled but I can try it with next version of CQRLOG.

kk5ni
Latest commit 420e51c Slackware/Raspberry Pi 3

This time only modification was to synaser.pas to take out the extra baud rates for UNIX (do not apply to RPi):.

With wsjtx monitor window open, when receiving a CQ:

TApplication.HandleException Invalid type cast
Stack trace:
$00424050
$002A1EE0
$005D8194 line 781 of richmemo/richmemo.pas
$001AA91C line 152 of fMonWsjtx.pas
$001AD4F4 line 778 of fMonWsjtx.pas
$000E97B8 line 2280 of fNewQSO.pas
$003F6864
$003F67AC
$0032A530