Graham Cobb, thank u very much. But i didn't solve the problem.
I input command by your way:
$ xhost +local:
$su -c "meego-sdk-chroot Downloads/meego-sdk-0524" root
r...@meego-netbook-sdk:/# export DBUS_SESSION_BUS_ADDRESS="startmeego-debug"
r...@meego-netbook-sdk:/# startmeego-debug
And then, Xephyr's screen show white again. The debug messages tell me
"No D-BUS daemon running" and "This program is not intended to be run
as root".
Full debug messages:
Failed to open connection to bus: Address does not contain a colon
(process:2926): GLib-GObject-WARNING **: invalid (NULL) pointer instance
(process:2926): GLib-GObject-CRITICAL **: g_signal_connect_data:
assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
(process:2926): mcd-CRITICAL **: mcd_mission_connect: assertion
`MCD_IS_MISSION (mission)' failed
Cannot get current online state: The name org.moblin.connman was not
provided by any .service fileslibnotify-Message: Unable to get session
bus: Address does not contain a colon
libnotify-Message: Unable to get session bus: Address does not contain a colon
dbus error: Address does not contain a colon
Can't connect to session dbus
** (bluetooth-panel:2944): WARNING **: Cannot connect to DBus: Address
does not contain a colon
** (gnome-settings-daemon:2977): WARNING **: Couldn't connect to
session bus: Address does not contain a colon
** (gnome-settings-daemon:2977): WARNING **: Could not get a
connection to the bus
** (matchbox-panel:2986): WARNING **: Missing argument for --geometry
** (carrick-connection-panel:2949): WARNING **: Cannot connect to
DBus: Address does not contain a colon
libnotify-Message: Unable to get session bus: Address does not contain a colon
** (moblin-power-icon:2996): WARNING **: Cannot connect to DBus:
Address does not contain a colon
(mutter:2927): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Address does not contain a colon
Window manager warning: No D-BUS daemon running
(mutter:2927): mutter-WARNING **: No D-BUS daemon running
(mutter:2927): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Address does not contain a colon
Window manager warning: No D-BUS daemon running
(mutter:2927): mutter-WARNING **: No D-BUS daemon running
(mutter:2927): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Address does not contain a colon
Window manager warning: No D-BUS daemon running
(mutter:2927): mutter-WARNING **: No D-BUS daemon running
(mutter:2927): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Address does not contain a colon
Window manager warning: No D-BUS daemon running
(mutter:2927): mutter-WARNING **: No D-BUS daemon running
(mutter:2927): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Address does not contain a colon
Window manager warning: No D-BUS daemon running
(mutter:2927): mutter-WARNING **: No D-BUS daemon running
(mutter:2927): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Address does not contain a colon
Window manager warning: No D-BUS daemon running
(mutter:2927): mutter-WARNING **: No D-BUS daemon running
(mutter:2927): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Address does not contain a colon
Window manager warning: No D-BUS daemon running
(mutter:2927): mutter-WARNING **: No D-BUS daemon running
(mutter:2927): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Address does not contain a colon
Window manager warning: No D-BUS daemon running
(mutter:2927): mutter-WARNING **: No D-BUS daemon running
(mutter:2927): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Address does not contain a colon
Window manager warning: No D-BUS daemon running
(mutter:2927): mutter-WARNING **: No D-BUS daemon running
(mutter:2927): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Address does not contain a colon
Window manager warning: No D-BUS daemon running
(mutter:2927): mutter-WARNING **: No D-BUS daemon running
(mutter:2927): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Address does not contain a colon
Window manager warning: No D-BUS daemon running
(mutter:2927): mutter-WARNING **: No D-BUS daemon running
(mutter:2927): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Address does not contain a colon
Window manager warning: No D-BUS daemon running
(mutter:2927): mutter-WARNING **: No D-BUS daemon running
(mutter:2927): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Address does not contain a colon
Window manager warning: No D-BUS daemon running
(mutter:2927): mutter-WARNING **: No D-BUS daemon running
(mutter:2927): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Address does not contain a colon
Window manager warning: No D-BUS daemon running
(mutter:2927): mutter-WARNING **: No D-BUS daemon running
(mutter:2927): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Address does not contain a colon
Window manager warning: No D-BUS daemon running
(mutter:2927): mutter-WARNING **: No D-BUS daemon running
(mutter:2927): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Address does not contain a colon
Window manager warning: No D-BUS daemon running
(mutter:2927): mutter-WARNING **: No D-BUS daemon running
(mutter:2927): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Address does not contain a colon
Window manager warning: No D-BUS daemon running
(mutter:2927): mutter-WARNING **: No D-BUS daemon running
(mutter:2927): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Address does not contain a colon
Window manager warning: No D-BUS daemon running
(mutter:2927): mutter-WARNING **: No D-BUS daemon running
(mutter:2927): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Address does not contain a colon
Window manager warning: No D-BUS daemon running
(mutter:2927): mutter-WARNING **: No D-BUS daemon running
(mutter:2927): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Address does not contain a colon
Window manager warning: No D-BUS daemon running
(mutter:2927): mutter-WARNING **: No D-BUS daemon running
(mutter:2927): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Address does not contain a colon
Window manager warning: No D-BUS daemon running
(mutter:2927): mutter-WARNING **: No D-BUS daemon running
(mutter:2927): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Address does not contain a colon
Window manager warning: No D-BUS daemon running
(mutter:2927): mutter-WARNING **: No D-BUS daemon running
(mutter:2927): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Address does not contain a colon
Window manager warning: No D-BUS daemon running
(mutter:2927): mutter-WARNING **: No D-BUS daemon running
(mutter:2927): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Address does not contain a colon
Window manager warning: No D-BUS daemon running
(mutter:2927): mutter-WARNING **: No D-BUS daemon running
(mutter:2927): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Address does not contain a colon
Window manager warning: No D-BUS daemon running
(mutter:2927): mutter-WARNING **: No D-BUS daemon running
(mutter:2927): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Address does not contain a colon
Window manager warning: No D-BUS daemon running
(mutter:2927): mutter-WARNING **: No D-BUS daemon running
(mutter:2927): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Address does not contain a colon
Window manager warning: No D-BUS daemon running
(mutter:2927): mutter-WARNING **: No D-BUS daemon running
(mutter:2927): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Address does not contain a colon
Window manager warning: No D-BUS daemon running
(mutter:2927): mutter-WARNING **: No D-BUS daemon running
(mutter:2927): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Address does not contain a colon
Window manager warning: No D-BUS daemon running
(mutter:2927): mutter-WARNING **: No D-BUS daemon running
(mutter:2927): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Address does not contain a colon
Window manager warning: No D-BUS daemon running
(mutter:2927): mutter-WARNING **: No D-BUS daemon running
(mutter:2927): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Address does not contain a colon
Window manager warning: No D-BUS daemon running
(mutter:2927): mutter-WARNING **: No D-BUS daemon running
Window manager warning: 0 stored in GConf key
/apps/metacity/general/num_workspaces is out of range 1 to 36
(mutter:2927): mutter-WARNING **: 0 stored in GConf key
/apps/metacity/general/num_workspaces is out of range 1 to 36
(mutter:2927): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Address does not contain a colon
Window manager warning: No D-BUS daemon running
(mutter:2927): mutter-WARNING **: No D-BUS daemon running
(mutter:2927): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Address does not contain a colon
Window manager warning: No D-BUS daemon running
(mutter:2927): mutter-WARNING **: No D-BUS daemon running
Window manager warning: 0 stored in GConf key
/desktop/gnome/peripherals/mouse/cursor_size is out of range 1 to 128
(mutter:2927): mutter-WARNING **: 0 stored in GConf key
/desktop/gnome/peripherals/mouse/cursor_size is out of range 1 to 128
(mutter:2927): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Address does not contain a colon
Window manager warning: No D-BUS daemon running
(mutter:2927): mutter-WARNING **: No D-BUS daemon running
(mutter:2927): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Address does not contain a colon
GConf Error: No D-BUS daemon running
(mutter:2927): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Address does not contain a colon
GConf Error: No D-BUS daemon running
(mutter:2927): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Address does not contain a colon
Window manager warning: No D-BUS daemon running
(mutter:2927): mutter-WARNING **: No D-BUS daemon running
(mutter:2927): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Address does not contain a colon
GConf Error: No D-BUS daemon running
(mutter:2927): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Address does not contain a colon
GConf Error: No D-BUS daemon running
Window manager warning: Failed to load theme "(null)": Failed to find
a valid file for theme (null)
(mutter:2927): mutter-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
(mutter:2927): mutter-WARNING **: Failed to load theme "Simple":
Failed to find a valid file for theme Simple
Initializing tracker-miner-fs...
Tracker-Message: Checking XDG_DATA_HOME is writable and exists
Tracker-Message: XDG_DATA_HOME is '(null)'
Tracker-Message: Path is OK
Tracker-Message: XDG_DATA_HOME set to '/root/.local/share'
Tracker-Message: Path is OK
Tracker-Message: Setting process priority
Tracker-Message: Setting up monitor for changes to config
file:'/root/.config/tracker/tracker-miner-fs.cfg'
libnotify-Message: Unable to get session bus: Address does not contain a colon
(gpk-update-icon:2981): Unique-DBus-WARNING **: Unable to open a
connection to the session bus: Address does not contain a colon
(gpk-update-icon:2981): Unique-DBus-WARNING **: Unable to connect to
the running instance, aborting.
W: main.c: This program is not intended to be run as root (unless
--system is specified).
Address does not contain a colon
obexd[3001]: manager_init failed
** (moblin-panel-myzone:2991): WARNING **: Cannot connect to DBus:
Address does not contain a colon
Tracker-Message: Loading defaults into GKeyFile...
Could not open log:'/root/.local/share/tracker/tracker-miner-fs.log',
No such file or directory
All logging will go to stderr
Starting log:
File:'/root/.local/share/tracker/tracker-miner-fs.log'
16 Jun 2010, 00:29:08: Tracker-Critical **: Could not connect to the
D-Bus session bus, Address does not contain a colon
(tracker-miner-fs:3025): Tracker-CRITICAL **: Could not connect to the
D-Bus session bus, Address does not contain a colon
[ERROR] g_dbus_setup_bus(): Address does not contain a colon
XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0"
after 130 requests (130 known processed) with 0 events remaining.
Window manager warning: Fatal IO error 11 (Resource temporarily
unavailable) on display ':2'.
(mutter:2927): mutter-WARNING **: Fatal IO error 11 (Resource
temporarily unavailable) on display ':2'.
/usr/bin/startmeego-debug: line 131: 2926 Segmentation fault
(core dumped) ionice -n7 /usr/libexec/mission-control-5
2010/6/14, Graham Cobb <[email protected]>:
> On Sunday 13 June 2010 12:15:47 Xu Cheng wrote:
>> I has been download and set up MeeGo-SDK on my laptop. (Intel T3200,
>> GMA4500, Fedora 13 KDE English). But it show white window when
>> simulator started.
>
> I saw a similar problem when I first tried using the SDK (Debian Testing,
> AMD64, Nvideo graphics).
>
>> r...@meego-netbook-sdk:/# startmeego-debug
>> 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.
>
> In my experience, this is the key error message, which causes all the rest.
> This is the one to concentrate on fixing! The message is telling you that
> dbus is not running (or cannot be found).
>
> One thing I found (and it depends on how you invoke the SDK): before you run
> startmeego-debug, check that the environment symbol DBUS_SESSION_BUS_ADDRESS
> is not defined or is null. Try:
>
> DBUS_SESSION_BUS_ADDRESS="" startmeego-debug
>
> In my case, I was running meego-sdk-chroot using su and both su and
> meego-sdk-chroot were carefully preserving the environment symbols from my
> user session, including the DBUS Session Bus Address which then did not work
> inside the chroot! You can avoid that by using "su - ", which runs a login
> shell. I don't use sudo myself but I believe the "-i" option to sudo is
> similar.
>
> Another thing that could case a similar error: I had tried using "su"
> **WITHIN** the chroot to change to another account (so that the files it
> wrote would be owned by my user account when viewed outside the chroot).
> Obviously that is NOT how the Wiki page says to run startmeego and it didn't
> work. But it did give a similar error message.
>
> Graham
> _______________________________________________
> MeeGo-dev mailing list
> [email protected]
> http://lists.meego.com/listinfo/meego-dev
>
--
Xu Cheng
徐诚 +86-13517271560
-----------------------------------------------------------------
Wuhan Dail Science & Technology Co., Ltd
武汉代尔科技有限公司
www.virtualdell.com
TEL: +86-27-83360199
FAX: +86-27-83775399
ADD: 中国湖北省武汉市�~口区荣华一村13号
Ronghuayicun No.13, Qiaokou District
Wuhan, Hubei Province, P.R.C
PC: 430023
-----------------------------------------------------------------
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
