Hi, everyone
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.
Thanks.
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.
(process:2396): GLib-GObject-WARNING **: invalid (NULL) pointer instance
(process:2396): GLib-GObject-CRITICAL **: g_signal_connect_data:
assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
(process:2396): 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: 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.
libnotify-Message: Unable to 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.
dbus error: 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.
Can't connect to session dbus
** (bluetooth-panel:2413): WARNING **: 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.
** (matchbox-panel:2455): WARNING **: Missing argument for --geometry
** (carrick-connection-panel:2418): WARNING **: 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.
** (gnome-settings-daemon:2451): WARNING **: Couldn't connect to
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.
** (gnome-settings-daemon:2451): WARNING **: Could not get a
connection to the bus
(mutter:2397): 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
(mutter:2397): mutter-WARNING **: No D-BUS daemon running
(mutter:2397): 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
(mutter:2397): mutter-WARNING **: No D-BUS daemon running
(mutter:2397): 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
(mutter:2397): mutter-WARNING **: No D-BUS daemon running
(mutter:2397): 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
(mutter:2397): mutter-WARNING **: No D-BUS daemon running
(mutter:2397): 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
(mutter:2397): mutter-WARNING **: No D-BUS daemon running
(mutter:2397): 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
(mutter:2397): mutter-WARNING **: No D-BUS daemon running
(mutter:2397): 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
(mutter:2397): mutter-WARNING **: No D-BUS daemon running
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.
obexd[2470]: manager_init failed
(mutter:2397): 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
(mutter:2397): mutter-WARNING **: No D-BUS daemon running
(mutter:2397): 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
(mutter:2397): mutter-WARNING **: No D-BUS daemon running
(mutter:2397): 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
(mutter:2397): mutter-WARNING **: No D-BUS daemon running
(mutter:2397): 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
(mutter:2397): mutter-WARNING **: No D-BUS daemon running
(mutter:2397): 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
(mutter:2397): mutter-WARNING **: No D-BUS daemon running
(mutter:2397): 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
(mutter:2397): mutter-WARNING **: No D-BUS daemon running
(mutter:2397): 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
(mutter:2397): mutter-WARNING **: No D-BUS daemon running
(mutter:2397): 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
(mutter:2397): mutter-WARNING **: No D-BUS daemon running
libnotify-Message: Unable to 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.
(gpk-update-icon:2449): Unique-DBus-WARNING **: Unable to open a
connection to the 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.
(gpk-update-icon:2449): Unique-DBus-WARNING **: Unable to connect to
the running instance, aborting.
(mutter:2397): 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
(mutter:2397): mutter-WARNING **: No D-BUS daemon running
(mutter:2397): 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
(mutter:2397): mutter-WARNING **: No D-BUS daemon running
(mutter:2397): 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
(mutter:2397): mutter-WARNING **: No D-BUS daemon running
(mutter:2397): 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
(mutter:2397): mutter-WARNING **: No D-BUS daemon running
(mutter:2397): 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
(mutter:2397): mutter-WARNING **: No D-BUS daemon running
(mutter:2397): 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
(mutter:2397): mutter-WARNING **: No D-BUS daemon running
(mutter:2397): 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
(mutter:2397): mutter-WARNING **: No D-BUS daemon running
(mutter:2397): 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
(mutter:2397): mutter-WARNING **: No D-BUS daemon running
(mutter:2397): 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
(mutter:2397): mutter-WARNING **: No D-BUS daemon running
(mutter:2397): 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
(mutter:2397): mutter-WARNING **: No D-BUS daemon running
(mutter:2397): 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
(mutter:2397): mutter-WARNING **: No D-BUS daemon running
(mutter:2397): 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
(mutter:2397): mutter-WARNING **: No D-BUS daemon running
(mutter:2397): 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
(mutter:2397): mutter-WARNING **: No D-BUS daemon running
(mutter:2397): 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
(mutter:2397): mutter-WARNING **: No D-BUS daemon running
(mutter:2397): 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
(mutter:2397): mutter-WARNING **: No D-BUS daemon running
(mutter:2397): 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
(mutter:2397): 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:2397): mutter-WARNING **: 0 stored in GConf key
/apps/metacity/general/num_workspaces is out of range 1 to 36
(mutter:2397): 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
(mutter:2397): mutter-WARNING **: No D-BUS daemon running
(mutter:2397): 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
(mutter:2397): 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:2397): mutter-WARNING **: 0 stored in GConf key
/desktop/gnome/peripherals/mouse/cursor_size is out of range 1 to 128
(mutter:2397): 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
(mutter:2397): mutter-WARNING **: No D-BUS daemon running
(mutter:2397): 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.
GConf Error: No D-BUS daemon running
(mutter:2397): 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.
GConf Error: No D-BUS daemon running
(mutter:2397): 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
(mutter:2397): mutter-WARNING **: No D-BUS daemon running
(mutter:2397): 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.
GConf Error: No D-BUS daemon running
(mutter:2397): 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.
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:2397): 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:2397): mutter-WARNING **: Failed to load theme "Simple":
Failed to find a valid file for theme Simple
W: main.c: This program is not intended to be run as root (unless
--system is specified).
** (moblin-panel-myzone:2460): WARNING **: 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.
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'
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'
13 Jun 2010, 06:50:59: Tracker-Critical **: Could not connect to the
D-Bus 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.
(tracker-miner-fs:2497): Tracker-CRITICAL **: Could not connect to the
D-Bus 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.
libnotify-Message: Unable to 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.
** (moblin-power-icon:2465): WARNING **: 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.
[ERROR] g_dbus_setup_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.
XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0"
after 133 requests (133 known processed) with 0 events remaining.
Window manager warning: Fatal IO error 11 (Resource temporarily
unavailable) on display ':2'.
(mutter:2397): mutter-WARNING **: Fatal IO error 11 (Resource
temporarily unavailable) on display ':2'.
/usr/bin/startmeego-debug: line 131: 2396 Segmentation fault
(core dumped) ionice -n7 /usr/libexec/mission-control-5
[1]+ Exit 1 startmeego
--
Xu Cheng
+86-13517271560
-----------------------------------------------------------------
Wuhan Dail Science & Technology Co., Ltd
www.virtualdell.com
TEL: +86-27-83360199
FAX: +86-27-83775399
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
