Hardy image-creator projects don't run correctly in Gutsy Xephyr
Bug #196280 reported by
Bill Filler
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Moblin Image Creator |
Confirmed
|
Medium
|
Praj | ||
dbus (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
moblin-image-creator (Ubuntu) |
Confirmed
|
Undecided
|
Praj |
Bug Description
Binary package hint: moblin-
Currently there is a problem with testing Hardy image creator projects on a Gutsy workstation. When running ume-xephyr-start, the UI is displayed but the .xsession-errors file shows many errors involving DBus and not being able to connect to the DBus session bus. This causes many applications and statusbar plugins to fail as they cannont initialze DBus or osso. This needs to be investigated further. Possibly it's a simple configuration that m-i-c might be able to set?
Changed in moblin-image-creator: | |
assignee: | nobody → prajwal-linux |
Changed in moblin-image-creator: | |
importance: | Undecided → Medium |
Changed in moblin-image-creator: | |
assignee: | nobody → prajwal-linux |
Changed in moblin-image-creator: | |
status: | New → Confirmed |
status: | New → Confirmed |
To post a comment you must log in.
Error from .xsession-errors:
Xsession: X session started for root at Wed Feb 27 22:00:57 UTC 2008
sudo: unable to resolve host bfiller-ironhorse
(seahorse- agent:5960) : GnomeUI-WARNING **: While connecting to session manager:
Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed.
** INFO: server started
localuser:root being added to access control list
Can't get session bus: 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.
** Message: Phone Manager UI start
** (hildon- desktop: 5960): WARNING **: Failed to open connection to bus: 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.
** (moblin- settings- daemon: 6033): WARNING **: The name org.freedesktop.Hal was not provided by any .service files
** (moblin- settings- daemon: 6033): WARNING **: Can not access the Alsa device node!
** (moblin- settings- daemon: 6033): WARNING **: Unable to 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.
** (moblin- settings- daemon: 6033): CRITICAL **: dbus_g_ connection_ register_ g_object: assertion `connection != NULL' failed
** (moblin- settings- daemon: 6033): CRITICAL **: dbus_g_ proxy_new_ for_name: assertion `connection != NULL' failed
** (moblin- settings- daemon: 6033): CRITICAL **: dbus_g_proxy_call: assertion `DBUS_IS_G_PROXY (proxy)' failed