cqrlog 2.3.0-1 and stack trace in remote mode for wsjt.

9 posts / 0 new
Last post
ik0dwj
ik0dwj's picture
cqrlog 2.3.0-1 and stack trace in remote mode for wsjt.

Hi Petr!
I state that i use debian "buster".
With the previous version 2.2.0-1 the remote mode for wsjt worked well with CQRLog. With the new version 2.3.0-1, when I register the QSO in FT8 a pop-up of CQRLog opens with the warning of an access violation and I have two options: "CANCEL" or "SAVE". if I click on "SAVE" I run the risk of corrupting my data, if I click on "CANCEL" CQRLog disappears and only WSJT-X (1.9.1) remains active, however the contact is registered on CQRLog, as well as automatically it is uploaded on CLUB LOG and HAMQTH.
Below I have extracted the relevant debugging part of CQRLog. You can see a stack trace.

Cqrlog Ver:2.3.0 (001) Date:2018-06-17
**** DEBUG LEVEL 1 ****

SSL libraries:
/usr/lib/x86_64-linux-gnu/libssl.so.1.0.0
/usr/lib/x86_64-linux-gnu/libcrypto.so.1.0.2
Loading libmysqlclient: /usr/lib/x86_64-linux-gnu/libmariadbclient.so.18.0.0
**************************
MySQL version: 10.
**************************
**********************************
MySQL version assigned: 5.6
**********************************
Loaded 118377 LoTW users
Loaded 115544 eQSL users
Loaded 40133 SCP calls

[CUT]

edtName before pressing save:Mark
Start Date :2018-06-18
Start Time: 19:47
WSJTX decode #5 logging: press save
Note:
insert into cqrlog_main (qsodate,time_on,time_off,callsign,freq,mode,rst_s,rst_r,name,qth,qsl_s,qsl_r,qsl_via,iota,pwr,itu,waz,loc,my_loc,county,award,remarks,adif,idcall,state,qso_dxcc,band,profile,cont,club_nr1,club_nr2,club_nr3,club_nr4,club_nr5, prop_mode, satellite, rxfreq) values('2018-06-18','19:47','19:48','EI3KD',50.315,'FT8','+05','+02','Mark','','N','','','','80',27,14,'IO51','JN62BK','','','',245,'EI3KD','',0,'6M',-1,'EU','','','','','','','',null)

SELECT * FROM profiles WHERE visible > 0 ORDER BY nr

SELECT * FROM profiles WHERE nr = -1

WSJTX decode #5 logging now ended
TApplication.HandleException Access violation
Stack trace:
$0000000000429FCE
$000000000080E3E9
$0000000000740123
$00007F5D0EFD5B73
Sending: fmv

F5JQF
Hi !.. same trouble in my

Hi !.. same trouble in my side

73 Yves

f5jqf

Best 73 Yves

Linuxmint 18.3 64bits

oh1kh
cqrlog 2.3.0-1 and stack trace in remote mode for wsjt.

Hi !

If this happens when wsjt-x remote is on, but CQ-monitor (or Wsjtx map) is closed you can pass this with OK safely.
Quick fix is to open CQ-monitor (and minimize it if you do not like it, but not close).

There is one variable reset after logging and if CQ monitor is closed it does not exist.

So it is a clear bug.
I can reproduce this by keeping CQ-monitor closed.

Thanks for pointing this out.

--
Saku
OH1KH

oh1kh
cqrlog 2.3.0-1 and stack trace in remote mode for wsjt.

Hi !

I have fixed this bug (I think) and made also some changes to the function "sTx" that caused this bug. It should now drop TX (if checked) also if split answering to CQ is done from wsjt-x main screen line.

Also added some more text to "auto backup" discussed here https://www.cqrlog.com/comment/6482#comment-6482
And did changes to corresponding help files.

Test binary 2.3.0-101 can be found from my web page http://www.saunalahti.fi/~sakny/bin/cqrlog2/
(source code at https://github.com/OH1KH/cqrlog-devel )
For testing the bugfix it is enough just to unzip only the cqrlog binary itself and replace current /usr/bin/cqrlog with that.
(maybe save the original first...)

If it works as should I'll do pull request to cqrlog-master later.

--
Saku
OH1KH

ok7an
ok7an's picture
Re: cqrlog 2.3.0-1 and stack trace in remote mode for wsjt.

Great work Saku! Please create pull request only with that bug fix, I'll merge it to master and also to 2.3.x branch which will be 2.3.1 bug fix version.

ik0dwj
ik0dwj's picture
cqrlog 2.3.0-1 and stack trace in remote mode for wsjt.

Hi Saku,
thank you for quickly fixing the bug. Your version of cqrlog works well and I will use this for now.

73 Giuseppe IKØDWJ

F5JQF
thank you for your speed to

thank you for your speed to correct the bug. Everything works on my side. I applied the remedy advocated by Saku (binary 2.3.0-101). Thank you again for maintaining this great software.

friendships

Yves f5jqf

Best 73 Yves

Linuxmint 18.3 64bits

AG5OV
Verifying this solves the issue

Registered and came here just to let you know I had the same issue, went through the apparmor + lotw.txt fixes to no avail and found this thread. The -101 works correctly and solves the issue on my 16.04 radio box.

73 AG5OV Rob

N6HMK
Thanks, Saku

Just wanted to add my thanks to you for the bug fix!