Advertisement
Guest User

Untitled

a guest
Apr 1st, 2010
255
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 12.66 KB | None | 0 0
  1. [sbox-FREMANTLE_X86: ~] > af-sb-init.sh start
  2. Note: For remote X connections DISPLAY should contain hostname!
  3. Sample files present.
  4. DBUS system bus is already running, doing nothing
  5. D-BUS session bus daemon is already running, doing nothing
  6. Starting Maemo Launcher: maemo-launcher start failed.
  7. Starting Sapwood image server
  8. Starting hildon-desktop
  9. maemo-launcher: invoking '/usr/bin/hildon-desktop.launch'
  10. process 4043: arguments to dbus_connection_send_with_reply_and_block() were incorrect, assertion "connection != NULL" failed in file dbus-connection.c line 3298.
  11. This is normally a bug in some application using the D-Bus library.
  12. maemo-launcher: invoking '/usr/bin/hildon-status-menu.launch'
  13. process 4043: arguments to dbus_message_get_args() were incorrect, assertion "message != NULL" failed in file dbus-message.c line 1670.
  14. This is normally a bug in some application using the D-Bus library.
  15. hildon-desktop[4043]: GLIB WARNING ** GVFS-RemoteVolumeMonitor - Error parsing args in reply for IsSupported(): (null): (null)
  16. process 4047: arguments to dbus_connection_send_with_reply_and_block() were incorrect, assertion "connection != NULL" failed in file dbus-connection.c line 3298.
  17. This is normally a bug in some application using the D-Bus library.
  18. process 4047: arguments to dbus_message_get_args() were incorrect, assertion "message != NULL" failed in file dbus-message.c line 1670.
  19. This is normally a bug in some application using the D-Bus library.
  20. hildon-status-menu[4047]: GLIB WARNING ** GVFS-RemoteVolumeMonitor - Error parsing args in reply for IsSupported(): (null): (null)
  21. maemo-launcher: opening of /usr/bin/hildon-desktop.launch took 1723 usec
  22. maemo-launcher: opening of /usr/bin/hildon-status-menu.launch took 677 usec
  23. /usr/bin/hildon-status-menu: console is quiet, define DEBUG_OUTPUT to prevent this.
  24. maemo-launcher: invoking '/usr/bin/hildon-home.launch'
  25. process 4050: arguments to dbus_connection_send_with_reply_and_block() were incorrect, assertion "connection != NULL" failed in file dbus-connection.c line 3298.
  26. This is normally a bug in some application using the D-Bus library.
  27. process 4050: arguments to dbus_message_get_args() were incorrect, assertion "message != NULL" failed in file dbus-message.c line 1670.
  28. This is normally a bug in some application using the D-Bus library.
  29. hildon-home[4050]: GLIB WARNING ** GVFS-RemoteVolumeMonitor - Error parsing args in reply for IsSupported(): (null): (null)
  30. maemo-launcher: opening of /usr/bin/hildon-home.launch took 1202 usec
  31. process 4050: arguments to dbus_connection_send() were incorrect, assertion "connection != NULL" failed in file dbus-connection.c line 3099.
  32. This is normally a bug in some application using the D-Bus library.
  33. process 4050: arguments to dbus_connection_send_with_reply_and_block() were incorrect, assertion "connection != NULL" failed in file dbus-connection.c line 3298.
  34. This is normally a bug in some application using the D-Bus library.
  35. process 4050: arguments to dbus_bus_start_service_by_name() were incorrect, assertion "connection != NULL" failed in file dbus-bus.c line 1313.
  36. This is normally a bug in some application using the D-Bus library.
  37. hildon-home[4050]: GLIB WARNING ** libgnomevfs - Failed to activate daemon: (null)
  38. process 4050: arguments to dbus_connection_get_data() were incorrect, assertion "connection != NULL" failed in file dbus-connection.c line 5757.
  39. This is normally a bug in some application using the D-Bus library.
  40. process 4050: arguments to dbus_connection_set_data() were incorrect, assertion "connection != NULL" failed in file dbus-connection.c line 5721.
  41. This is normally a bug in some application using the D-Bus library.
  42. hildon-home[4050]: GLIB ERROR ** default - Not enough memory to set up DBusConnection for use with GLib
  43. aborting...
  44. Starting Keyboard
  45. process 4067: arguments to dbus_connection_get_data() were incorrect, assertion "connection != NULL" failed in file dbus-connection.c line 5757.
  46. This is normally a bug in some application using the D-Bus library.
  47. process 4067: arguments to dbus_connection_set_data() were incorrect, assertion "connection != NULL" failed in file dbus-connection.c line 5721.
  48. This is normally a bug in some application using the D-Bus library.
  49. mafw-dbus-wrapper[4067]: GLIB ERROR ** default - Not enough memory to set up DBusConnection for use with GLib
  50. aborting...
  51. process 4066: arguments to dbus_connection_get_data() were incorrect, assertion "connection != NULL" failed in file dbus-connection.c line 5757.
  52. This is normally a bug in some application using the D-Bus library.
  53. process 4066: arguments to dbus_connection_set_data() were incorrect, assertion "connection != NULL" failed in file dbus-connection.c line 5721.
  54. This is normally a bug in some application using the D-Bus library.
  55. mafw-dbus-wrapper[4066]: GLIB ERROR ** default - Not enough memory to set up DBusConnection for use with GLib
  56. aborting...
  57. maemo-launcher: child (pid=4050) terminated due to signal=6
  58. Initializing trackerd...
  59. trackerd[4064]: GLIB DEBUG Tracker - Checking XDG_DATA_HOME is writable and exists
  60. trackerd[4064]: GLIB MESSAGE Tracker - XDG_DATA_HOME set to '/home/balazsbela/.local/share'
  61. trackerd[4064]: GLIB DEBUG Tracker - Path is OK
  62. trackerd[4064]: GLIB MESSAGE Tracker - Setting IO priority
  63. trackerd[4064]: GLIB MESSAGE Tracker - Setting up stopword list for language code:'en'
  64. trackerd[4064]: 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
  65. trackerd[4064]: GLIB MESSAGE Tracker - Setting up stemmer for language code:'en'
  66. maemo-launcher: invoking '/usr/bin/hildon-input-method.launch'
  67. process 4071: arguments to dbus_connection_send_with_reply_and_block() were incorrect, assertion "connection != NULL" failed in file dbus-connection.c line 3298.
  68. This is normally a bug in some application using the D-Bus library.
  69. process 4071: arguments to dbus_message_get_args() were incorrect, assertion "message != NULL" failed in file dbus-message.c line 1670.
  70. This is normally a bug in some application using the D-Bus library.
  71. hildon-input-method[4071]: GLIB WARNING ** GVFS-RemoteVolumeMonitor - Error parsing args in reply for IsSupported(): (null): (null)
  72. Starting browser daemon: maemo-launcher: opening of /usr/bin/hildon-input-method.launch took 776 usec
  73. hildon-desktop[4043]: GLIB WARNING ** default - Could not open D-Bus session/system bus connection.
  74. browserd
  75. /usr/bin/af-sb-init.sh: line 302: 4042 Aborted /usr/bin/hildon-home
  76. /usr/bin/af-sb-init.sh: line 302: 4064 Segmentation fault (core dumped) $TRACKER
  77. /usr/bin/af-sb-init.sh: line 302: 4066 Aborted (core dumped) mafw-dbus-wrapper /usr/lib/mafw-plugin/mafw-tracker-source.so
  78. /usr/bin/af-sb-init.sh: line 302: 4067 Aborted (core dumped) mafw-dbus-wrapper /usr/lib/mafw-plugin/mafw-gst-renderer.so
  79. hildon-input-method[4071]: GLIB WARNING ** default - Could not initialize osso from hildon-input-method
  80. hildon-input-method[4071]: GLIB WARNING ** default - Could not register the osso_hw_set_event_cb
  81. hildon-input-method[4071]: GLIB MESSAGE default - ui up and running
  82. maemo-launcher: child (pid=4047) terminated due to signal=11
  83. [sbox-FREMANTLE_X86: ~] > maemo-launcher: child (pid=4043) terminated due to signal=11
  84. The application 'sapwood-server' lost its connection to the display :2.0;
  85. most likely the X server was shut down or you killed/destroyed
  86. the application.
  87. The application 'hildon-input-method' lost its connection to the display :2.0;
  88. most likely the X server was shut down or you killed/destroyed
  89. the application.
  90. The application 'browserd' lost its connection to the display :2.0;
  91. most likely the X server was shut down or you killed/destroyed
  92. the application.
  93. maemo-launcher: child (pid=4071) terminated due to exit()=1
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement