Bug 35670

Summary: Sometimes leaks freshly-created connections.
Product: Telepathy Reporter: Will Thompson <will>
Component: mission-controlAssignee: Telepathy bugs list <telepathy-bugs>
Status: RESOLVED MOVED QA Contact: Telepathy bugs list <telepathy-bugs>
Severity: normal    
Priority: medium    
Version: unspecified   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:

Description Will Thompson 2011-03-25 09:19:37 UTC 
The illustrious Robert McQueen reported that he had a Gabble connection kicking around that Mission Control didn't know about, preventing him from connecting to that account. Some investigation revealed that it was in the “NEW” state telepathy-glib uses internally to mean “no-one called Connect() yet”.

This suggests that something went wrong in the gap between MC calling RequestConnection() and calling Connect().

One hypothesis is that MC crashed while introspecting the connection before calling Connect() on it, and the MC crash recovery code didn't shoot the connection in the head, but nor did it pick up where it left off.
Comment 1 GitLab Migration User 2019-12-03 19:35:12 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/telepathy/telepathy-mission-control/issues/39.

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.