Opened 6 years ago

Last modified 3 years ago

#15380 new defect

pidgin not automatically reconnecting

Reported by: crates Owned by: EionRobb
Milestone: Component: unclassified
Version: 2.10.6 Keywords:
Cc: peto, MintPaw

Description

Running under Win7 SP1 x64. Pidgin seems to quickly and easily "give up" when trying to auto-reconnect after having been disconnected. I experience a lot of disconnections--suspend/resume, moving among connections (my home router bonds cable, DSL, and 3G connectivity), physically moving among wifi APs, starting and stopping various kinds of VPNs. So I often notice Pidgin is only partially connected to my 6 IM accounts on as many services. There's no rhyme or reason among them--sometimes one manages to maintain connectivity, sometimes another. Eventually (if I don't pay attention and keep clicking reconnect), they'll all be disconnected and disabled and non-functional.

I've seen old tickets mentioning this, but they all seem to have been closed. I know Pidgin will do some limited automatic attempts to reconnect, but it's not enough. (If I use a native IM client for any of these services, they will auto-reconnect, so I know it's possible.) Is there any way to have Pidgin keep trying to connect, even if as diffidently as once every ten minutes (forever)? And to allow the end user to tell it to never disable an account?

Attachments (1)

purple-debug.log (1.6 KB) - added by peto 6 years ago.

Download all attachments as: .zip

Change History (10)

comment:1 Changed 6 years ago by warp

I'm seeing the same problem on unreliable internet connections. Pidgin just prompted me with "warpr@…/ disconnected" and "Not Authorized". It offers my two choices, "Modify Account" and "Reconnect". Clicking Reconnect will correctly reconnect the account without making any changes to the account, so the account settings are correct and pidgin for some reason incorrectly flags the connection problem as something which it should not retry.

(This is using Pidgin 2.10.6 (libpurple 2.10.6) 4cfe697ea3ae39a4fb3dad8e3ed1c70855901095 on Ubuntu 12.10).

Last edited 6 years ago by warp (previous) (diff)

comment:2 Changed 6 years ago by peto

I am having the same problem as warp described - Pidgin reconnect correctly after clicking Reconnect, but doesnt do it automatically. But sometimes, when I lost connection and get it again, Pidgin reconnects automatically without asking me...

Pidgin 2.10.7 (libpurple 2.10.7) on Ubuntu 13.04

comment:3 Changed 6 years ago by datallah

"Not Authorized" is a "fatal" error (bad username, passsword, etc.) - i.e. one that wouldn't be resolved by trying again with the same values. It's possible that Pidgin is miscategorizing the error, but in this particular case, it is likely that the server is sending the wrong error.

A debug log of one of these disconnections may provide some more information.

comment:4 Changed 6 years ago by peto

ok, here is my scenario:

I open pidgin, I am logged to Gtalk. Everything is ok. I loose my wifi connection and Ubuntu doesnt reconnect automatically. At this time, pidgin's status is green and says waiting for network... Now, I disable and enable wifi and ubuntu reconnects automatically. At the moment, when it is connected again, pidgin gives me that error that disconnected, unable to connect with 2 buttons: modify account or reconnect.

The same happens, when I manually disconnect from wifi network and then manually reconnect to it. I will attach logs soon.

Changed 6 years ago by peto

comment:5 Changed 6 years ago by peto

I added attachment with my debug log.

comment:6 Changed 5 years ago by rekkanoryo

  • Owner changed from rekkanoryo to EionRobb

comment:7 follow-up: Changed 5 years ago by andyross

The design assumption above seems wrong in some cases. I'm using pidgin (on linux) with the pidgin-sipe plugin using Windows AD/kerberos authentication. If I'm not authenticated on the network, this will obviously fail. But that failure (being "fatal", apparently) will now *persist* once I reconnect.

This is hugely annoying. I need to manually reconnect every morning when I get to work. And of course I forget and people can't find me.

Basically: a failure to authenticate ("Client couldn't do it for some reason") is not the same thing as an affirmative failure to authorize ("Server says: this user is not allowed"), and it seems like pidgin gets them confused...

comment:8 in reply to: ↑ 7 Changed 5 years ago by datallah

Replying to andyross:

The design assumption above seems wrong in some cases. I'm using pidgin (on linux) with the pidgin-sipe plugin using Windows AD/kerberos authentication. If I'm not authenticated on the network, this will obviously fail. But that failure (being "fatal", apparently) will now *persist* once I reconnect.

This is hugely annoying. I need to manually reconnect every morning when I get to work. And of course I forget and people can't find me.

Basically: a failure to authenticate ("Client couldn't do it for some reason") is not the same thing as an affirmative failure to authorize ("Server says: this user is not allowed"), and it seems like pidgin gets them confused...

The protocol plugin gets to decide if a particular error should be fatal or not (so pidgin-sipe could change the behavior that you don't like). Based on the backlog, this ticket is actually about a somewhat different thing (despite what the first comment says about "Not-Authorized").

comment:9 Changed 3 years ago by MintPaw

This is still a huge problem, I can't go around to each protocol/plugin to redefine what errors are fatal and non-fatal. Every time wifi cuts out Pidgin is essentially unusable and knowing it won't reconnect half my services I've simply written a script to kill and relaunch it. To be a competent multi-client messenger we need a way to force auto-reconnect.

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!