Thread: Empty SDK UI
View Single Post
Posts: 25 | Thanked: 8 times | Joined on Dec 2009 @ Caracas/Venezuela
#1
Hello, i recently installed the SDK on a virtual machine. I managed to run the UI using Xephir but it seems to be empty..

The users interface seems to work fine, but without any program installed.
I only can acces "Settings" and "App manager". After adding the different repositorys in the virtual App manager, i get acces to all the applications as in the real device, but failing in the installation.

this is what i get in the terminal
^[[A^[[A[sbox-FREMANTLE_X86: ~] > export DISPLAY=:2
[sbox-FREMANTLE_X86: ~] > af-sb-init.sh start
Note: For remote X connections DISPLAY should contain hostname!
Sample files present.
DBUS system bus is already running, doing nothing
D-BUS session bus daemon is already running, doing nothing
Starting Maemo Launcher: maemo-launcher start failed.
Starting Sapwood image server
Starting hildon-desktop
maemo-launcher: invoking '/usr/bin/hildon-desktop.launch'
process 28039: arguments to dbus_connection_send_with_reply_and_block() were incorrect, assertion "connection != NULL" failed in file dbus-connection.c line 3298.
This is normally a bug in some application using the D-Bus library.
process 28039: arguments to dbus_message_get_args() were incorrect, assertion "message != NULL" failed in file dbus-message.c line 1670.
This is normally a bug in some application using the D-Bus library.
hildon-desktop[28039]: GLIB WARNING ** GVFS-RemoteVolumeMonitor - Error parsing args in reply for IsSupported(): (null): (null)
maemo-launcher: opening of /usr/bin/hildon-desktop.launch took 3326 usec
maemo-launcher: invoking '/usr/bin/hildon-status-menu.launch'
maemo-launcher: invoking '/usr/bin/hildon-home.launch'
process 28041: arguments to dbus_connection_send_with_reply_and_block() were incorrect, assertion "connection != NULL" failed in file dbus-connection.c line 3298.
This is normally a bug in some application using the D-Bus library.
process 28041: arguments to dbus_message_get_args() were incorrect, assertion "message != NULL" failed in file dbus-message.c line 1670.
This is normally a bug in some application using the D-Bus library.
hildon-status-menu[28041]: GLIB WARNING ** GVFS-RemoteVolumeMonitor - Error parsing args in reply for IsSupported(): (null): (null)
maemo-launcher: opening of /usr/bin/hildon-status-menu.launch took 1006 usec
process 28043: arguments to dbus_connection_send_with_reply_and_block() were incorrect, assertion "connection != NULL" failed in file dbus-connection.c line 3298.
This is normally a bug in some application using the D-Bus library.
process 28043: arguments to dbus_message_get_args() were incorrect, assertion "message != NULL" failed in file dbus-message.c line 1670.
This is normally a bug in some application using the D-Bus library.
hildon-home[28043]: GLIB WARNING ** GVFS-RemoteVolumeMonitor - Error parsing args in reply for IsSupported(): (null): (null)
/usr/bin/hildon-status-menu: console is quiet, define DEBUG_OUTPUT to prevent this.
maemo-launcher: opening of /usr/bin/hildon-home.launch took 38368 usec
process 28043: arguments to dbus_connection_send() were incorrect, assertion "connection != NULL" failed in file dbus-connection.c line 3099.
This is normally a bug in some application using the D-Bus library.
process 28043: arguments to dbus_connection_send_with_reply_and_block() were incorrect, assertion "connection != NULL" failed in file dbus-connection.c line 3298.
This is normally a bug in some application using the D-Bus library.
process 28043: arguments to dbus_bus_start_service_by_name() were incorrect, assertion "connection != NULL" failed in file dbus-bus.c line 1313.
This is normally a bug in some application using the D-Bus library.
hildon-home[28043]: GLIB WARNING ** libgnomevfs - Failed to activate daemon: (null)
process 28043: arguments to dbus_connection_get_data() were incorrect, assertion "connection != NULL" failed in file dbus-connection.c line 5757.
This is normally a bug in some application using the D-Bus library.
process 28043: arguments to dbus_connection_set_data() were incorrect, assertion "connection != NULL" failed in file dbus-connection.c line 5721.
This is normally a bug in some application using the D-Bus library.
hildon-home[28043]: GLIB ERROR ** default - Not enough memory to set up DBusConnection for use with GLib
aborting...
maemo-launcher: child (pid=28043) terminated due to signal=6
/usr/bin/af-sb-init.sh: line 52: 28042 Aborted /usr/bin/hildon-home
Starting Keyboard
hildon-desktop[28039]: GLIB WARNING ** default - Could not open D-Bus session/system bus connection.
Initializing trackerd...
trackerd[28059]: GLIB DEBUG Tracker - Checking XDG_DATA_HOME is writable and exists
maemo-launcher: invoking '/usr/bin/hildon-input-method.launch'
process 28058: arguments to dbus_connection_send_with_reply_and_block() were incorrect, assertion "connection != NULL" failed in file dbus-connection.c line 3298.
This is normally a bug in some application using the D-Bus library.
process 28058: arguments to dbus_message_get_args() were incorrect, assertion "message != NULL" failed in file dbus-message.c line 1670.
This is normally a bug in some application using the D-Bus library.
hildon-input-method[28058]: GLIB WARNING ** GVFS-RemoteVolumeMonitor - Error parsing args in reply for IsSupported(): (null): (null)
maemo-launcher: opening of /usr/bin/hildon-input-method.launch took 1425 usec
trackerd[28059]: GLIB MESSAGE Tracker - XDG_DATA_HOME set to '/home/maemo/.local/share'
trackerd[28059]: GLIB DEBUG Tracker - Path is OK
trackerd[28059]: GLIB MESSAGE Tracker - Setting IO priority
trackerd[28059]: GLIB MESSAGE Tracker - Setting up stopword list for language code:'en'
trackerd[28059]: GLIB MESSAGE Tracker - Tracker couldn't read stopword file:'/usr/share/tracker/languages/stopwords.en', Failed to open file '/usr/share/tracker/languages/stopwords.en': open() failed: No such file or directory
trackerd[28059]: GLIB MESSAGE Tracker - Setting up stemmer for language code:'en'
process 28061: arguments to dbus_connection_get_data() were incorrect, assertion "connection != NULL" failed in file dbus-connection.c line 5757.
This is normally a bug in some application using the D-Bus library.
process 28061: arguments to dbus_connection_set_data() were incorrect, assertion "connection != NULL" failed in file dbus-connection.c line 5721.
This is normally a bug in some application using the D-Bus library.
mafw-dbus-wrapper[28061]: GLIB ERROR ** default - Not enough memory to set up DBusConnection for use with GLib
aborting...
process 28062: arguments to dbus_connection_get_data() were incorrect, assertion "connection != NULL" failed in file dbus-connection.c line 5757.
This is normally a bug in some application using the D-Bus library.
process 28062: arguments to dbus_connection_set_data() were incorrect, assertion "connection != NULL" failed in file dbus-connection.c line 5721.
This is normally a bug in some application using the D-Bus library.
/usr/bin/af-sb-init.sh: line 303: 28061 Aborted (core dumped) mafw-dbus-wrapper /usr/lib/mafw-plugin/mafw-tracker-source.so
mafw-dbus-wrapper[28062]: GLIB ERROR ** default - Not enough memory to set up DBusConnection for use with GLib
aborting...
maemo-launcher: child (pid=28041) terminated due to signal=11
hildon-input-method[28058]: GLIB WARNING ** default - Could not initialize osso from hildon-input-method
maemo-launcher: child (pid=28039) terminated due to signal=11
hildon-input-method[28058]: GLIB WARNING ** default - Could not register the osso_hw_set_event_cb
hildon-input-method[28058]: GLIB MESSAGE default - ui up and running