Re: Could not unregister, regression

> Damien Sandras a écrit :
>> Le lundi 15 juin 2009 à 13:07 +0200, Eugen Dedu a écrit :
>>> Julien Puydt wrote:
>>>> Michael Rickmann a écrit :
>>>>> Eugen Dedu schrieb:
>>>>>> Michael Rickmann wrote:
>>>>>>> longer. Also the subcriber threads do not terminate any longer.
>>>>>>> Ekiga needs considerably longer to shutdown than it took one week
>>>>>>> ago and does
>>>>>> I noticed it too...
>>>>>>
>>>>>>> Another point: Ekiga cannot be compiled since opal version 2258
>>>>>>> because the SIPEndPoint::Message form called in
>>>>>>> sip-endpoint.cpp:360 no longer exists.
>>>>>> I am working on this.
>>>>>>
>>>>> Strange things are accumulating at this point. I went back to Ekiga
>>>>> 7bb1d0 (Updated Spanish translation) and Opal/ptlib 22836 which
>>>>> correspond to the state at Wed Jun 10. Ekiga's unregistration was
>>>>> already broken at that time. But the subsriber threads were still
>>>>> shutting down and Ekiga could shut down under gdb.
>>>> Here the situation is the following :
>>>> - enabling/disabling account works ;
>>>> - although disabling seems to always give an error message (I need
>>>> to investigate) ;
>>> This last point: I noticed it too since the beginning.  I wanted to
>>> fix it in the same time as many other (user confusing) problems with
>>> registration.
>>
>> Do those problems affect STABLE too?
>> Are they due to changes in OPAL or in Ekiga?
>
> Looking at a -d 4, it seems that ekiga asks to unregister by trying to
> register again, and gets a 489 Bad event back...
>
> Perhaps my recent refactoring of the account code is responsible for the
> problem...