|
|
Post by WX2S on Mar 3, 2022 11:11:10 GMT
Hi,
How can I file bug reports against a version of JTDX on Windows 10? I've seen two serious bugs in 2.2.159 that need to be managed.
73, -Steve WX2S
|
|
|
|
Post by w9mdb on Mar 3, 2022 12:59:00 GMT
You do it here.
And those bugs would be?
|
|
|
|
Post by WX2S on Mar 3, 2022 17:07:23 GMT
You do it here. And those bugs would be? One bug against 2.2.159, for now. As a semiformal bug report:
Defect: Setting call sign and grid in a blank JTDX.ini locks up the application. Date and time filed: 2022-Mar-03 1718Z
Found in version: 2.2.159 Introduced in version: 2.2.159 Environment: Windows 10 Pro, version 20H2, OS build 19042.1526
Severity: Major.
Reason: Prevents basic setup in new installations. Prevents startup with some existing JTDX.ini files.
Steps to reproduce: a. Delete or rename JTDX.ini in the log folder. b. Start JTDX 2.2.159.
Expected: JTDX creates a blank JTDX.ini. Actual: As expected.
c. In Settings->General, set the call sign and grid and click OK.
Expected: Call sign and grid are set.
Actual: Application becomes unresponsive.
Reproducibility: 100%. Environment dependence: Yes. Developers have not been able to reproduce the issue.
Notes: - Also reproduces when JTDX 2.2.159 is run as administrator.
- File permissions on JTDX.ini after 2.2.159 creates it look normal. Full control by SYSTEM, Administrators, and me.
- Appears dependent on environment. OE1MWW could not reproduce the issue at his bench.
- Previously reported issue on setting highlight colors and rules in Notifications may actually be this bug.
- Bug does not reproduce for me in 2.2.158. Therefore it was introduced in 2.2.159.
I thought there might have been a bug in setting the color highlights, but it might have been this one instead, so I'll hold off on submitting that one until I can reproduce it independently of setting the call and grid.
BTW, doesn't Sourceforge come with a bug-tracking system?
73, -Steve WX2S
|
|
|
|
Post by Wolfgang OE1MWW on Mar 3, 2022 17:26:53 GMT
Hi,
How can I file bug reports against a version of JTDX on Windows 10? I've seen two serious bugs in 2.2.159 that need to be managed.
73, -Steve WX2S
Steve,
- can not be reproduced on any of my 3 PC - ( 2 x Win 10, 1 x Win 7), never seen that frozen JTDX before.
- guess it has something to do with your user permissions to write into the JTDX.ini
Maybe a virus scanner or such may prevent JTDX to further write into the JTDX.ini
So, this one is not a bug of JTDX - and could be, the second one has the same roots
Try to start JTDX as administrator.
73's de OE1MWW Wolfgang
|
|
|
|
Post by WX2S on Mar 3, 2022 17:41:58 GMT
Wolfgang, The bug reproduces for me when I run JTDX 2.2.159 as administrator.
I also note that JTDX 2.2.159 successfully creates JTDX.ini. That eliminates the possibility of it being a permission problem on that file.
ED: Wait, no it doesn't, if 2.2.159 doesn't give itself permission to write the file after it creates it. I'll check.
ED: Permissions look normal when the file is created. Full control given to me, Administrators, and System.
ED: Also note that the bug does not reproduce in 2.2.158. So it was introduced in 2.2.159. I edited the bug report to state that.
73, -Steve WX2S |
|
|
|
Post by Wolfgang OE1MWW on Mar 4, 2022 9:07:01 GMT
Wolfgang, The bug reproduces for me when I run JTDX 2.2.159 as administrator. ... 73, -Steve WX2S
Steve,
JTDX ran through 4 release candidates until it became final .159 and it was tested by many beta testers. According to statistic in PSKreporter.info several hundred (!)
users are now on 159 - and what you describe is a very serious 'hickup': you enter
call + QRA locator + OK and JTDX is freezing - up until today no one else reported
such a bug.
You call it 'unresponsive' ? Can you terminate JTDX, do you need the Task Manager
to kill JTDX, or what else ?
Still don't understand your comment about color settings. You say, you start with a plain JTDX (default JTDX.ini after installation), enter call + QRA + OK and JTDX
is unresponsive. How can you change colors now ?
Guess the only chance - terminate all background jobs, anti virus etc. and terminate services, step by step, to see what causes to freeze .159 JTDX on your PC.
Btw. in forum conversation, please do not edit & add text in previous posts, difficult
to follow, if you include my answer in a post before.
73's de OE1MWW Wolfgang
|
|
|
|
Post by WX2S on Mar 4, 2022 12:08:28 GMT
Wolfgang,
I have to use Task Manager to kill JTDX when it locks up.
I will not say more because I am quite angry about the way I have been treated here. I have a PhD in Computer Science and ten years of experience managing a System Test department at Siemens -- you may have heard of that company -- so I do believe I know a few things about software development and defect handling.
-Steve WX2S
|
|
|
|
Post by w9mdb on Mar 4, 2022 12:16:15 GMT
Steve -- tried WSJT-X to see if it works?
|
|
|
|
Post by WX2S on Mar 4, 2022 12:53:13 GMT
Mike, WSJT-X works fine. So does JTDX 2.2.158. Also, Yoshiharu Tsukuura made the helpful suggestion on Facebook of editing in my call and grid into a blank copy of JTDX.ini that 159 creates. I did such an edit using Notepad. 159 still does not start properly after that -- just creates a windowless task that I have to kill with Task Manager. And when I start 158 after that, I get an error popup as shown.  Attachments:
|
|
|
|
Post by WX2S on Mar 4, 2022 14:54:44 GMT
Okay, I have a data point. The problem is related to wsjtx_log.adi. When I delete it, 159 functions normally.
2.2.158 works fine with exactly the same file.
I'm attaching wsjt_log.adi as a zip file. Set the call to WX2S and the grid to FN20 and I''ll bet you duplicate the bug.
|
|
|
|
Post by Wolfgang OE1MWW on Mar 4, 2022 15:55:27 GMT
I'm attaching wsjt_log.adi as a zip file. Set the call wo WX2S and the grid to FN20 and I''ll bet you duplicate the bug.
Your ADIF file is not created by JTDX, it's a renamed file, created by DXKeeper and has a multi line header.
-- ADIF file created by DXKeeper 16.4.5 on 02-Mar-2022 15:26:11 UTC <ProgramID:8>DXKeeper <ProgramVersion:6>16.4.5 <Created_Timestamp:15>20220302 152611 <ADIF_Ver:5>3.0.9 <EOH> --
Difficult to help and find 'a bug', if you don't tell us about this.
Guess, if you change the header to a plain, one line, "WSJT-X ADIF Export<eoh>", all will be fine.
73's de OE1MWW Wolfgang
|
|
|
|
Post by WX2S on Mar 4, 2022 16:49:44 GMT
Why does that file work in 2.2.158 and not in 2.2.159? Was the ADIF parser changed?
"Worked before status is calculated from your WSJT-X ADIF Logging file, you may replace ADIF log file with one exported from your station logging application, Rescan ADIF Log rebuilds the WSJT-X worked before indexes using the current ADIF log file."
WSJT-X 2.5.1 (the latest full release, AFAIK) does fine with that ADIF log that I exported from DXKeeper.
-S. Attachments:
|
|
|
|
Post by Michael 5p1kzx on Mar 4, 2022 16:52:57 GMT
Hi Stephen and Wolfgang
The Header ain't the problem. The problem is missing <EOR> in mani lines. I downloaded the file and testet it here and got the KillByName Error. Took a look at the file and the header was ok. Copied the Header and some lines where the <EOR> was ok over into a new wsjtx_log.adi. And then there was no problem - JTDX just worked as it should. So the problem here is not releated to JTDX but the missing <EOR> in Stephens file. I don't know why it's working in v 2.2.158.
73 de Michael 5p1kzx
|
|
|
|
Post by w9mdb on Mar 4, 2022 17:11:15 GMT
There are no missing EOR's in the file. The multi-line is the address field which is allowed to be multi-line by ADIF standards.
So it's a problem with the ADIF parser in JTDX not accepting correct ADIF format.
Mike W9MDB
|
|
|
|
Post by Wolfgang OE1MWW on Mar 4, 2022 18:54:38 GMT
Nothing to complain, JTDX is just based on WSJT-X, so, it does not break compatibility. Compatibility is only required on RF protocol level. Btw., JTDX is permanently maintained and enhanced - and it's for free!You have done something with the wsjtx_log.adi file, no one dared to do before :-) Now, as we know the reason for
your problem - and the possible bug in .159, change the .adi to the one line header and all is fine. A task of a minute,
compared to the endless hours I had to spend in my job (retired now) to explain bugs in Siemens 'Hicom' PABX software. ;-)
73's de OE1MWW Wolfgang
|
|
