Re: [Sugar-devel] Etoys in RC4 SoaS-v7 does not start when jabber is connected. ( f17 release is imminent )
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 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 logged in and/or wired network is not connected. (no jabber connected) As Etoys is a favorite on the f3 ring and f17 release is imminent, I feel that this is an important bug to look at. Sorry, it was reported too late. It should have also been reported to the soas list. I have been reporting this occasional failure, But only realized what was causing this behavior 3 days ago. : ( It is possible to use E-toys but the DBusError created by the starting example is very distracting. See bugs.sugarlabs.org/ticket/3640#comment:1 The start up example seems to require process /usr/bin/sugar-presence-service 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. - Bert - ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Etoys in RC4 SoaS-v7 does not start when jabber is connected. ( f17 release is imminent )
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 translations and the non standard location it installs them Why is that a problem? Seems to have worked fine so far - and nothing else but Etoys is using these translation files. - Bert - ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Etoys in RC4 SoaS-v7 does not start when jabber is connected. ( f17 release is imminent )
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 sugar-presence-service package which has been obsolete for a long time. Etoys 5 is no worse than previous versions in that respect. On the contrary, it deals better with presence service deterioration. Re-implementing the presence service takes time, I'm on my own, can't make it happen soon. - Bert - ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Etoys in RC4 SoaS-v7 does not start when jabber is connected. ( f17 release is imminent )
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 /usr/bin/sugar-presence-service exited with status 1 Etoys runs fine if wireless is not logged in and/or wired network is not connected. (no jabber connected) As Etoys is a favorite on the f3 ring and f17 release is imminent, I feel that this is an important bug to look at. Sorry, it was reported too late. It should have also been reported to the soas list. Peter ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Etoys in RC4 SoaS-v7 does not start when jabber is connected. ( f17 release is imminent )
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, e-toys will not start: DBusError: Process /usr/bin/sugar-presence-service exited with status 1 Etoys runs fine if wireless is not logged in and/or wired network is not connected. (no jabber connected) As Etoys is a favorite on the f3 ring and f17 release is imminent, I feel that this is an important bug to look at. Sorry, it was reported too late. It should have also been reported to the soas list. I have been reporting this occasional failure, But only realized what was causing this behavior 3 days ago. : ( It is possible to use E-toys but the DBusError created by the starting example is very distracting. See bugs.sugarlabs.org/ticket/3640#comment:1 The start up example seems to require process /usr/bin/sugar-presence-service Peter ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Etoys in RC4 SoaS-v7 does not start when jabber is connected. ( f17 release is imminent )
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 logged in and/or wired network is not connected. (no jabber connected) As Etoys is a favorite on the f3 ring and f17 release is imminent, I feel that this is an important bug to look at. Sugar on a Stick 7 (Quandong) Fedora release 17 (beefy Miracle) 0.96.1 Tom Gilliard satellit_ tested with dd usb and liveinst HD install [1] http://dl.fedoraproject.org/pub/alt/stage/17.RC4/Spins/x86_64/Fedora-17-x86_64-Live-SoaS.iso ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
