It happened to me after resuming my Linux box from suspend. Maybe this'll
give some clue.
--
Marcin
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
This happens on Windows as well, after resume (Win7 in particular)
On Tue, Jul 15, 2014 at 7:35 PM, Marcin M. marmistrz...@gmail.com wrote:
It happened to me after resuming my Linux box from suspend. Maybe this'll
give some clue.
--
Marcin
___
Hi Jarko and Juha
Right now QtCreator is deploying as RPM without a problem - whereas last
week it was consistently giving the error. I am sure it will rear its
ugly head soon, so I will report back then following your advice.
In the meantime, some more background info.
I am on OSX 10.8.5
Hi Jarko
Have got on the train, started deploying, and get the problem. Below is
output from the SDK and QtCreator.
I am starting to wonder if the problem is related to networking in some
way. This morning I successfully deployed at home - connected to the
home wireless network.
Now I am
Hi Jarko
Still on the train, now with the Jolla Wifi Hotspot active, and I can
build without problems.
This indicates that I get the problem when no network is connected. In
this case I am deploying to the Emulator, so no network should be
required
Grüsse
Chris
On 02.06.14 10:23,
I get the same error often when developing with Windows 8 64-bit, never on Mac
OSX 10. They are both always connected to the (same) network. It helps to close
and open the virtual machine, the it stays reachable for another while once it
does the same again.
- Saija
Lähetetty iPadista
Hi Saija
In my case restarting the VMs does not help. I think (from memory) that
rebooting the whole laptop does help.
It is possible that the same reported error may have a number of
different causes - in my case it seems to be when my development host
loses its network connection (though
Oh, that sounds like a lot worse case than mine. I can live with mine since
it's easy to fix temporarily, but I truly hope the cause is found for your case
and fixed permanently.
- Saija
Lähetetty iPadista
Christopher Lamb christopher.l...@thurweb.ch kirjoitti 3.6.2014 kello
10.24:
Hi
Hi Christopher,
the changing networks may play a part in this problem. Did I already
sometime earlier ask you to modify your Mac's /etc/hosts file?
It has helped in some cases to add the name for the MerSDK virtual
machine to /etc/hosts like this:
127.0.0.1 SailfishSDK
Or if you already
Hi Juha
I have edited my /etc/hosts to look like this:
127.0.0.1 localhost SailfishSDK
255.255.255.255 broadcasthost
::1 localhost
fe80::1%lo0 localhost
Now in the office, with WIFI turned off, and no ethernet plugged in, I
can deploy as RPM successfully! So for the
Hi Juha
I am now on the train. Deployment also works with WiFi active, but not
properly connected.
This means that - at least in my case - adding SailfishSDK to the
/etc/hosts is a good fix for this error.
I think this is one for the Known Issues page.
I guess that (without the entry in
On 28.04.2014 09:01, christopher.l...@thurweb.ch wrote:
Hi
Thanks.
I found a well hidden {1} timeout setting in the preferences / devices
and increased this from the default 2 secs to 10 secs. This does seem
to help, but as always with sporadic problems only time will tell if
this is a fix,
Hi I for once happen to get the issue every once in a while even during
binary deployment.
Best,
tk
On Thursday, May 29, 2014, Christopher Lamb christopher.l...@thurweb.ch
wrote:
Hi All
I am still suffering from this issue, and getting more and more frustrated!
Right now it is refusing to
Hi All
I am still suffering from this issue, and getting more and more frustrated!
Right now it is refusing to deploy as RPM to the Emulator.
Is anything I can do to better debug / understand this issue?
The timeout settings previously suggested are probably red-herrings, as
they apply to
Hi
Thanks.
I found a well hidden {1} timeout setting in the preferences / devices
and increased this from the default 2 secs to 10 secs. This does seem
to help, but as always with sporadic problems only time will tell if
this is a fix, or if the problem is just dormant for a while.
What
Hi All
I am suffering from sporadic bouts of the error: Could not connect to
MerSDK Virtual Machine. Timeout waiting for reply from server
One moment I can be happily hacking and deploying code to my Jolla
without error. Then I make a small change to the code, try to deploy,
and bing!
I believe the timeout setting can be adjusted in QtCreator where you set up
your mer device(ssh password, etc). By increasing this value you can probably
prevent the timeout issue altogether. I don't have the SDK in front of me to
give you the exact menu you need to open, but it isn't too hard
17 matches
Mail list logo
