Re: [SailfishDevel] Timeout of MerSDK and the Emulator

Hi, That was exactly the same problem. Checking those boxes fixed that for me too. Thanks! On 23.07.2016 16:28, r0kk3rz wrote: Hi Guys, I just faced a similar issue and figured out that in the VBox network settings for the VM that the 'Cable Connected' checkbox for each adapter was

Re: [SailfishDevel] Timeout of MerSDK and the Emulator

Hi Guys, I just faced a similar issue and figured out that in the VBox network settings for the VM that the 'Cable Connected' checkbox for each adapter was unticked after a clean install. Checking those boxes fixed the issue Regards, Lewis Rockliffe On Thu, Jul 21, 2016 at 8:24 AM, Marcin

Re: [SailfishDevel] Timeout of MerSDK and the Emulator

Hi, I tried zyppering the package, but Error code: connection failed Error message: Couldn't resolve host: 'releases.jolla.com' $ ping 8.8.8.8 connect: Network is unreachable So I have no networking inside the VM. Last upgrade was a couple of days ago, next will be today. I did reboot ;)

Re: [SailfishDevel] Timeout of MerSDK and the Emulator

Hi Marcin, failed.log, statefs.log: both failing statefs and tmpfiles are known issues and shouldn't be related to this. sshd.log: according to the log you mistyped "sshd" as "ssh", but anyway "sshd.service" is not used, instead you should check the status of "sshd.socket". Also note that the

Re: [SailfishDevel] Timeout of MerSDK and the Emulator

Hi, sshd is not running at all. The output of `systemctl --failed`, `systemctl status statefs`, `systemctl status sshd` On 18.07.2016 16:27, Martin Kampas wrote: Hi Marcin, Could you check SSH logs on the VM side? For that purpose please start the MerSDK VM directly from VirtualBox and

Re: [SailfishDevel] Timeout of MerSDK and the Emulator

Hi, As root the logs are empty (only a message: logs begin at ... end at ...) On 19.07.2016 10:22, Martin Kampas wrote: Hi Marcin, > Before and after: No journal files were found. Did you run it as root? BR, Martin -- Marcin ___ SailfishOS.org

Re: [SailfishDevel] Timeout of MerSDK and the Emulator

Hi Marcin, > Before and after: No journal files were found. Did you run it as root? BR, Martin ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] Timeout of MerSDK and the Emulator

Hi Marcin, Simply move the -b switch to the very end of the command line: `journalctl _COMM=sshd -b` so that it does not treat "_COMM=sshd" as an argument to it. BR, Martin ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to

Re: [SailfishDevel] Timeout of MerSDK and the Emulator

I have a weird thing. running `journalctl -b _COMM=sshd` yields Failed to parse relative boot ID number '_COMM=sshd" On 18.07.2016 16:27, Martin Kampas wrote: Hi Marcin, Could you check SSH logs on the VM side? For that purpose please start the MerSDK VM directly from VirtualBox and quit Qt

Re: [SailfishDevel] Timeout of MerSDK and the Emulator

Hi Marcin, Could you check SSH logs on the VM side? For that purpose please start the MerSDK VM directly from VirtualBox and quit Qt Creator *before* that (it would try to reconnect periodically, filling the log excessively). Started this way the MerSDK VM will show its window - read the

Re: [SailfishDevel] Timeout of MerSDK and the Emulator

Hi, I didn't install AppArmor, SELinux or a firewall manually. I had an Ubuntu live iso, installed openssh added a port forwarding on adapter 1 (NAT): protocol: TCP, host IP: 127.0.0.1, host port: 2224, guest IP: left blank, guest port 22 Then I connected: ssh -p 2224 ubuntu@localhost and I

Re: [SailfishDevel] Timeout of MerSDK and the Emulator

Hi Marcin, > ssh_exchange_identification: read: Connection reset by peer Could this be result of some firewall or mandatory access control (SELinux, AppArmor, ...) on your installation? (Can you SSH to any other VirtualBox VM? If you have no other VM, could you install e.g. Arch Linux in your

Re: [SailfishDevel] Timeout of MerSDK and the Emulator

Hi Marcin, Does SSH-ing from command line work? For emulator you can try: ssh -i ~/devel/SailfishOS/vmshare/ssh/private_keys/SailfishOS_Emulator/root -p 2223 root@localhost -o StrictHostKeyChecking=no For build engine: ssh -i ~/devel/SailfishOS/vmshare/ssh/private_keys/engine/root -p

Re: [SailfishDevel] Timeout of MerSDK and the Emulator

I guess I tried again once or twice, with the same result. Then gave up. Basically the emulator shows up after ~5 seconds but the SDK can't connect to it. On Mon Jul 18 08:29:21 2016 Martin Kampas wrote: > Hi Marcin, > > > Anyway, the SDK reported a timeout and asked

Re: [SailfishDevel] Timeout of MerSDK and the Emulator

Hi Marcin, > Anyway, the SDK reported a timeout and asked whether I want to try running > the emulator again. What happened then? Did the message window persisted (re-)appearing on the screen indefinitely? BR, Martin ___ SailfishOS.org Devel mailing

Re: [SailfishDevel] Timeout of MerSDK and the Emulator

Maybe this one helps? https://together.jolla.com/question/137948/howto-virtualbox-io-error/ cheers, Michael. On Sonntag, 17. Juli 2016 12:56:25 CEST Marcin Mielniczuk wrote: > Hi, > > I installed the SailfishOSSDK-Beta-1602-Qt5-linux-64-offline.run on my > Arch Linux. I'm using Virtualbox 5.1,

[SailfishDevel] Timeout of MerSDK and the Emulator

Hi, I installed the SailfishOSSDK-Beta-1602-Qt5-linux-64-offline.run on my Arch Linux. I'm using Virtualbox 5.1, uname -a is: Linux arch 4.4.15-1-lts #1 SMP Mon Jul 11 20:46:47 CEST 2016 x86_64 GNU/Linux I created a sample project and ran the SailfishOS emulator. Within 30 seconds the emulator