Created attachment 20025 [details] backtrace Sometimes connection errors seem to fire for PurpleAccounts that no longer correspond to a HazeConnection. In the attached backtrace, the HazeConnection in question is not actually the one we wanted; it was finalized ages ago. It seems that this might be caused by a combination of: * purple_account_new secretly being purple_account_ensure * PurpleAccounts being destroyed in idle_disconnected_cb not in haze_connection_finalize * crack. There was lots of (haze:30884): tp-glib-DEBUG: tp_base_connection_manager_request_connection: failed: Error acquiring bus name org.freedesktop.Telepathy.Connection.haze.msn.vector2uk_40hotmail_2ecom: Connection manager already has a connection to this account in the debug scrollback which suggests that accounts are disconnecting but not being finalized properly.
I think I know what's happening here, and I have a test case.
Fixed in a branch, awaiting review: http://git.collabora.co.uk/?p=user/wjt/telepathy-haze;a=shortlog;h=refs/heads/crash-on-reconnect
Fixed in 0.3.0.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.