[Pidgin] #7323: Pidgin does not reconnect after Networkmanager sent StateChange

[Pidgin]

#7323: Pidgin does not reconnect after Networkmanager sent StateChange
--------------------------------------+-------------------------------------
 Reporter:  aneiser                   |        Owner:           
     Type:  patch                     |       Status:  closed   
Milestone:  2.5.3                     |    Component:  libpurple
  Version:  2.5.2                     |   Resolution:  fixed    
 Keywords:  networkmanager reconnect  |  
--------------------------------------+-------------------------------------

Comment(by rlaager):

 VuDu: Does Pidgin connect at all, ever? If not, that's got nothing to do
 with this. If it does, then what do you mean about it saying it can't
 connect?

 aneiser: I don't know how we're supposed to know if NetworkManager has
 brought up a VPN. I'm not sure what changed in 0.7... In my opinion, users
 should be able to specify that a VPN come up automatically (ideally based
 on certain conditions). If that's the case, and the VPN is setup to be the
 default route, then NM should treat the network as offline until the VPN
 comes up. If this happened, everything would just work. (It would fail in
 the case of a VPN that only advertises specific routes and one of those
 routes being for your IM server, but I'm not too worried about that. You
 could use SSL instead, so the IM server doesn't have to be accessed
 through the VPN.)

-- 
Ticket URL: <http://developer.pidgin.im/ticket/7323#comment:12>
Pidgin <http://pidgin.im>
Pidgin