开云体育

Hi Dave.

Not seeing the accumulated logs (and a lot of other problems) maybe a result of that change some years ago to use $HOME/.fldigi/.fldigi when it was previously just $HOME/.fldigi

eg my older installation in $HOME/.fldigi/fldigi.prefs defines the macro files as;

last_macro_file:/home/xxxx/.fldigi/macros/macros.mdf

Whereas some experimental configs add an extra "'.fldigi". eg

last_macro_file:/home/xxxx/.fldigi.experimental/.fldigi/macros/macros.mdf

(The .nbems directory also gets put in the later .fldigi structure)

Also check fldigi_def.xml for every reference to a file/directory location, that is valid for your installation. Mine for example are;
<THOR_AVATAR_IMAGE_FILE>/home/xxxx/.fldigi/avatars/vk2yqa.png</THOR_AVATAR_IMAGE_FILE>
<CTYDAT_PATHNAME>/home/xxxx/.fldigi/</CTYDAT_PATHNAME>
<XMLRIGFILENAME>/home/xxxx/.fldigi/rigs/IC-9100-D.xml</XMLRIGFILENAME>
<LOGBOOKFILENAME>/home/xxxx/.fldigi/logs/logbook.adif</LOGBOOKFILENAME>
<WEFAXSAVEDIR>/home/xxxx/.fldigi/wefax/</WEFAXSAVEDIR>
<KML_SAVE_DIR>/home/xxxx/.fldigi/kml/</KML_SAVE_DIR>
<AUTO_PROG3_PATHNAME>/home/xxxx/bin/logsn3</AUTO_PROG3_PATHNAME>

Oh and make sure you haven't merged an old and new tree together. There would normally be nothing except .fldigi and .nbems directories within the newer $HOME/.fldigi one. Any mixing might explain the lack of logfile visibility too.

As an in initial check in a shell box, cd to the directory you want to check and;

find . -print

Then post the output here along with fldigi.prefs and fldigi_def.xml. Check that there is only one file of that name in your tree. (Pls verify nothing personal/private gets posted)

Hope this makes sense!

Cheers Bob VK2YQA