[SailfishDevel] Sailfish Emulator on Lubuntu Native not working either.

[christopher.lamb at thurweb.ch]

Hi Jonni

While your suggestion that nested VMs might cause the behavour I  
reported was plausible and sage, in this case the nested VMs thing has  
proved to be a red-herring.

I now have a native install of Lubuntu 13.04 on an old Lenovo T61  
laptop (from which I am penning this mail). This setup exhibits  
exactly the same Emulator SSH wackiness, and the same workarounds  
described below also cure things.

ciao

Chris

Zitat von "Jonni Rainisto" <jonni.rainisto at jollamobile.com>:

> Hi,
>
> We are not supporting nested VM's, it may or may not work. Nesting  
> kills performance and can cause other weirdness too, like you are  
> experiencing. You are better off just using OSX SDK without nesting.
>
> re. Jonni
> ________________________________________
> From: devel-bounces at lists.sailfishos.org  
> [devel-bounces at lists.sailfishos.org] on behalf of  
> christopher.lamb at thurweb.ch [christopher.lamb at thurweb.ch]
> Sent: Sunday, April 28, 2013 8:40 PM
> To: Thomas Perl
> Cc: devel at lists.sailfishos.org
> Subject: Re: [SailfishDevel] Sailfish Emulator on Lubuntu: SSH not    
>    working:        Victoria in Excelsis!!!!
>
> Hi Thomas
>
> Thanks for your advice
>
> I was aware of the "Agent admitted failure to sign .." know issue, but
> had not tried the SSH_AUTH_SOCK= workaround, as my error message is
> different.
>
> However in the meantime I upgraded my Lubuntu installation to 13.04.
> After the upgrade, I got the Agent error AND the "Permission denied
> (publickey)" when trying to ssh to the MERSDK.
>
> chris at LubuntuVM:~$ ssh -p 2222 -i ~/.ssh/mer-qt-creator-rsa
> root at localhostAgent admitted failure to sign using the key.
> Permission denied (publickey).
>
> --> applying fix from known issues:
> chris at LubuntuVM:~$ export SSH_AUTH_SOCK=
> chris at LubuntuVM:~$ ssh -p 2222 -i ~/.ssh/mer-qt-creator-rsa root at localhost
> Last login: Sat Apr 27 16:10:26 2013
> [root at SailfishSDK ~]#
>
>
> As we see above the SSH_AUTH_SOCK= fixes things for the MERSDK.
>
> Trying the same for the Emulator:
> chris at LubuntuVM:~$ ssh -p 2223 -i ~/.ssh/mer-qt-creator-rsa root at localhost
> Permission denied (publickey).
> chris at LubuntuVM:~$ export SSH_AUTH_SOCK=
> chris at LubuntuVM:~$ ssh -p 2223 -i ~/.ssh/mer-qt-creator-rsa root at localhost
> Permission denied (publickey).
> chris at LubuntuVM:~$
>
> did not fix things for the Emulator.
>
> After a lot of playing around I concluded that the problem is that
> Emulator (should that not be an Ostrichator on Lubuntu?) was not
> mounting its shared folders, while the MerSdk clearly was. In some
> ways i had hinted at this in my original post at the start of this
> thread.
>
> So I tried this in the Emulator:
>
> mount -t vboxsf ssh /etc/ssh/authorised _keys/
>
> And Voila! I can now SSH in from the host Lubuntu as root and nemo.
>
> So next I ventured into the dark world of fstab; adding an entry to  
> automount:
> cd /etc
> echo ssh /etc/ssh/authorized_keys vboxsf defaults 0 0 >> fstab
>
> After a restart, the shared drive is now auto mounted, and I can ssh in.
>
> Interestingly (in a nerdy sort of way), after doing this the Emulator
> seems to keep its vertical shape. Previously it started wider, was
> briefly vertical, then switched quickly back to the horizontal wide
> shape. (This is circumstantial evidence at the moment, after one
> restart ...)
>
> Most importantly, having ensured that the shared folder automounts, I
> can now build and run the mediagallery example without error: This was
> the original objective of the Lubuntu test installation.
>
> So the question is: Why does:
> 1) the MerSdk on Lubuntu mount its shared folders no problem, but the
> Emulator on Lubuntu not automount, and needs tweaking as described
> above?
> 2) the MerSdk and the Emulator on OSX mount their share folders no  
> problem ...
>
> Grüsse
>
> Chris
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Zitat von "Thomas Perl" <th.perl at gmail.com>:
>
>> Hi Christopher,
>>
>> 2013/4/27  <christopher.lamb at thurweb.ch>:
>>> I can ssh to the SDK VM, but get errors when I SSH to the Emulator VM.
>>>
>>> I get "Permission denied (publickey)."
>>
>> Should be similar to the one problem mentioned in the known issues page[1]:
>>
>>     If you get "Agent admitted failure to sign using the key"
>>     when using ssh, try setting SSH_AUTH_SOCK=
>>
>> Alternatively, you can set a different shared folder in VirtualBox'
>> preferences and make sure that your normal SSH key's public key gets
>> picked up by the emulator. Or move your ~/.ssh/id_rsa (private key)
>> out of place somewhere temporarily and make sure the ssh agent forgets
>> it to check if that's the issue.
>>
>> Finally, you can set up a SSH connection to your local sailfish
>> emulator (in ~/.ssh/config):
>>
>> Host sailfishemu
>>     HostName localhost
>>     User nemo
>>     IdentityFile ~/.ssh/mer-qt-creator-rsa
>>     Port 2223
>>
>>
>> HTH :)
>> Thomas
>>
>> [1] https://sailfishos.org/wiki/SDK_Alpha_Known_Issues#Emulator
>>
>
>
> _______________________________________________
> SailfishOS.org Devel mailing list
>