WSJT-X import using locator instead of the Callsign on DX Spots window

[K7DZE]

In the attached screenshot you can see the WSJTX import for 2 CQ calls
K2J and K2M (see note section for the actual call)
However the DX Call column is showing the locator (FM06 and EN90)

WSJTX version 2.4.0 (running on ubuntu)
RumlogNG version 5.6 (489)

[K7DZE]

This behavior seems to be occurring with 1x1 callsigns.
Here in this screenshot you can see the callsign is W4C, but Rumlog is displaying data for EL95.

The second line shows another call that is parsed correctly, so I think this might be related to shorter calls.

I think something might be off with the data parser.
Rumlog is telling WSJTX to call W4C(auto enabled), not EL95 but it is announcing EL never heard before.

[K7DZE]

Here you can see the same call (W4C) being displayed in the dxspots window as EL95 and the Network window showing Rumlog telling WSJT-X to start calling EL95(second from bottom line).
WSJTX correctly called W4C and when I halted transmission, you can see Rumlog shows the correct callsign being terminate (bottom line)