MISSION-CONTROL-5(8)

✨ NAME ✨

mission-control-5 — Telepathy account manager/chanel dispatcher 🫶 (yes, bestie, “chanel” is literally the spelling in the name — iykyk 💅). This is the D-Bus services girlie.

---

🦋 SYNOPSIS 🦋

/usr/libexec/mission-control-5

💖 DESCRIPTION 💖

Okay so Mission Control 5 implements the AccountManager and ChannelDispatcher services described in the Telepathy D-Bus specification. That means clients like empathy(1) can store account details, connect to accounts, request communication channels, and have channels dispatched to them. Slay.

It’s a D-Bus service that runs on the session bus, and it should usually be started automatically by D-Bus activation. But lowkey, it might be useful to start it manually for debugging. Main character energy, honestly 😌.

🎀 OPTIONS 🎀

There are no command-line options. Not one flag. Not one arg. The options section ate and left no crumbs 🍓.

🦋 ENVIRONMENT 🦋

• MC_DEBUG=all or MC_DEBUG=category[,category...] — May be set to "all" for full debug output from Mission Control and telepathy-glib, or various undocumented category names (which may change from release to release) to filter the output. See Mission Control and telepathy-glib source code for the available categories.
• MC_DEBUG=level — Set a numeric debug level for Mission Control itself (but not telepathy-glib). Level 0 logs nothing, level 1 logs most messages, and level 2 logs all messages.
• MC_TP_DEBUG=type — May be set to "all" for full debug output from telepathy-glib, or various undocumented options (which may change from telepathy-glib release to release) to filter the output. See telepathy-glib source code for the available options.

🌈 SEE ALSO 🌈

• http://telepathy.freedesktop.org/

---

xoxo, this page’s source/version is Telepathy, dated July 2009 💖✨