Bug 24000

Summary: o.fd.T.MC5 name should not appear on dbus before o.fd.T.CD and o.d.fd.T.AM are ready
Product: Telepathy Reporter: George Goldberg <grundleborg>
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 George Goldberg 2009-09-17 08:59:23 UTC
In order to get DBus to autostart MC5, you prod it on org.freedesktop.Telepathy.MissionControl5. However, this should not appear on MC startup before o.fd.T.ChannelDispatcher and o.fd.T.AccountManager are already ready for use.
Comment 1 Simon McVittie 2012-10-09 14:23:21 UTC
If this is fixed/changed, be aware that the activation setup will need to change (see commit ad4b94ec and Bug #53220).
Comment 2 Simon McVittie 2014-01-29 14:20:06 UTC
Also, we really do need to take *a* name early in initialization, as a mutex that will protect our account migration process from other copies of MC running in parallel. If we don't take the "main" name until later, then that name can't be our mutex.
Comment 3 GitLab Migration User 2019-12-03 19:33:29 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/9.

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.