Friday, 25 October 2013

Alpha 2: After the update of 22 Oct 2013

Hi All

As announced by Jarko here there is a refresh of the Sailfish Alpha available now.

This post lists some immediate differences I have noticed, and some changes I had to make to get "things" working again.

As / If I discover other stuff, I will update this post


Where is my SDK VM?

The most obvious thing (and mentioned deep in Jarko's post) is that the SDK Build Engine VM now starts without a GUI. But the GUI can be reactivated if required via tools/options/mer menu.


If, after the SDK update, you get the following errors when SSHing to the Emulator or SDK VMs read on.


apple-pip:abstractui christopherlamb$ ssh -p 2223  -i ~/.ssh/mer-qt-creator-rsa  nemo@localhost





Someone could be eavesdropping on you right now (man-in-the-middle attack)!

It is also possible that a host key has just been changed.

The fingerprint for the RSA key sent by the remote host is


Please contact your system administrator.

Add correct host key in /Users/christopherlamb/.ssh/known_hosts to get rid of this message.

Offending RSA key in /Users/christopherlamb/.ssh/known_hosts:8

RSA host key for [localhost]:2223 has changed and you have requested strict checking.

Host key verification failed.

apple-pip:abstractui christopherlamb$ zypper se

-bash: zypper: command not found


The solution is very easy, but it is one of those that always has me for scratching my head for a few minutes trying to remember how I last did this:


Find the know_hosts file in ./ssh


Make a back up copy of the file


From the original, remove the two entries starting with:






Note you may have multiple entries with the same port number. In the error above we see the correct one to remove is line 8.


You will find more advice in this thread.


Previously I used to SSH to the Emulator / SDK as follows:


ssh -p 2222  -i ~/.ssh/mer-qt-creator-rsa  nemo@localhost


ssh -p 2223  -i ~/.ssh/mer-qt-creator-rsa  nemo@localhost


As the SDK and Emulator have been newly installed (rather than being updated) it means we have to use new keys

To connect to the SDK BuildEngine VM:

ssh -p 2222 -i ~/<SailfishOSInstallLocation>/vmshare/ssh/private_keys/engine/mersdk mersdk@localhost

ssh -p 2222 -i ~/<SailfishOSInstallLocation>/vmshare/ssh/private_keys/engine/root root@localhost

To connect to the Emulator:

ssh -p 2223 -i ~/<SailfishOSInstallLocation>/vmshare/ssh/private_keys/1/nemo nemo@localhost

ssh -p 2223 -i ~/<SailfishOSInstallLocation>/vmshare/ssh/private_keys/1/root root@localhost


Zypper may need refreshing. To verify this, first run "zypper se". If only lists the installed modules, and not those available but not yet installed then you will need to run the following:

sudo zypper refresh

After this zypper se should give a much longer list of modules.




No comments:

Post a Comment