[Telepathy] issue in launching mission control

Sjoerd Simons sjoerd.simons at collabora.co.uk
Tue Aug 31 09:34:04 PDT 2010


On Tue, 2010-08-31 at 19:20 +0530, ved kpl wrote:
> Hi,
> 
> I built telepathy out of the box, onto an embedded platform.
> When I try to launch the mission-control, i get the following error.
> 
> # /usr/local/libexec/mission-control-5 &
> # Failed to open connection to bus: dbus-launch failed to autolaunch
> D-Bus session: EOF in dbus-launch reading address from bus daemon

All the issues below stem from this problem right here, you're dbus
daemon is failing to autolaunch. Try launch a bus first and then run the
various components (for example dbus-launch /bin/sh)

Note that there is no need start mission-control-5 by hand, on a
properly configured system it will be automatically launched by dbus

> (process:2110): GLib-GObject-WARNING **: invalid (NULL) pointer instance
> 
> (process:2110): GLib-GObject-CRITICAL **: g_signal_connect_data:
> assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
> 
> (process:2110): mcd-CRITICAL **: mcd_mission_connect: assertion
> `MCD_IS_MISSION (mission)' failed
> [sys_assert] START of sighandler
> [sys_assert]this thread is main thread. pid=2110
> local time 2010 8 31 13:34:49
> [sys-assert] exename = mission-control-5
> [sys-assert]Previous umask = 0022
> [sys assert] exe path = /usr/local/libexec/mission-control-5
> [sys-assert] start print_node_to_file
> sighandler = 0x40029a10, g_sig_oldact[i] = (nil)
> [sys_assert] END of sighandler
> 
> [1]+  Segmentation fault (core dumped) /usr/local/libexec/mission-control-5
> 
> 
> What could be the issue?
> 
> Thanks,
> Vikram
> _______________________________________________
> telepathy mailing list
> telepathy at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/telepathy


-- 
Sjoerd Simons <sjoerd.simons at collabora.co.uk>
Collabora Ltd.


More information about the telepathy mailing list