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
Tone Kastlunger wrote:
> Strictly speaking, I don't see any problem with this - from a syncml
> client / server
> perspective; was the socket owned by the bluetooth manager also for bluez4
> as well?
No, the problem is with Qt5 - There was a totally different mechanism and
the service interface w
Hello,
I have been looking at the Sailfish OS network connection management code and
libconnman-qt. I expected to see code that writes a connman configuration for
WPA2 Enterprise support, but so far I have not found it. Our current solution
is to write a file in /var/lib/connman that has the au
After having reinstalled one more time, I was just about to throw in the
towel - when, lo and behold, it was working!!! Except for having to
authorize the device, it was out-of-the-box.
Anyways, this was what I had written, and warnings in the installation log
were quite frightening. Link inclu
>These might be useful for another applications that may be using dbus, but
>not for the syncml code that relies solely on filedescriptors outside dbus.
Strictly speaking, I don't see any problem with this - from a syncml client
/ server
perspective; was the socket owned by the bluetooth manager a
Thomas Tanghus wrote:
> Yes, I do.
> I have these:
>
> src="/home/tol/SailfishOS/mersdk/Sailfish OS Build Engine/Sailfish OS
> Build Engine.vbox"/> uuid="{1b641bc9-9c41-47fe-998a-8b8e91810c5b}"
> src="/home/tol/SailfishOS/emulator/Sailfish OS Emulator/Sailfish OS
> Emulator.vbox"/> uuid="{aa96
On mandag den 5. august 2019 13.22.09 CEST deloptes wrote:
> Thomas Tanghus wrote:
> > Regarding "Another instance for VM "Sailfish OS Emulator 3.1.0.12" already
> > exists":
> >
> > I had to install/remove several times to get it in a semi-working state.
> > One of those times I manually removed
Iosif Hamlatzis wrote:
> Under Win10 during installation I get the following error: SSH timeout.
Sorry I do not use windows. On Linux I deleted everything and removed the
entry from the xml file. Windows might be registry thing - no idea - sorry.
regards
How did you manage to install the SDK?
Under Win10 during installation I get the following error: SSH timeout.
If I press retry I continuously get the same error. If I press ignore I get
the same error for all targets. At some time the installation succeeds, but
cannot start the build engine
On
Thomas Tanghus wrote:
> Regarding "Another instance for VM "Sailfish OS Emulator 3.1.0.12" already
> exists":
>
> I had to install/remove several times to get it in a semi-working state.
> One of those times I manually removed the ~/SailfishOS and
> ~/.config/SailfishOS- SDK and ~/.config/Virtual
Hi,
I finally got the newest SDK installed, but the build stops with:
'Error while building/deploying project harbour-kitchentimer (kit:
SailfishOS-3.1.0.12-armv7hl (in Sailfish OS Build Engine))
When executing step "Start Build Engine"'
In the console it prints:
---[snip]
11 matches
Mail list logo
