[maemo-developers] unable to run mission control server

[From: Mohammed Taqi]

Hi all,

I am trying to rum the telepathy-mission control application in my i386
Diablo target.

I am getting the following dbus error

 [sbox-DIABLO_X86: ~/telepathy/telepathy-mission-control-4.61/server] >
./mission-control
Failed to open connection to bus: Failed to execute dbus-launch to
autolaunch D-Bus sessionlt-mission-control[28663]: GLIB WARNING **
GLib-GObject - invalid (NULL) pointer instance
lt-mission-control[28663]: GLIB CRITICAL ** GLib-GObject -
g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
lt-mission-control[28663]: GLIB WARNING ** GLib-GObject - invalid (NULL)
pointer instance
lt-mission-control[28663]: GLIB CRITICAL ** GLib-GObject -
g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
lt-mission-control[28663]: GLIB WARNING ** GLib-GObject - invalid (NULL)
pointer instance
lt-mission-control[28663]: GLIB CRITICAL ** GLib-GObject -
g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
lt-mission-control[28663]: GLIB WARNING ** GLib-GObject - invalid (NULL)
pointer instance
lt-mission-control[28663]: GLIB CRITICAL ** GLib-GObject -
g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
lt-mission-control[28663]: GLIB WARNING ** GLib-GObject - invalid (NULL)
pointer instance
lt-mission-control[28663]: GLIB CRITICAL ** GLib-GObject -
g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
lt-mission-control[28663]: GLIB WARNING ** GLib-GObject - invalid (NULL)
pointer instance
lt-mission-control[28663]: GLIB CRITICAL ** GLib-GObject -
g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
lt-mission-control[28663]: GLIB WARNING ** GLib-GObject - invalid (NULL)
pointer instance
lt-mission-control[28663]: GLIB CRITICAL ** GLib-GObject -
g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
lt-mission-control[28663]: GLIB WARNING ** GLib-GObject - invalid (NULL)
pointer instance
lt-mission-control[28663]: GLIB CRITICAL ** GLib-GObject -
g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
lt-mission-control[28663]: GLIB WARNING ** GLib-GObject - invalid (NULL)
pointer instance
lt-mission-control[28663]: GLIB CRITICAL ** GLib-GObject -
g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
lt-mission-control[28663]: GLIB WARNING ** GLib-GObject - invalid (NULL)
pointer instance
lt-mission-control[28663]: GLIB CRITICAL ** GLib-GObject -
g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
lt-mission-control[28663]: GLIB DEBUG default - Requesting MC dbus service
lt-mission-control[28663]: GLIB CRITICAL ** default -
dbus_g_connection_get_connection: assertion `gconnection' failed
process 28663: arguments to dbus_bus_request_name() were incorrect,
assertion "connection != NULL" failed in file dbus-bus.c line 980.
This is normally a bug in some application using the D-Bus library.
  D-Bus not built with -rdynamic so unable to print a backtrace
Aborted (core dumped)


Can I run mission-control server standalone?
Do I need to run any other application or change any dbus related
configuration, Plz. let me know.

Dbus daemon is already running in the scratchbox.

Thanks &
Regards
Taqi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.maemo.org/pipermail/maemo-developers/attachments/20090605/b968c674/attachment.htm