Bug#876626: RE : Re: Bug#876626: [Xastir] Bug#876626: Xastir loose TCP/IP data afer 12 hours of use

[mlhpub <mlhpub@free.fr>]

Sorry it is 12 hours and not days.

I should have written "12 hours a day"... 

I usually start Xastir on 7.00 am and shutdown around 10:00 pm (saturdays and sundays).

Thanks, I will try update and tell if it is better.

73

Matthieu

F4ACU

-------- Message d'origine --------

De : David A Aitcheson <david.aitcheson@gmail.com>

Date : 27/09/2017 02:07 (GMT+01:00)

À : MLHPUB <mlhpub@free.fr>, 876626@bugs.debian.org

Cc : "Iain R. Learmonth" <irl@debian.org>

Objet : Re: Bug#876626: [Xastir] Bug#876626: Xastir loose TCP/IP data afer 12 hours of use

Matthieu

Please clarify when the problem starts, is it after 12 HOURS or is it
after 12 DAYS? I rarely run my computer beyond 24 hours and probably
only run Xastir about 10 hours at a stretch so I may not be seeing the
issues you are seeing.

Once you convert to building from source for Xastir updating is simple,
just run a included "update" script that does a everything for you. I am
currently running Xastir V2.0.9 (8a3999d) Compiled (from source) on
Monday September 18 2017 at 17:17:00 EDT on my Laptop running Ubuntu
14.04.04-LTS

73
Dave
KB3EFS


On 09/26/2017 05:27 PM, MLHPUB wrote:
> Hello Ian,
>
> I don't know about latest snapshots.
> Maybe it does not occur with 2.0.9 version but I am not comfortable
> with upgrade outside of Debian repositiories...
>
> Regards,
>
> Matthieu
> F4ACU
>
> On Sun, 24 Sep 2017 10:55:13 +0100 "Iain R. Learmonth"
> <irl@debian.org> wrote:
>> Hi,
>>
>> On Sun, Sep 24, 2017 at 05:20:44AM -0400, David A Aitcheson wrote:
>> > > I usually use Xastir during all day, only with a TCP/IP to APRS-IS
>> > > connection at this moment (no radio link).
>> > > After more than 12 days uptime, Xastir loose many data from
>> APRS-IS :
>> > >
>> > > - ACK messages are not received
>> > > - positions reports (even visible on aprs.fi) are not displayed
>> > >
>> > > There is a kind of latency time on RX data from APRS-IS.
>> > >
>> > > It is necessary to quit and restart Xastir to retreive en normal
>> > > behavior.
>>
>> My question would be: does this occur in the latest Xastir snapshots?
>>
>> It's been a long time since there was a release of Xastir and I'm
>> sure the
>> Debian package is missing a number of fixes that have been applied
>> upstream.
>>
>> It's been on my todo list for a while to just update to a git
>> snapshot to
>> get some fixes into the Debian package, but I've not yet had time. If
>> someone can tell me this doesn't happen if you build from source then
>> that
>> would be an easy fix.
>>
>> Thanks,
>> Iain.
>>
>
>