On 27.05.2012, at 19:41, Thomas C Gilliard wrote:
On 05/27/2012 05:37 AM, Peter Robinson wrote:
On Thu, May 24, 2012 at 4:56 PM, Thomas C Gilliard
satel...@bendbroadband.com wrote:
I have been testing the RC4 f17 release of SoaS [1] and I see a problem with
e-toys:
If jabber.sugarlabs.org
On 28.05.2012, at 15:52, Peter Robinson wrote:
On Mon, May 28, 2012 at 2:50 PM, Bert Freudenberg b...@freudenbergs.de
wrote:
SoaS still has the old Etoys version (4.1). Etoys 5 was released along with
Sugar 0.96. It is more robust wrt presence service failures.
It has issues with
On 28.05.2012, at 15:52, Peter Robinson wrote:
On Mon, May 28, 2012 at 2:50 PM, Bert Freudenberg b...@freudenbergs.de
wrote:
SoaS still has the old Etoys version (4.1). Etoys 5 was released along with
Sugar 0.96. It is more robust wrt presence service failures.
it also still needs the
On Thu, May 24, 2012 at 4:56 PM, Thomas C Gilliard
satel...@bendbroadband.com wrote:
I have been testing the RC4 f17 release of SoaS [1] and I see a problem with
e-toys:
If jabber.sugarlabs.org is connected via a wireless AP, or wired network,
e-toys will not start:
DBusError: Process
On 05/27/2012 05:37 AM, Peter Robinson wrote:
On Thu, May 24, 2012 at 4:56 PM, Thomas C Gilliard
satel...@bendbroadband.com wrote:
I have been testing the RC4 f17 release of SoaS [1] and I see a problem with
e-toys:
If jabber.sugarlabs.org is connected via a wireless AP, or wired network,
I have been testing the RC4 f17 release of SoaS [1] and I see a problem
with e-toys:
If jabber.sugarlabs.org is connected via a wireless AP, or wired
network, e-toys will not start:
DBusError: Process /usr/bin/sugar-presence-service exited with status 1
Etoys runs fine if wireless is not
6 matches
Mail list logo
