I am almost sure 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. Unfortunately I am not a C++ programmer... 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. Strangely enough, its the thread doing the X display that freezes, all other threads seem to be running... I should like to get into a situation where we are able to repair the stuff ourselves, and not be reliant on other people. Unfortunately I still have an intermittent problem with the THOR modems in jPSKmail version 2. After that is solved we could think about an integrated solution for the client, and a separate java modem for the server.. I am OK with a skype session from here, just bought a wifi ticket for the next 4 weeks :-) Fixing some more bugs in jPSkmail 1.5.5 at the moment, during the few hours a day we don't have the sunshine... 73, Rein EA/PA0R/M >Hi all, > >Thanks to those that have added rows to the spreadsheet! >At the moment I can't see any significant fact that could help locate >these issues. Perhaps if we add more stations to the spreadsheet? >It is here btw: http://bit.ly/AeKwmx > >Larrys suggestion here is something I have done in the past so is worth >testing. At the moment my server is between crashes so I am waiting for >the next and will try that again. I have done that in the past so I'm >afraid it will not fix the situation. > >It's very unfortunate that fldigi is so unstable, perhaps we need to >consider our options here (skype conference?). >One thing I have done is to prepare a script that kills fldigi and the >server and then relaunches it. If I can check if fldigi has crashed then >I can have cron launch that script periodically. It's not a fix for >fldigi, it's more of an ugly band aid... > >73 de Per, sm0rwo > > >Larry Levesque skrev 2012-02-14 19:57: >> This is always my first suggestion: >> >> Backup and then delete your fldigi configuration directory. >> >> Now try running fldigi again. Let us know how it works. >> >> >> On Tue, Feb 14, 2012 at 07:13:39AM -0600, Bernard Dekok wrote: >>> I get the flDigi lockup on my little Acer Netbook client all the time >>> recently. (Not previously.) >>> Could be memory related, but I doubt it. >>> Could be RF in the system, maybe..., but testing with low power into a >>> dummy load, so doubt that too. >>> >>> flDigi on my server has been running fine from the gitgo. >>> >>> Will investigate the setup differences between the two flDigis and report >>> on your spreadsheet. >>> >>> KC9SGV >>> >>> >>> On Tue, Feb 14, 2012 at 3:35 AM, Rein Couperus <rein@xxxxxxxxxxxx> wrote: >>> >>>> Very nice initiative, this is my main pain in the butt.... >>>> Have to restart PI4TUE 2x a day... >>>> >>>> Rein EA/PA0R/M >>>> >>>> >>>>> Hi all, >>>>> >>>>> This is an old subject but it seems some are still experiencing lockups. >>>>> I tried to find the cause earlier and got as far as pointing the finger >>>>> at rigcat (that part handles ptt and is used even if not selected). I >>>>> then had a patch on fldigi to try to log more during the next crash but >>>>> it never came.. What I did find earlier was that it happened during ptt >>>>> on/off and could be related to frequency change during those events. As >>>>> some still have to restart fldigi now and then I figured we could >>>>> perhaps find something in common if we gather some more data about the >>>>> servers with issues. Its a longshot but could be interesting anyway. I >>>>> put a simple spreadsheet here: >>>>> http://bit.ly/AeKwmx >>>>> >>>>> You are all welcome to add details to that spreadsheet if you wish, >>>>> perhaps we can see something that helps thack this issue? >>>>> >>>>> 73 de Per, sm0rwo >>>>> >>>> >>>> >>>> >> > > >-- >Mobile: +46703784299 >