QSO not found in log

10 posts / 0 new
Last post
NZ0T
QSO not found in log

I cannot get the QSO not found window to appear when downloading from LOTW. I get the warning window that says there are QSOs not found but when I click YES to see them the window does not appear.

Any help?

73, Bill NZ0T

n3gb
Re: QSO not found in log

Make sure you have the 'External viewers' page filled in Preferences.

NZ0T
I have not changed anything

I have not changed anything there, here is what is filled in:
TEXT FILES - gedit
PDF FILES - evince
IMAGES - eog
HTML - /usr/bin/xdg-open

oh1kh
I have not changed anything

HI Bill!

It is best to set the full path to all of those. Like "HTML" has.
Open console and give following commands to find the full path:
whereis -b gedit
whereis -b evince
whereis -b eog

and copy results to External viewers. In case you do not happen to have one whereis results empty and you have to select another program instead for that case.

--
Saku
OH1KH

NZ0T
Made all those changes and

Made all those changes and the window is still not showing.

oh1kh
QSO not found in log

Hi Bill!

Start Cqrlog from command console with:

cqrlog --debug=1 > /tmp/debug.txt

Go to LoTW download and when it asks do you want to see qsos that are not in log click YES. Then, when nothing appears, close cqrlog.
Then open /tmp/debug,txt with your favorite text editor and search your text editor name that you have set in preferences/external viewers.

My viewer is called "leafpad". When I search "leafpad" from debug.txt I find lines:
------------------
RunOnBackground start leafpad "/home/saku/errors_LoTW.adi"
AProcess.Executable: leafpad Parameters: /home/saku/errors_LoTW.adi
----------------

Check that file shown there exists (my case /home/saku/errors_LoTW.adi) yours will look different.
If file exists then try to start view from command console.
Copy rest of debug.txt line after "start" to console. In my case:
leafpad "/home/saku/errors_LoTW.adi"

That shoud open file in text editor. Does it?

--
Saku
OH1KH

oh1kh
QSO not found in log

Ooops!

Forum messed up the picture, but Ihope you get it ok.

--
Saku
OH1KH

NZ0T
Hi Saku,

Hi Saku,

I'm sorry but I am very confused. My apologies but I'm not very good with this sort of thing. I don't understand what "open /tmp/debug,txt with your favorite text editor and search your text editor name that you have set in preferences/external viewers" means. I think my text editor is /bin/nano but when I enter /tmp/debug,txt nothing happens. I entreated /bin/nano in console which opens a window but hen I enter th edebug nothing happens. I hope this makes sense.

73, Bill NZ0T

oh1kh
QSO not found in log

Hi Bill!

OK. Lets forget the debug.txt for a while.

If you have entered /bin/nano to preferences/External viewers/Text file you do not get anything when trying to open error file. That is because nano is a command console editor and Cqrlog runs in graphical mode.

To find a simple, light, graphical text editor you need to look at you startup menu and find one from there. (to see what your Linux has already installed) .
If that is gedit as you stated before you should put the full path to "preferences/External viewers/Text file"

But if that did not open the error file something is wrong and first we have to find out that you really have gedit installed and see what is the name with full path.
That is where "whereis -b gedit" helps us. Once you have got the full path you can try to enter it to command console and press return.
It should open gedit as a new window.
If it does that you can copy it to "preferences/External viewers/Text file" and try to open error or export files.

For me (Fedora 36) that editor is "leafpad" that is a light graphics mode text editor.
I have also Openoffice installed so I could use also that but it is too heavy for this simple thing although it works ok.

If I write to command console:
whereis -b openoffice.org

It says /usr/bin/openoffice.org and if I enter that to command console it opens Openffice text editor.
Then I can put that to "preferences/External viewers/Text file" and it works ok with error and exported files.

If you have OpenOffice installed you can try also that instead of gedit.

Once you have cleared this part and still do not see error files we go back to /tmp/debug.txt to dig deeper.

--
Saku
OH1KH

NZ0T
Hi Saku,

Hi Saku,

Problem solved! I found that gedit was no longer installed - I have no idea why. I installed it and entered the proper path for texts and all is fine now.

As always thanks so much for your help!

73, Bill NZ0T