Hi All

I'vd complete "jhbuild-moblin build" stage with no error.
But when launch moblin2 shell, I got some error message and moblin desktop shows about 5 secs, then get back to black window.

Please help to check it out what's the problem. Fellowing are full message.


# Xephyr :1 -screen 1024x600 -host-cursor -ac &
Then, a new window opened with following message:
=====================================================
SELinux: Disabled on system, not enabling in X server
unrecognised device identifier!
(EE) config/hal: NewInputDeviceRequest failed (2)
unrecognised device identifier!
(EE) config/hal: NewInputDeviceRequest failed (2)
unrecognised device identifier!
(EE) config/hal: NewInputDeviceRequest failed (2)
unrecognised device identifier!
=====================================================
I don't know if the message is normal...., continue next step.

# jhbuild-moblin2 run /path/to/moblin2-jhbuild/build/launch-in-xephyr.sh
Then I got following message:

====================================================================
(mutter:1005): GConf-WARNING **: Client failed to connect to the D-BUS daemon: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Window manager warning: No D-BUS daemon running

*******(above message repeats over 40 times)

Window manager warning: Failed to load theme "(null)": Failed to find a valid file for theme (null)

Window manager warning: Failed to load theme "Simple": Failed to find a valid file for theme Simple

Window manager warning: Failed to load theme "LargePrint": Failed to find a valid file for theme LargePrint

Window manager warning: Failed to load theme "LowContrastLargePrint": Failed to find a valid file for theme LowContrastLargePrint

Window manager warning: Log level 16: Cannot connect to DBus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Window manager warning: Log level 16: mnb-toolbar.c:1949 DBus connection not available !!! Window manager warning: Log level 16: Cannot connect to DBus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Window manager warning: Log level 128: Panel service [myzone] is not running, starting. Window manager warning: Log level 8: dbus_g_connection_get_connection: assertion `gconnection' failed process 1005: arguments to dbus_bus_start_service_by_name() were incorrect, assertion "connection != NULL" failed in file dbus-bus.c line 1306.
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
======================================================================
*** That new window shows moblin desktop picture for about 5 secs, then get back to black ***


_______________________________________________
Moblin dev Mailing List
[email protected]

To manage or unsubscribe from this mailing list visit:
http://lists.moblin.org/listinfo/dev or your user account on http://moblin.org 
once logged in.

For more information on the Moblin Developer Mailing lists visit:
http://moblin.org/community/mailing-lists

Reply via email to