Bug#1011449: Info received (Bug#1011449: Acknowledgement (pidgin cannot resume interrupted XMPP connection if no srv_rec available.))

[Mad Horse]

This bug should have been fixed in pidgin 2.14.10-1 since it should 
contain https://keep.imfreedom.org/pidgin/pidgin/rev/ea52fcc50e50 , as 
shown in https://keep.imfreedom.org/pidgin/pidgin/graph/594d72369304 .

Bug#1011449: Acknowledgement (pidgin cannot resume interrupted XMPP connection if no srv_rec available.)

[Mad Horse]

There is already a fix ( 
https://keep.imfreedom.org/pidgin/pidgin/rev/ea52fcc50e50 ) on pidgin's 
repository, although the approach is different.

Bug#1011449: Acknowledgement (pidgin cannot resume interrupted XMPP connection if no srv_rec available.)

[Mad Horse]

The temporary walkaround could be using "old-ssl" or bosh on XMPP accounts,

because their early error-handlings avoid (js->srv_rec).

Bug#1011449: Acknowledgement (pidgin cannot resume interrupted XMPP connection if no srv_rec available.)

[Mad Horse]

This issue should occur when jabber_login_connect() fails and calls 
jabber_login_callback() with an error.


在 2022/5/23 16:00, Mad Horse 写道:
This is because in jabber_login_callback(), when an error occurs 
(source < 0),
if (js->srv_rec != NULL), it will report the error and call 
try_srv_connect()
to try another SRV record, and return, but if (js->srv_rec == NULL), 
it will
return directly without reporting the error, nor any further process. 


It makes things worse that because now the state of affected connection 
is not


PURPLE_DISCONNECTED, further calls of _purple_connection_new() will return

early, making the connection unable to resume. The only way to connect the

corresponding account is to disable it first, (set its state to

PURPLE_DISCONNECTED) and enable it again, manually.