*** Original post on bio 228 at 2009-08-28 23:18:00 UTC *** Steps to reproduce: - Add an account with no password, autologin enabled - restart instantbird, the account has no error, nor it is connected. - make instantbird crash - autologin disabling at startup (see Bug 953584 (bio 137)) triggers even if Instantbird crashes a few hours after autologin was performed Issue coming from libpurple that simply does nothing when an account has no password. Libpurple should send an error message in those cases.
*** Original post on bio 228 at 2010-01-17 00:14:31 UTC *** Shouldn't we mark the account has having an error, even before there is any connection attempt on it?
*** Original post on bio 228 at 2010-03-04 22:55:30 UTC *** I think this issue is fixed by my patch for bug 953730 (bio 287).