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
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
Thanks guys, I did find a solution in the comment section here:
http://joshuawise.com/horndis#available_versions
On 17 July 2016 at 11:27, Chris Walker <
cdw_noki...@the-walker-household.co.uk> wrote:
> On Sat, 16 Jul 2016 16:00:52 +0100
> Krisztian Olah 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 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
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
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
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
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
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