Re: [MeeGo-dev] Show white window when run the simulator on MeeGo-SDK
My laptop could running MeeGo 1.0 image fine. But your graphic chipset maybe without support list. Now, i could started MeeGo in simulator and show wallpaper without other widget. 在 2010年6月17日 上午4:16，cc fedora2...@163.com写道： I just meet the same problem. and after few days , I still have not sloved this problem. And even i changed my hardware that support SSS3 instruction. my harderware: CPU core D E7500 MEM 2G MOTHERBORD G41 GraphicsCard: NV7300GT But i just tested Meego on different operating system. Ubuntu9.10 without Nvdia 7300 graphics card run OK. Ubuntu9.10 with Nvdia 7300 graphics car run D-Bus Error Fedora 10 without Nvdia 7300 graphics card run D-Bus Error Fedora 10 with Nvdia 7300 graphics card also run D-Bus Error when i see your discussion. i use su - export DBUS_SESSION_BUS_ADDRESS= solved the DebusError but it still run white window . problem like blow shows /***/ Cannot get current online state: The name org.moblin.connman was not provided by any .service filesABRT服务不在运行 ** (bluetooth-panel:30090): DEBUG: Unable to create proxy for /org/moblin/UX/Shell/Toolbar: Could not get owner of name 'org.moblin.UX.Shell.Toolbar': no such name (bluetooth-panel:30090): GLib-GObject-WARNING **: invalid (NULL) pointer instance (bluetooth-panel:30090): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed (bluetooth-panel:30090): GLib-GObject-WARNING **: invalid (NULL) pointer instance (bluetooth-panel:30090): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed (bluetooth-panel:30090): GLib-GObject-WARNING **: invalid (NULL) pointer instance (bluetooth-panel:30090): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed ** (carrick-connection-panel:30097): DEBUG: Unable to create proxy for /org/moblin/UX/Shell/Toolbar: Could not get owner of name 'org.moblin.UX.Shell.Toolbar': no such name ** (carrick-connection-panel:30097): DEBUG: Error: Couldn't end get properties call - The name org.moblin.connman was not provided by any .service files ** (carrick-connection-panel:30097): DEBUG: Error when ending GetProperties call: The name org.moblin.connman was not provided by any .service files ** (carrick-connection-panel:30097): DEBUG: Error when ending GetProperties call: The name org.moblin.connman was not provided by any .service files (gpk-update-icon:30133): devkit-power-gobject-WARNING **: Couldn't enumerate devices: The name org.freedesktop.DeviceKit.Power was not provided by any .service files (gpk-update-icon:30133): devkit-power-gobject-WARNING **: Error invoking GetAll() to get properties: The name org.freedesktop.DeviceKit.Power was not provided by any .service files ** (matchbox-panel:30138): WARNING **: 缺少 --geometry 的参数 failed to create drawable ** ERROR **: Unable to initialize Clutter. aborting... failed to create drawable W: main.c: 不应以root身份运行本程序（除非指定 --system）。 Loading simple Config module ... Creating backend ... Initializing tracker-miner-fs... Tracker-Message: Checking XDG_DATA_HOME is writable and exists Tracker-Message: XDG_DATA_HOME is '(null)' ** (moblin-power-icon:30151): DEBUG: Unable to create proxy for /org/moblin/UX/Shell/Toolbar: Could not get owner of name 'org.moblin.UX.Shell.Toolbar': no such name (moblin-power-icon:30151): devkit-power-gobject-WARNING **: Couldn't enumerate devices: The name org.freedesktop.DeviceKit.Power was not provided by any .service files (moblin-power-icon:30151): devkit-power-gobject-WARNING **: Couldn't enumerate devices: The name org.freedesktop.DeviceKit.Power was not provided by any .service files (gnome-settings-daemon:30128): GVFS-RemoteVolumeMonitor-WARNING **: invoking IsSupported() failed for remote volume monitor with dbus name org.gtk.Private.GduVolumeMonitor: org.freedesktop.DBus.Error.Spawn.ChildSignaled: Process /usr/libexec/gvfs-gdu-volume-monitor received signal 6 ** (moblin-power-icon:30151): DEBUG: No outputs have backlight property ** (moblin-power-icon:30151): DEBUG: no XRANDR extension, so aborting init (moblin-power-icon:30151): devkit-power-gobject-WARNING **: Couldn't enumerate devices: The name org.freedesktop.DeviceKit.Power was not provided by any .service files (moblin-power-icon:30151): devkit-power-gobject-WARNING **: Error invoking GetAll() to get properties: The name org.freedesktop.DeviceKit.Power was not provided by any .service files (moblin-power-icon:30151): Clutter-WARNING **: Called clutter_main() but Clutter wasn't initialised. You must call clutter_init() first. Tracker-Message: Path is OK Tracker-Message: XDG_DATA_HOME set to '/root/.local/share' Tracker-Message: Path is OK Tracker-Message: Setting
Re: [MeeGo-dev] Show white window when run the simulator on MeeGo-SDK
On Wednesday 16 June 2010 05:34:42 Xu Cheng wrote: Graham Cobb, thank u very much. But i didn't solve the problem. I may not have made myself clear. Try either (or both) of the following: I input command by your way: $ xhost +local: $su -c meego-sdk-chroot Downloads/meego-sdk-0524 root Try using: su -c meego-sdk-chroot Downloads/meego-sdk-0524 - root (note that the - is preceded and followed by a space) r...@meego-netbook-sdk:/# export DBUS_SESSION_BUS_ADDRESS=startmeego-debug r...@meego-netbook-sdk:/# startmeego-debug Try: export DBUS_SESSION_BUS_ADDRESS= startmeego-debug The problem is that DBUS_SESSION_BUS_ADDRESS must either be undefined or must be a null string before invoking startmeego-debug. It seems to be deliberate that startmeego-debug doesn't start dbus if it is already running but I am beginning to think it should be changed. Graham ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] Show white window when run the simulator on MeeGo-SDK
On Wednesday 16 June 2010 11:58:25 Graham Cobb wrote: The problem is that DBUS_SESSION_BUS_ADDRESS must either be undefined or must be a null string before invoking startmeego-debug. It seems to be deliberate that startmeego-debug doesn't start dbus if it is already running but I am beginning to think it should be changed. Reported as bug 3156. By the way, if this turns out to be your problem you may want to vote for the bug! ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] Show white window when run the simulator on MeeGo-SDK
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
