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
