[Pidgin] #168: Handle "you have logged in somewhere else" errors smarter

[Pidgin]

#168: Handle "you have logged in somewhere else" errors smarter
---------------------------+------------------------------------------------
  Reporter:  seanegan      |       Owner:  rlaager
      Type:  defect        |      Status:  new    
  Priority:  minor         |   Milestone:  2.2.3  
 Component:  pidgin (gtk)  |     Version:  2.0    
Resolution:                |    Keywords:         
   Pending:  0             |  
---------------------------+------------------------------------------------
Comment (by resiak):

 The only complaint mentioned in this bug that is not fixed in the
 .disconnectreasons branch is that, because the accounts are still
 disabled, restarting Pidgin does not make them reconnect (although the
 notification is not recreated when you restart).  There are various ways
 this could be fixed:

 1. Don't disable the accounts; when you change status, they will be
 reconnected.
 2. Don't disable the accounts; have some special-casing in the status code
 to not connect an account for which `_get_current_error()->type ==
 NAME_IN_USE`.
 3. Don't disable the accounts; implement some kind of status layering
 system, and add the account to a "do not reconnect" layer.
 4. Disable the accounts; save an account's current error on quit, restore
 it on load (possibly only if it's this error?).
 5. Disable the accounts; rig up an account property that makes Pidgin re-
 enable it next time you start it.
 6. Don't fix anything; this works well enough.

 I'm personally good with 6.  :-)

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