The issue here is that after installing telepathy-mission-control the glib 
schemas need to be recompiled.
One can do that himself (as root) using something like

/usr/bin/glib-compile-schemas /usr/share/glib-2.0/schemas

(Not sure about the exact paths on ubuntu)

Ideally that should be handled by the package though.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to telepathy-mission-control-5 in Ubuntu.
https://bugs.launchpad.net/bugs/894655

Title:
  Settings schema 'im.telepathy.MissionControl.FromEmpathy' is not
  installed

Status in “telepathy-mission-control-5” package in Ubuntu:
  Confirmed

Bug description:
  package version: 1:5.10.1-0ubuntu1 (i386)
  release: Ubuntu 12.04

  When Empathy starts, it displays an error dialog stating:

  +----
  |  There was an error while trying to connect to
  |  the Telepathy Account Manager. The error was:
  |  Message did not receive a reply (timeout by message bus)
  +----

  A similar error appears when I try to start Empathy from a terminal
  window:

  +----
  |  folks-WARNING **: Error preparing Backend 'telepathy':
  |  Message did not receive a reply (timeout by message bus)
  +----

  I notice that two files in /usr/share/dbus-1/service:
    * org.freedesktop.Telepathy.AccountManager.service
    * org.freedesktop.Telepathy.MissionControl5.service
  both contain the following exec call:
    Exec=/usr/lib/telepathy/mission-control-5

  When I try to execute that directly from a terminal window, I receive
  the following error:

  +----
  |  mcd-WARNING **: Could not add client names match rule: Key 'arg0namespace'
  |  in match rule contains junk after argument number. Only 'path' is
  |  optionally valid ('arg0path' for example).
  |
  |  GLib-GIO-ERROR **: Settings schema
  | 'im.telepathy.MissionControl.FromEmpathy' is not installed
  |
  |  Trace/breakpoint trap
  +----

  It appears that Empathy is unable to start Telepathy Mission Control.
  Googling has revealed similar reports, but mostly on Fedora,
  referencing an incorrect SELinux security context. I'm guessing that
  doesn't apply here.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/894655/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to