OK, here is the next fldigi crash on PI4TUE.... The terminal says: E: ModulateXmtr: Sound error: Connection timed out E: ModulateXmtr: Sound error: Connection timed out E: ModulateXmtr: Sound error: Connection timed out E: ModulateXmtr: Sound error: Connection timed out E: ModulateXmtr: Sound error: Connection timed out E: ModulateXmtr: Sound error: Connection timed out E: ModulateXmtr: Sound error: Connection timed out E: ModulateXmtr: Sound error: Connection timed out E: ModulateXmtr: Sound error: Connection timed out E: ModulateXmtr: Sound error: Connection timed out E: ModulateXmtr: Sound error: Connection timed out E: ModulateXmtr: Sound error: Connection timed out E: ModulateXmtr: Sound error: Connection timed out E: ModulateXmtr: Sound error: Connection timed out E: ModulateXmtr: Sound error: Connection timed out E: ModulateXmtr: Sound error: Connection timed out E: ModulateXmtr: Sound error: Connection timed out E: ModulateXmtr: Sound error: Connection timed out I: ParseMode: ARQ new modem set to PSK500R I: ParseMode: ARQ new modem set to PSK500R I: ParseMode: ARQ new modem set to PSK500R I: ParseMode: ARQ new modem set to PSK500R I: ParseMode: ARQ new modem set to THOR4 I: ParseMode: ARQ new modem set to THOR4 I: ParseMode: ARQ new modem set to THOR4 I: ParseMode: ARQ new modem set to THOR4 I: ParseMode: ARQ new modem set to PSK500R I: ParseMode: ARQ new modem set to PSK500R I: apply: RSID: PSK250R @ 1497 Hz I: apply: RSID: PSK250R @ 1497 Hz I: apply: RSID: PSK250R @ 1523 Hz I: apply: RSID: THOR_8 @ 1507 Hz I: apply: RSID: THOR_8 @ 1507 Hz E: trx_trx_receive_loop: Sound error: Connection timed out The X display is not updated anymore, although the window frame will still take comands.... Rein EA/PA0R/M >I use hamlib for all rigs (K2, K3, FT897). >The IC7200 has an internal USB sound card. So I guess it is >handled by the USB sound driver.... >The error message for the PTT is: >E: trx_trx_receive loop: Sound error: Connection timed out > >When the program freezes, the ARQ socket is stiil taking commands from >PSKmail... >They are printed to the terminal and also to the Event log window. > >sorry, this time fldigi was running without a terminal, as I was away for >only 2 hours.... > >Restarting fldigi without a killall, it gave the following error messages: > >E: init_stream: Could not find device "", using default device >E: start: Could not start ARQ server (bind: Address already in use) >Multiple instances of fldigi?? >E: start: Could not start XML-RPC server (bind: Address already in use) > >Restart WITH a killall gives the following error message: >Expression 'snd_pcm_hw_params_set_format( pcm, hwParams, Pa2AlsaFormat( >hostFormat ) )' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 1077 >It works anyway... > >The above shows that although the display thread was dead (see attached screen >dump) >the socket threads were still running... > >Next time I will send you the output of the teminal.... > >Rein EA/PA0R/M > >BTW, the server is running on ubuntu 10.04 (uptime 307 days)... > > > > > >>"the fldigi problem is due to improper handling of exceptions in the >>area of the arq socket, the rig control socket, and the sound driver. >>... I always get the freeze after a timeout of the software PTT >>command from rig control, or after a timeout of the sound driver on >>the IC7200." >> >>Couple of questions please: >> >>* What do you use to control your rig ? Hamlib ? >>* What is exactly the "sound driver on the IC7200" ? >>* Which kind of operations are occuring on the arq side when it happens ? >> >