[Bug 894655] [NEW] Settings schema 'im.telepathy.MissionControl.FromEmpathy' is not installed

[Steve Riley]

Public bug reported:

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.

** Affects: telepathy-mission-control-5 (Ubuntu)
     Importance: Undecided
         Status: New

** Description changed:

  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:
+ |  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:
+ 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
+   * org.freedesktop.Telepathy.AccountManager.service
+   * org.freedesktop.Telepathy.MissionControl5.service
  both contain the following exec call:
-   Exec=/usr/lib/telepathy/mission-control-5
+   Exec=/usr/lib/telepathy/mission-control-5
  
- 
- When I try to execute that directly from a terminal window, I receive the following error:
+ 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.
+ 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.

** Description changed:

  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)
+ |  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).
+ |  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
+ |  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.

** Description changed:

  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
+ |  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.

-- 
You received this bug notification because you are a member of
Telepathy, 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

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