[Telepathy] [Bug 18058] New: no good way to clean up lost-in-space connections you' d like to recreate

[bugzilla-daemon at freedesktop.org]

http://bugs.freedesktop.org/show_bug.cgi?id=18058

           Summary: no good way to clean up lost-in-space connections you'd
                    like to recreate
           Product: Telepathy
           Version: unspecified
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: telepathy-spec
        AssignedTo: telepathy at lists.freedesktop.org
        ReportedBy: will.thompson at collabora.co.uk


When you call RequestConnection for a connection that already exists,
telepathy-glib-based CMs return NotAvailable. There's no way to get rid of the
existing connection so that you can make a new one. This leads to the following
situation:

1. A Telepathy client makes a Connection, never calls Connect() on it, and
quits.
2. Empathy tries to connect to that account, but MC can't make a connection.
3. No IM for you!

This situation arises in practice because something (MC?) makes connections and
forgets about them.

Currently, you can work around this by setting Empathy to offline and then
online again, due to MC4's "kill everything on startup" behaviour. But in
general, you have to either log out and in again, or know how to drive
Telepathy-Inspector.

Discussion on #telepathy lead to a proposed solution:

1. Add a specific error which RequestConnection returns if the connection
already exists.
2. Add a method to ConnectionManager which kills off any clashing connections
and returns you a new one.
3. UIs could then react to 1. by offering a button to call 2.


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.