Opened 7 years ago

Last modified 5 years ago

#15350 new enhancement

Buddy list status of "Available - Connecting" problems

Reported by: pazpaz Owned by: EionRobb
Milestone: Component: unclassified
Version: 2.10.6 Keywords:


When the Buddy List displays "Available - Connecting" it's not possible to reconnect this protocol in some cases without first disconnecting and then reconnecting the protocol. It would be nice to have a "Retry" button or be able to reconnect the account without disabling it first. Sometimes I have to disable multiple protocols which are having the same problem only to then reconnect them.

I'm not sure what solution(s) should solve this problem but thought I'd just put the idea out there. Thanks again.

Change History (6)

comment:1 Changed 49 years ago by pazpaz

  • Status changed from pending to new

comment:1 Changed 7 years ago by datallah

  • Status changed from new to pending

What is the situation under which you see this happening?

I think that eventually you'll hit the TCP timeout and it will automatically retry.

comment:2 Changed 7 years ago by pazpaz

I'm sorry I don't have specific examples at the moment. It seems to mostly happen with XMPP connections but I'm not sure there. I woke up this morning to find the same problem, "Available - Connecting" (on a account) and I have no idea how long it was like that. Disabling and re-enabling the account did reconnect it though.

I think maybe a "Reconnect" option in the Status area (Available, Offline, etc) or under the Accounts > accountname menu item might be helpful to the enable/disable flow, but that's just a few ideas. Maybe a better visual indicator that the connection in the list isn't connected, too? The gray used isn't that much different looking from the plain text.

I'll try to keep a better eye on what might be causing this. Thank again.

comment:3 Changed 7 years ago by pazpaz

I caught it happening again and saw the connection to was established. The moment I killed the connection (from outside of Pidgin) the status in Pidgin changed to "Lost connection with server: Remote host closed connection." as normal. When I reconnected it worked fine. It doesn't seem to ever timeout by itself.

When I catch it happening again I'll have the XMPP console and Pidgin debugger running before I kill the connection to see if I can get any helpful info.

comment:4 Changed 7 years ago by datallah

From what you're saying, Pidgin is actually working as intended - it's waiting for the connection to time out and then retrying. If the connection doesn't time out by itself, that's going to be related to your OS TCP connect timeout settings.

This actually this isn't a problem for most people because normally the TCP connect timeout is set up to be a matter of a few seconds.

comment:5 Changed 5 years ago by rekkanoryo

  • Owner changed from rekkanoryo to EionRobb
Note: See TracTickets for help on using tickets.
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!