| 2011-11-25 07:58:41 |
z |
bug |
|
|
added bug |
| 2011-11-25 07:59:26 |
z |
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. |
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. |
|
| 2011-11-25 08:00:16 |
z |
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. |
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. |
|
| 2011-11-25 08:00:49 |
z |
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. |
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. |
|
| 2011-11-30 20:40:18 |
Launchpad Janitor |
telepathy-mission-control-5 (Ubuntu): status |
New |
Confirmed |
|
| 2011-12-07 19:42:22 |
Heimen Stoffels |
bug |
|
|
added subscriber Vistaus |
| 2011-12-10 22:17:11 |
Effe Erre |
bug |
|
|
added subscriber Francesco Reinerio |
| 2012-01-19 07:29:39 |
Yoan Blanc |
bug |
|
|
added subscriber Yoan Blanc |
| 2012-02-11 23:46:09 |
Paul Jaros |
bug |
|
|
added subscriber Paul Jaros |
| 2012-05-21 22:52:26 |
Tom |
bug |
|
|
added subscriber Tom |
| 2015-12-14 21:22:54 |
z |
removed subscriber Steve Riley |
|
|
|
