<div class="gmail_quote">Hi Daniil,<br><br>Thanks for your response.I have been debugging my ConnectionManager and Connection code for a while with no success. <br><div><br></div><div>This is the sequence of events that happen when I execute the DBus Command manually(or when mission control automatically attempts to connect to my connection manager):<br>
<br>dbus-send --type=method_call --print-reply --dest=org.freedesktop.Telepathy.AccountManager /org/freedesktop/Telepathy/Account/vicar/tel/vicar0 org.<br>freedesktop.Telepathy.Account.Reconnect<br><br></div><div>1) The telepathy client (mission control in this case) calls ConnectionManager::RequestConnection() method.</div>
<div>2) My connection manager creates a connection object, registers the object on D-Bus, Emits NewConnection signal</div>
<div>3) Mission control calls Connection::HoldHandles()<br></div><div>4) Mission control calls Connection::Connect()</div><div>5) My connection changes the status to Connected and emits StatusChanged signal.</div><div>6) Mission control emits AccountPropertyChanged signal with connection object path set to "/org/freedesktop/Telepathy/Connection/vicar/tel/vicar" and ConnectionStatus set to 0 (Connected).</div>
<div>7) Immediately after this I see in the dbus-monitor output that
mission control emits AccountPropertyChanged sign with connection object
path set to "/" and ConnectionStatus set to 2 (Disconnected). </div><div>
<br>After step 6, the Connection object status remains as Connected (set in my code) but client-side account status changes to Disconnected [1]. Apparently, something is happening between
steps 6 and 7 that causes mission control (client) to disconnect from the Connection.