[Bug 53220] New: when racing to activate o.fd.T.MC5 and o.fd.T.AM, one or both fail

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=53220

             Bug #: 53220
           Summary: when racing to activate o.fd.T.MC5 and o.fd.T.AM, one
                    or both fail
    Classification: Unclassified
           Product: Telepathy
           Version: unspecified
          Platform: Other
        OS/Version: All
            Status: ASSIGNED
          Keywords: patch
          Severity: normal
          Priority: medium
         Component: mission-control
        AssignedTo: simon.mcvittie at collabora.co.uk
        ReportedBy: simon.mcvittie at collabora.co.uk
         QAContact: telepathy-bugs at lists.freedesktop.org


Created attachment 65246
  --> https://bugs.freedesktop.org/attachment.cgi?id=65246
Avoid race between Mission Control's two names by having one  wait for the
other

If you do:

dbus-send --dest=org.freedesktop.Telepathy.MissionControl5 \
  --type=method_call --print-reply / org.freedesktop.DBus.Peer.Ping & \
dbus-send --dest=org.freedesktop.Telepathy.AccountManager \
--type=method_call --print-reply / org.freedesktop.DBus.Peer.Ping

then one or both of the calls will fail because the executable claims
one of its bus names, but can't get the other, and exits 1.

By making one wait for the other, we get the desired behaviour.
I've made activating MissionControl5 wait for AccountManager because
in MC's current implementation AccountManager is taken last (Bug #24000).

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