[maemo-developers] af-sb-init.sh start error

[From: daniel wilms]

Hi,

it seems, that you have already some processes running. So please try 
the following:

1) stop the framework:
    af-sb-init.sh stop

2) stop all the old processes:
    sb-conf killall

And then try again, and please tell us if then still errors are coming up.

Cheers Daniel
   



ext Dream Soul wrote:
> Hi,
>
> please help, I am try to run maemo-sdk beta2:
>
> [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.
> Sapwood image server is already running, doing nothing
> Starting hildon-desktop
> Xlib:  extension "Generic Event Extension" missing on display ":2.0".
> Xlib:  extension "Generic Event Extension" missing on display ":2.0".
> Xlib:  extension "Generic Event Extension" missing on display ":2.0".
> Xlib:  extension "Generic Event Extension" missing on display ":2.0".
> Xlib:  extension "Generic Event Extension" missing on display ":2.0".
> Xlib:  extension "Generic Event Extension" missing on display ":2.0".
> Xlib:  extension "Generic Event Extension" missing on display ":2.0".
> Xlib:  extension "Generic Event Extension" missing on display ":2.0".
> Xlib:  extension "Generic Event Extension" missing on display ":2.0".
> Xlib:  extension "Generic Event Extension" missing on display ":2.0".
> Keyboard is already running, doing nothing
> Xlib:  extension "Generic Event Extension" missing on display ":2.0".
> [sbox-FREMANTLE_X86: ~] > hildon-desktop[12384]: GLIB WARNING ** 
> default - Could not open D-Bus session/system bus connection.
> process 12386: 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 12386: arguments to dbus_message_get_args() were incorrect, 
> assertion "message != NULL" failed in file dbus-message.c line 1666.
> This is normally a bug in some application using the D-Bus library.
> hildon-home[12386]: GLIB WARNING ** GVFS-RemoteVolumeMonitor - Error 
> parsing args in reply for IsSupported(): (null): (null)
> process 12386: 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 12386: 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 12386: 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[12386]: GLIB WARNING ** libgnomevfs - Failed to activate 
> daemon: (null)
> process 12386: 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 12386: 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[12386]: GLIB ERROR ** default - Not enough memory to set 
> up DBusConnection for use with GLib
> aborting...
>
> [sbox-FREMANTLE_X86: ~] >
>