Bug 25423 - don't allow the real MC to be service-activated while we test the development MC
Summary: don't allow the real MC to be service-activated while we test the development MC
Status: RESOLVED INVALID
Alias: None
Product: Telepathy
Classification: Unclassified
Component: mission-control (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Telepathy bugs list
QA Contact: Telepathy bugs list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-12-03 13:52 UTC by Simon McVittie
Modified: 2010-03-01 07:25 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments

Description Simon McVittie 2009-12-03 13:52:12 UTC 
+++ This bug was initially created as a clone of Bug #25421 +++

<http://git.collabora.co.uk/?p=user/smcv/telepathy-qt4-smcv.git;a=shortlog;h=refs/heads/buildsys> has:

* a bugfix for distcheck, which would sometimes fail because Mission Control gets service-activated instead of the fake AccountManager (if you have, e.g., telepathy-mission-control-5 >= 5.3.2-2 on Debian)

[... and some other stuff]

This bugfix, derived from one David Laban provided for telepathy-glib, should also go into MC if needed (it might become relevant there if the MC under test crashes).
Comment 1 Simon McVittie 2010-03-01 07:25:22 UTC 
In MC this seems to be right already.

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.