Hi Thomas,
All the errors in the log you shared are expected errors, they do not cause any
issue.
The error "Another instance for VM "Sailfish OS Emulator 3.1.0.12" already
exists" is also unrelated to your issues.
The errors from qt.network.ssl are something I would be worry about, but again
it is not related
to your issues.
What I bet is (was) the source of your issues is the content of your
VirtualBox.xml.
> <MachineEntry uuid="{75bfc298-7ac0-4ca5-91fb-9f031ee0a5a3}"
>
> src="/home/tol/SailfishOS/mersdk/Sailfish OS Build Engine/Sailfish
> OS Build Engine.vbox"/>>
> <MachineEntry uuid="{1b641bc9-9c41-47fe-998a-8b8e91810c5b}"
>
> src="/home/tol/SailfishOS/emulator/Sailfish OS Emulator/Sailfish OS
> Emulator.vbox"/>>
> <MachineEntry uuid="{aa96b162-4811-475c-bb57-8147302d6178}"
>
> src="/home/thomas/SailfishOS/mersdk/MerSDK/MerSDK.vbox"/>
>
> <MachineEntry uuid="{1944d1bb-99ff-4ac8-8507-1475fdbcfa6d}"
>
> src="/home/thomas/SailfishOS/mersdk/Sailfish OS Build
> Engine/Sailfish OS Build Engine.vbox"/>>
> <MachineEntry uuid="{f8bc1e14-f8e1-48ed-a1a0-e51cd94296da}"
>
> src="/home/thomas/SailfishOS/emulator/Sailfish OS Emulator
> 3.1.0.12/Sailfish OS Emulator 3.1.0.12/Sailfish OS Emulator
> 3.1.0.12.vbox"/>>
> </MachineRegistry>
Did you change your user name in past or so?
There are two entries with "/home/tol/" as the home directory, while the others
have "/home/
thomas/". One of them is for a "Sailfish OS Build Engine" from some older SDK
installation that I
believe is not available anymore on that path under /home/tol, which would be a
possible reason
to end with VBOX_E_INVALID_OBJECT_STATE. Qt Creator uses VM names instead of
UUIDs, so
which VM would it be trying to start with `vboxmanage startvm 'Sailfish OS
Build Engine'`? The
existing one under /home/thomas or the unavailable one under /home/tol?
BR,
Martin
_______________________________________________
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
