Just to confirm - the sailfish icon in question is a tiny icon at the top left by the url bar.
What happens is that QtC checks this url too soon (ie before it launches the SDK Engine with the web app) and doesn't retry when it gets this problem. Finally, if http://localhost:8080/ in the url bar fails then that's a new problem :) David On 02/08/13 10:14, christopher.l...@thurweb.ch wrote: > Hi Lucien > > I have both VMs up an running, and have been able to deploy a test > application. > > Any amount of clicking on the Sailfish Icon does not change anything - I still > get the same error. > > I have this both on OSX and on Lubuntu. > > Chris > > > Zitat von "Lucien XU" <sfietkonstan...@free.fr>: > >> Hello Chris, >> >> Refresh the view by clicking n the Sailfish. It should give you the >> maintenance view back (if your MerSDK VM is launched) >> >> Cheers, >> Lucien >> >> Le vendredi 2 août 2013 08:15:33 christopher.l...@thurweb.ch a écrit : >>> Hi All >>> >>> On the new Qt5Alpha, If I press the SailfishOS Icon on the left of >>> QtCreator (e.g. to see what packages are installed) I get the >>> following error: >>> >>> "The SDK VM is not responding. Create a new SailfishOS project (or >>> open an existing one) and press the Start SDK button on the lower left." >>> >>> I have the default SailfishOS project open, and have successfully >>> deployed it to the Emulator VM. >>> >>> Grüsse >>> >>> Chris >>> >>> _______________________________________________ >>> SailfishOS.org Devel mailing list >> _______________________________________________ >> SailfishOS.org Devel mailing list >> > > > > _______________________________________________ > SailfishOS.org Devel mailing list _______________________________________________ SailfishOS.org Devel mailing list
