Re: [Sugar-devel] [SoaS] Recommendations for running Sugar on standard hardware (non-XOs)?

2014-04-09 Thread Christoph Derndorfer
Tom, Sam, Martin, Ian, David,

thanks a lot for all your input, I'll point the German guy to these
resources and ask him to report back his findings.

Cheers,
Christoph

On Wed, Apr 9, 2014 at 2:26 AM, David Beveridge bevh...@gmail.com wrote:

 I have a stick here based on Fedora 20.  To get to root I pressed F3
 to get to the list menu and clicked on Terminal.
 Once terminal is running I type su - to be come root and liveinst
 to start ananconda
 $ su -
 # liveinst


 On Wed, Apr 9, 2014 at 2:39 AM, Christoph Derndorfer
 christoph.derndor...@gmail.com wrote:
  Hi David,
 
  thanks for the link.
 
  Given that this page was last updated back in 2012 I'm wondering whether
  anyone knows if the instructions are still up-to-date and working?
 
  Cheers,
  Christoph
 
 
  On Tue, Apr 8, 2014 at 8:19 AM, David Beveridge bevh...@gmail.com
 wrote:
 
  I would try this method..,
 
 
 http://wiki.sugarlabs.org/go/Tutorials/Installation/Install_with_liveinst
 
  On Tue, Apr 8, 2014 at 4:36 AM, Christoph Derndorfer
  christoph.derndor...@gmail.com wrote:
   Hey everyone,
  
   a guy I know wants to set up a couple of older laptops with Sugar in a
   sort
   of learning lab in Germany and asked me what the best route for
 doing
   that
   was. Since I haven't dabbled in that area in quite a while I'm not
 sure
   what
   the best recommendations are these days:
  
   * using the SoaS version from late December?
   * installing Fedora 20 and running Sugar on top of that?
   * something entirely different?
  
   Any comments, suggestions, links, etc. would be much appreciated.
  
   Thanks,
   Christoph
  
   --
   Christoph Derndorfer
  
   volunteer, OLPC (Austria) [www.olpc.at]
   editor, OLPC News [www.olpcnews.com]
   co-founder, TechnikBasteln® [www.technikbasteln.net]
  
   e-mail: christ...@derndorfer.eu
  
  
   ___
   SoaS mailing list
   s...@lists.sugarlabs.org
   http://lists.sugarlabs.org/listinfo/soas
  
  ___
  SoaS mailing list
  s...@lists.sugarlabs.org
  http://lists.sugarlabs.org/listinfo/soas
 
 
 
 
  --
  Christoph Derndorfer
 
  volunteer, OLPC (Austria) [www.olpc.at]
  editor, OLPC News [www.olpcnews.com]
  co-founder, TechnikBasteln® [www.technikbasteln.net]
 
  e-mail: christ...@derndorfer.eu
 
 
  ___
  SoaS mailing list
  s...@lists.sugarlabs.org
  http://lists.sugarlabs.org/listinfo/soas
 




-- 
Christoph Derndorfer

volunteer, OLPC (Austria) [www.olpc.at]
editor, OLPC News [www.olpcnews.com]
co-founder, TechnikBasteln® [www.technikbasteln.net]

e-mail: christ...@derndorfer.eu
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


[Sugar-devel] Really bad web activity crashes on XO

2014-04-09 Thread Sam Parkinson
Hi,

I was trying to run a web activity on an XO with the 102 image, but no
matter what activity I run I just get:

 1397035392.644876 ERROR root: Using port 56277

/usr/lib/python2.7/site-packages/gi/module.py:151: Warning: cannot register
existing type `WebKitWebResource'

 g_type = info.get_g_type()

/usr/lib/python2.7/site-packages/gi/module.py:151: Warning:
g_once_init_leave: assertion `result != 0' failed

 g_type = info.get_g_type()

/usr/lib/python2.7/site-packages/gi/module.py:155: Warning:
g_type_get_qdata: assertion `node != NULL' failed

 type_ = g_type.pytype

/usr/lib/python2.7/site-packages/gi/module.py:195: Warning:
g_type_get_qdata: assertion `node != NULL' failed

 g_type.pytype = wrapper

/usr/lib/python2.7/site-packages/gi/module.py:195: Warning:
g_type_set_qdata: assertion `node != NULL' failed

 g_type.pytype = wrapper


This is a bit of an issue as every web activity crashes :(

Does anyone have any ideas? It didn't crash on 100. I tested removing the
file selector changes but it didn't fix it (yay, wasn't my fault :P).


Thanks, Sam



P.S. Does anyone know about these errors in sugar-build:

  libEGL warning: DRI2: failed to open swrast (search paths /usr/lib64/dri)

  libEGL warning: GLX: glXQueryVersion failed

They only appear on sugar-build, not epiphany (another gtk-webkit2 browser)
in gnome.
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] Really bad web activity crashes on XO

2014-04-09 Thread Gonzalo Odiard
I don't know what could be the error, but thanks for reporting!

Gonzalo


On Wed, Apr 9, 2014 at 6:46 AM, Sam Parkinson sam.parkins...@gmail.comwrote:

 Hi,

 I was trying to run a web activity on an XO with the 102 image, but no
 matter what activity I run I just get:

  1397035392.644876 ERROR root: Using port 56277

 /usr/lib/python2.7/site-packages/gi/module.py:151: Warning: cannot
 register existing type `WebKitWebResource'

  g_type = info.get_g_type()

 /usr/lib/python2.7/site-packages/gi/module.py:151: Warning:
 g_once_init_leave: assertion `result != 0' failed

  g_type = info.get_g_type()

 /usr/lib/python2.7/site-packages/gi/module.py:155: Warning:
 g_type_get_qdata: assertion `node != NULL' failed

  type_ = g_type.pytype

 /usr/lib/python2.7/site-packages/gi/module.py:195: Warning:
 g_type_get_qdata: assertion `node != NULL' failed

  g_type.pytype = wrapper

 /usr/lib/python2.7/site-packages/gi/module.py:195: Warning:
 g_type_set_qdata: assertion `node != NULL' failed

  g_type.pytype = wrapper


 This is a bit of an issue as every web activity crashes :(

 Does anyone have any ideas? It didn't crash on 100. I tested removing the
 file selector changes but it didn't fix it (yay, wasn't my fault :P).


 Thanks, Sam



 P.S. Does anyone know about these errors in sugar-build:

   libEGL warning: DRI2: failed to open swrast (search paths
 /usr/lib64/dri)

   libEGL warning: GLX: glXQueryVersion failed

 They only appear on sugar-build, not epiphany (another gtk-webkit2
 browser) in gnome.

 ___
 Sugar-devel mailing list
 Sugar-devel@lists.sugarlabs.org
 http://lists.sugarlabs.org/listinfo/sugar-devel




-- 
Gonzalo Odiard

SugarLabs - Software for children learning
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] Really bad web activity crashes on XO

2014-04-09 Thread Daniel Narvaez
The sugar-build errors sounds like missing Mesa/gl bits, which are probably
not part of the platform yet. What are you trying to do?

On Wednesday, 9 April 2014, Sam Parkinson sam.parkins...@gmail.com wrote:

 Hi,

 I was trying to run a web activity on an XO with the 102 image, but no
 matter what activity I run I just get:

  1397035392.644876 ERROR root: Using port 56277

 /usr/lib/python2.7/site-packages/gi/module.py:151: Warning: cannot
 register existing type `WebKitWebResource'

  g_type = info.get_g_type()

 /usr/lib/python2.7/site-packages/gi/module.py:151: Warning:
 g_once_init_leave: assertion `result != 0' failed

  g_type = info.get_g_type()

 /usr/lib/python2.7/site-packages/gi/module.py:155: Warning:
 g_type_get_qdata: assertion `node != NULL' failed

  type_ = g_type.pytype

 /usr/lib/python2.7/site-packages/gi/module.py:195: Warning:
 g_type_get_qdata: assertion `node != NULL' failed

  g_type.pytype = wrapper

 /usr/lib/python2.7/site-packages/gi/module.py:195: Warning:
 g_type_set_qdata: assertion `node != NULL' failed

  g_type.pytype = wrapper


 This is a bit of an issue as every web activity crashes :(

 Does anyone have any ideas? It didn't crash on 100. I tested removing the
 file selector changes but it didn't fix it (yay, wasn't my fault :P).


 Thanks, Sam



 P.S. Does anyone know about these errors in sugar-build:

   libEGL warning: DRI2: failed to open swrast (search paths
 /usr/lib64/dri)

   libEGL warning: GLX: glXQueryVersion failed

 They only appear on sugar-build, not epiphany (another gtk-webkit2
 browser) in gnome.



-- 
Daniel Narvaez
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] Really bad web activity crashes on XO

2014-04-09 Thread Sam Parkinson
I am trying to:
* run the 2048 Activity (
http://activities.sugarlabs.org/en-US/sugar/addon/4738 )
* use the 'handwritten' (notebook) theme in sugar slides (
https://github.com/SAMdroid-apps/sugar-slides ). That theme has 2 fonts to
load so maybe that is it?
On Apr 9, 2014 8:11 PM, Daniel Narvaez dwnarv...@gmail.com wrote:

 The sugar-build errors sounds like missing Mesa/gl bits, which
 are probably not part of the platform yet. What are you trying to do?

 On Wednesday, 9 April 2014, Sam Parkinson sam.parkins...@gmail.com
 wrote:

 Hi,

 I was trying to run a web activity on an XO with the 102 image, but no
 matter what activity I run I just get:

  1397035392.644876 ERROR root: Using port 56277

 /usr/lib/python2.7/site-packages/gi/module.py:151: Warning: cannot
 register existing type `WebKitWebResource'

  g_type = info.get_g_type()

 /usr/lib/python2.7/site-packages/gi/module.py:151: Warning:
 g_once_init_leave: assertion `result != 0' failed

  g_type = info.get_g_type()

 /usr/lib/python2.7/site-packages/gi/module.py:155: Warning:
 g_type_get_qdata: assertion `node != NULL' failed

  type_ = g_type.pytype

 /usr/lib/python2.7/site-packages/gi/module.py:195: Warning:
 g_type_get_qdata: assertion `node != NULL' failed

  g_type.pytype = wrapper

 /usr/lib/python2.7/site-packages/gi/module.py:195: Warning:
 g_type_set_qdata: assertion `node != NULL' failed

  g_type.pytype = wrapper


 This is a bit of an issue as every web activity crashes :(

 Does anyone have any ideas? It didn't crash on 100. I tested removing the
 file selector changes but it didn't fix it (yay, wasn't my fault :P).


 Thanks, Sam



 P.S. Does anyone know about these errors in sugar-build:

   libEGL warning: DRI2: failed to open swrast (search paths
 /usr/lib64/dri)

   libEGL warning: GLX: glXQueryVersion failed

 They only appear on sugar-build, not epiphany (another gtk-webkit2
 browser) in gnome.



 --
 Daniel Narvaez


___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] Really bad web activity crashes on XO

2014-04-09 Thread Gonzalo Odiard
Are you using css animations?
Manuq reported problems with that in specific hardware

Can you test the Memorize web activity and see if you have the same error,
when the game finish and the pieces rotate?

Gonzalo


On Wed, Apr 9, 2014 at 7:37 AM, Sam Parkinson sam.parkins...@gmail.comwrote:

 I am trying to:
 * run the 2048 Activity (
 http://activities.sugarlabs.org/en-US/sugar/addon/4738 )
 * use the 'handwritten' (notebook) theme in sugar slides (
 https://github.com/SAMdroid-apps/sugar-slides ). That theme has 2 fonts
 to load so maybe that is it?
 On Apr 9, 2014 8:11 PM, Daniel Narvaez dwnarv...@gmail.com wrote:

 The sugar-build errors sounds like missing Mesa/gl bits, which
 are probably not part of the platform yet. What are you trying to do?

 On Wednesday, 9 April 2014, Sam Parkinson sam.parkins...@gmail.com
 wrote:

 Hi,

 I was trying to run a web activity on an XO with the 102 image, but no
 matter what activity I run I just get:

  1397035392.644876 ERROR root: Using port 56277

 /usr/lib/python2.7/site-packages/gi/module.py:151: Warning: cannot
 register existing type `WebKitWebResource'

  g_type = info.get_g_type()

 /usr/lib/python2.7/site-packages/gi/module.py:151: Warning:
 g_once_init_leave: assertion `result != 0' failed

  g_type = info.get_g_type()

 /usr/lib/python2.7/site-packages/gi/module.py:155: Warning:
 g_type_get_qdata: assertion `node != NULL' failed

  type_ = g_type.pytype

 /usr/lib/python2.7/site-packages/gi/module.py:195: Warning:
 g_type_get_qdata: assertion `node != NULL' failed

  g_type.pytype = wrapper

 /usr/lib/python2.7/site-packages/gi/module.py:195: Warning:
 g_type_set_qdata: assertion `node != NULL' failed

  g_type.pytype = wrapper


 This is a bit of an issue as every web activity crashes :(

 Does anyone have any ideas? It didn't crash on 100. I tested removing
 the file selector changes but it didn't fix it (yay, wasn't my fault :P).


 Thanks, Sam



 P.S. Does anyone know about these errors in sugar-build:

   libEGL warning: DRI2: failed to open swrast (search paths
 /usr/lib64/dri)

   libEGL warning: GLX: glXQueryVersion failed

 They only appear on sugar-build, not epiphany (another gtk-webkit2
 browser) in gnome.



 --
 Daniel Narvaez


 ___
 Sugar-devel mailing list
 Sugar-devel@lists.sugarlabs.org
 http://lists.sugarlabs.org/listinfo/sugar-devel




-- 
Gonzalo Odiard

SugarLabs - Software for children learning
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] Really bad web activity crashes on XO

2014-04-09 Thread Sam Parkinson
Yep, 2048 does have css animations. Memorize web does crash too!

But slides doesn't use animations, and the @font-face works a charm
elsewhere, so I don't know what is going on there :(


On Wed, Apr 9, 2014 at 8:43 PM, Gonzalo Odiard godi...@sugarlabs.orgwrote:

 Are you using css animations?
 Manuq reported problems with that in specific hardware

 Can you test the Memorize web activity and see if you have the same error,
 when the game finish and the pieces rotate?

 Gonzalo


 On Wed, Apr 9, 2014 at 7:37 AM, Sam Parkinson sam.parkins...@gmail.comwrote:

 I am trying to:
 * run the 2048 Activity (
 http://activities.sugarlabs.org/en-US/sugar/addon/4738 )
 * use the 'handwritten' (notebook) theme in sugar slides (
 https://github.com/SAMdroid-apps/sugar-slides ). That theme has 2 fonts
 to load so maybe that is it?
  On Apr 9, 2014 8:11 PM, Daniel Narvaez dwnarv...@gmail.com wrote:

 The sugar-build errors sounds like missing Mesa/gl bits, which
 are probably not part of the platform yet. What are you trying to do?

 On Wednesday, 9 April 2014, Sam Parkinson sam.parkins...@gmail.com
 wrote:

 Hi,

 I was trying to run a web activity on an XO with the 102 image, but no
 matter what activity I run I just get:

  1397035392.644876 ERROR root: Using port 56277

 /usr/lib/python2.7/site-packages/gi/module.py:151: Warning: cannot
 register existing type `WebKitWebResource'

  g_type = info.get_g_type()

 /usr/lib/python2.7/site-packages/gi/module.py:151: Warning:
 g_once_init_leave: assertion `result != 0' failed

  g_type = info.get_g_type()

 /usr/lib/python2.7/site-packages/gi/module.py:155: Warning:
 g_type_get_qdata: assertion `node != NULL' failed

  type_ = g_type.pytype

 /usr/lib/python2.7/site-packages/gi/module.py:195: Warning:
 g_type_get_qdata: assertion `node != NULL' failed

  g_type.pytype = wrapper

 /usr/lib/python2.7/site-packages/gi/module.py:195: Warning:
 g_type_set_qdata: assertion `node != NULL' failed

  g_type.pytype = wrapper


 This is a bit of an issue as every web activity crashes :(

 Does anyone have any ideas? It didn't crash on 100. I tested removing
 the file selector changes but it didn't fix it (yay, wasn't my fault :P).


 Thanks, Sam



 P.S. Does anyone know about these errors in sugar-build:

   libEGL warning: DRI2: failed to open swrast (search paths
 /usr/lib64/dri)

   libEGL warning: GLX: glXQueryVersion failed

 They only appear on sugar-build, not epiphany (another gtk-webkit2
 browser) in gnome.



 --
 Daniel Narvaez


 ___
 Sugar-devel mailing list
 Sugar-devel@lists.sugarlabs.org
 http://lists.sugarlabs.org/listinfo/sugar-devel




 --
 Gonzalo Odiard

 SugarLabs - Software for children learning

___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] Really bad web activity crashes on XO

2014-04-09 Thread Gonzalo Odiard
Would be good have these issues documented in the wiki.

Gonzalo


On Wed, Apr 9, 2014 at 7:56 AM, Sam Parkinson sam.parkins...@gmail.comwrote:

 Yep, 2048 does have css animations. Memorize web does crash too!

 But slides doesn't use animations, and the @font-face works a charm
 elsewhere, so I don't know what is going on there :(


 On Wed, Apr 9, 2014 at 8:43 PM, Gonzalo Odiard godi...@sugarlabs.orgwrote:

 Are you using css animations?
 Manuq reported problems with that in specific hardware

  Can you test the Memorize web activity and see if you have the same
 error,
 when the game finish and the pieces rotate?

 Gonzalo


 On Wed, Apr 9, 2014 at 7:37 AM, Sam Parkinson 
 sam.parkins...@gmail.comwrote:

 I am trying to:
 * run the 2048 Activity (
 http://activities.sugarlabs.org/en-US/sugar/addon/4738 )
 * use the 'handwritten' (notebook) theme in sugar slides (
 https://github.com/SAMdroid-apps/sugar-slides ). That theme has 2 fonts
 to load so maybe that is it?
  On Apr 9, 2014 8:11 PM, Daniel Narvaez dwnarv...@gmail.com wrote:

 The sugar-build errors sounds like missing Mesa/gl bits, which
 are probably not part of the platform yet. What are you trying to do?

 On Wednesday, 9 April 2014, Sam Parkinson sam.parkins...@gmail.com
 wrote:

 Hi,

 I was trying to run a web activity on an XO with the 102 image, but no
 matter what activity I run I just get:

  1397035392.644876 ERROR root: Using port 56277

 /usr/lib/python2.7/site-packages/gi/module.py:151: Warning: cannot
 register existing type `WebKitWebResource'

  g_type = info.get_g_type()

 /usr/lib/python2.7/site-packages/gi/module.py:151: Warning:
 g_once_init_leave: assertion `result != 0' failed

  g_type = info.get_g_type()

 /usr/lib/python2.7/site-packages/gi/module.py:155: Warning:
 g_type_get_qdata: assertion `node != NULL' failed

  type_ = g_type.pytype

 /usr/lib/python2.7/site-packages/gi/module.py:195: Warning:
 g_type_get_qdata: assertion `node != NULL' failed

  g_type.pytype = wrapper

 /usr/lib/python2.7/site-packages/gi/module.py:195: Warning:
 g_type_set_qdata: assertion `node != NULL' failed

  g_type.pytype = wrapper


 This is a bit of an issue as every web activity crashes :(

 Does anyone have any ideas? It didn't crash on 100. I tested removing
 the file selector changes but it didn't fix it (yay, wasn't my fault :P).


 Thanks, Sam



 P.S. Does anyone know about these errors in sugar-build:

   libEGL warning: DRI2: failed to open swrast (search paths
 /usr/lib64/dri)

   libEGL warning: GLX: glXQueryVersion failed

 They only appear on sugar-build, not epiphany (another gtk-webkit2
 browser) in gnome.



 --
 Daniel Narvaez


 ___
 Sugar-devel mailing list
 Sugar-devel@lists.sugarlabs.org
 http://lists.sugarlabs.org/listinfo/sugar-devel




 --
 Gonzalo Odiard

 SugarLabs - Software for children learning





-- 
Gonzalo Odiard

SugarLabs - Software for children learning
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] Really bad web activity crashes on XO

2014-04-09 Thread Jerry Vonau
How about actually using the preexisting bug tracker:

http://bugs.sugarlabs.org

Jerry

 On April 9, 2014 at 6:08 AM Gonzalo Odiard godi...@sugarlabs.org wrote:


 Would be good have these issues documented in the wiki.

 Gonzalo


 On Wed, Apr 9, 2014 at 7:56 AM, Sam Parkinson
 sam.parkins...@gmail.comwrote:

  Yep, 2048 does have css animations. Memorize web does crash too!
 
  But slides doesn't use animations, and the @font-face works a charm
  elsewhere, so I don't know what is going on there :(
 
 
  On Wed, Apr 9, 2014 at 8:43 PM, Gonzalo Odiard
  godi...@sugarlabs.orgwrote:
 
  Are you using css animations?
  Manuq reported problems with that in specific hardware
 
   Can you test the Memorize web activity and see if you have the same
  error,
  when the game finish and the pieces rotate?
 
  Gonzalo
 
 
  On Wed, Apr 9, 2014 at 7:37 AM, Sam Parkinson
  sam.parkins...@gmail.comwrote:
 
  I am trying to:
  * run the 2048 Activity (
  http://activities.sugarlabs.org/en-US/sugar/addon/4738 )
  * use the 'handwritten' (notebook) theme in sugar slides (
  https://github.com/SAMdroid-apps/sugar-slides ). That theme has 2
  fonts
  to load so maybe that is it?
   On Apr 9, 2014 8:11 PM, Daniel Narvaez dwnarv...@gmail.com
 wrote:
 
  The sugar-build errors sounds like missing Mesa/gl bits, which
  are probably not part of the platform yet. What are you trying to
  do?
 
  On Wednesday, 9 April 2014, Sam Parkinson sam.parkins...@gmail.com
  wrote:
 
  Hi,
 
  I was trying to run a web activity on an XO with the 102 image, but
  no
  matter what activity I run I just get:
 
   1397035392.644876 ERROR root: Using port 56277
 
  /usr/lib/python2.7/site-packages/gi/module.py:151: Warning: cannot
  register existing type `WebKitWebResource'
 
   g_type = info.get_g_type()
 
  /usr/lib/python2.7/site-packages/gi/module.py:151: Warning:
  g_once_init_leave: assertion `result != 0' failed
 
   g_type = info.get_g_type()
 
  /usr/lib/python2.7/site-packages/gi/module.py:155: Warning:
  g_type_get_qdata: assertion `node != NULL' failed
 
   type_ = g_type.pytype
 
  /usr/lib/python2.7/site-packages/gi/module.py:195: Warning:
  g_type_get_qdata: assertion `node != NULL' failed
 
   g_type.pytype = wrapper
 
  /usr/lib/python2.7/site-packages/gi/module.py:195: Warning:
  g_type_set_qdata: assertion `node != NULL' failed
 
   g_type.pytype = wrapper
 
 
  This is a bit of an issue as every web activity crashes :(
 
  Does anyone have any ideas? It didn't crash on 100. I tested
  removing
  the file selector changes but it didn't fix it (yay, wasn't my
  fault :P).
 
 
  Thanks, Sam
 
 
 
  P.S. Does anyone know about these errors in sugar-build:
 
    libEGL warning: DRI2: failed to open swrast (search paths
  /usr/lib64/dri)
 
    libEGL warning: GLX: glXQueryVersion failed
 
  They only appear on sugar-build, not epiphany (another gtk-webkit2
  browser) in gnome.
 
 
 
  --
  Daniel Narvaez
 
 
  ___
  Sugar-devel mailing list
  Sugar-devel@lists.sugarlabs.org
  http://lists.sugarlabs.org/listinfo/sugar-devel
 
 
 
 
  --
  Gonzalo Odiard
 
  SugarLabs - Software for children learning
 
 
 


 --
 Gonzalo Odiard

 SugarLabs - Software for children learning
 ___
 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


Re: [Sugar-devel] Really bad web activity crashes on XO

2014-04-09 Thread Gonzalo Odiard
True. Better use trac.


On Wed, Apr 9, 2014 at 8:17 AM, Jerry Vonau m...@jvonau.ca wrote:

 How about actually using the preexisting bug tracker:

 http://bugs.sugarlabs.org

 Jerry

  On April 9, 2014 at 6:08 AM Gonzalo Odiard godi...@sugarlabs.org
 wrote:
 
 
  Would be good have these issues documented in the wiki.
 
  Gonzalo
 
 
  On Wed, Apr 9, 2014 at 7:56 AM, Sam Parkinson
  sam.parkins...@gmail.comwrote:
 
   Yep, 2048 does have css animations. Memorize web does crash too!
  
   But slides doesn't use animations, and the @font-face works a charm
   elsewhere, so I don't know what is going on there :(
  
  
   On Wed, Apr 9, 2014 at 8:43 PM, Gonzalo Odiard
   godi...@sugarlabs.orgwrote:
  
   Are you using css animations?
   Manuq reported problems with that in specific hardware
  
Can you test the Memorize web activity and see if you have the same
   error,
   when the game finish and the pieces rotate?
  
   Gonzalo
  
  
   On Wed, Apr 9, 2014 at 7:37 AM, Sam Parkinson
   sam.parkins...@gmail.comwrote:
  
   I am trying to:
   * run the 2048 Activity (
   http://activities.sugarlabs.org/en-US/sugar/addon/4738 )
   * use the 'handwritten' (notebook) theme in sugar slides (
   https://github.com/SAMdroid-apps/sugar-slides ). That theme has 2
   fonts
   to load so maybe that is it?
On Apr 9, 2014 8:11 PM, Daniel Narvaez dwnarv...@gmail.com
  wrote:
  
   The sugar-build errors sounds like missing Mesa/gl bits, which
   are probably not part of the platform yet. What are you trying to
   do?
  
   On Wednesday, 9 April 2014, Sam Parkinson sam.parkins...@gmail.com
 
   wrote:
  
   Hi,
  
   I was trying to run a web activity on an XO with the 102 image, but
   no
   matter what activity I run I just get:
  
1397035392.644876 ERROR root: Using port 56277
  
   /usr/lib/python2.7/site-packages/gi/module.py:151: Warning: cannot
   register existing type `WebKitWebResource'
  
g_type = info.get_g_type()
  
   /usr/lib/python2.7/site-packages/gi/module.py:151: Warning:
   g_once_init_leave: assertion `result != 0' failed
  
g_type = info.get_g_type()
  
   /usr/lib/python2.7/site-packages/gi/module.py:155: Warning:
   g_type_get_qdata: assertion `node != NULL' failed
  
type_ = g_type.pytype
  
   /usr/lib/python2.7/site-packages/gi/module.py:195: Warning:
   g_type_get_qdata: assertion `node != NULL' failed
  
g_type.pytype = wrapper
  
   /usr/lib/python2.7/site-packages/gi/module.py:195: Warning:
   g_type_set_qdata: assertion `node != NULL' failed
  
g_type.pytype = wrapper
  
  
   This is a bit of an issue as every web activity crashes :(
  
   Does anyone have any ideas? It didn't crash on 100. I tested
   removing
   the file selector changes but it didn't fix it (yay, wasn't my
   fault :P).
  
  
   Thanks, Sam
  
  
  
   P.S. Does anyone know about these errors in sugar-build:
  
 libEGL warning: DRI2: failed to open swrast (search paths
   /usr/lib64/dri)
  
 libEGL warning: GLX: glXQueryVersion failed
  
   They only appear on sugar-build, not epiphany (another gtk-webkit2
   browser) in gnome.
  
  
  
   --
   Daniel Narvaez
  
  
   ___
   Sugar-devel mailing list
   Sugar-devel@lists.sugarlabs.org
   http://lists.sugarlabs.org/listinfo/sugar-devel
  
  
  
  
   --
   Gonzalo Odiard
  
   SugarLabs - Software for children learning
  
  
  
 
 
  --
  Gonzalo Odiard
 
  SugarLabs - Software for children learning
  ___
  Sugar-devel mailing list
  Sugar-devel@lists.sugarlabs.org
  http://lists.sugarlabs.org/listinfo/sugar-devel




-- 
Gonzalo Odiard

SugarLabs - Software for children learning
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] Really bad web activity crashes on XO

2014-04-09 Thread Sam Parkinson
Cool, bug URL: http://bugs.sugarlabs.org/ticket/4760
On Apr 9, 2014 9:18 PM, Gonzalo Odiard godi...@sugarlabs.org wrote:

 True. Better use trac.


 On Wed, Apr 9, 2014 at 8:17 AM, Jerry Vonau m...@jvonau.ca wrote:

 How about actually using the preexisting bug tracker:

 http://bugs.sugarlabs.org

 Jerry

  On April 9, 2014 at 6:08 AM Gonzalo Odiard godi...@sugarlabs.org
 wrote:
 
 
  Would be good have these issues documented in the wiki.
 
  Gonzalo
 
 
  On Wed, Apr 9, 2014 at 7:56 AM, Sam Parkinson
  sam.parkins...@gmail.comwrote:
 
   Yep, 2048 does have css animations. Memorize web does crash too!
  
   But slides doesn't use animations, and the @font-face works a charm
   elsewhere, so I don't know what is going on there :(
  
  
   On Wed, Apr 9, 2014 at 8:43 PM, Gonzalo Odiard
   godi...@sugarlabs.orgwrote:
  
   Are you using css animations?
   Manuq reported problems with that in specific hardware
  
Can you test the Memorize web activity and see if you have the same
   error,
   when the game finish and the pieces rotate?
  
   Gonzalo
  
  
   On Wed, Apr 9, 2014 at 7:37 AM, Sam Parkinson
   sam.parkins...@gmail.comwrote:
  
   I am trying to:
   * run the 2048 Activity (
   http://activities.sugarlabs.org/en-US/sugar/addon/4738 )
   * use the 'handwritten' (notebook) theme in sugar slides (
   https://github.com/SAMdroid-apps/sugar-slides ). That theme has 2
   fonts
   to load so maybe that is it?
On Apr 9, 2014 8:11 PM, Daniel Narvaez dwnarv...@gmail.com
  wrote:
  
   The sugar-build errors sounds like missing Mesa/gl bits, which
   are probably not part of the platform yet. What are you trying to
   do?
  
   On Wednesday, 9 April 2014, Sam Parkinson 
 sam.parkins...@gmail.com
   wrote:
  
   Hi,
  
   I was trying to run a web activity on an XO with the 102 image,
 but
   no
   matter what activity I run I just get:
  
1397035392.644876 ERROR root: Using port 56277
  
   /usr/lib/python2.7/site-packages/gi/module.py:151: Warning: cannot
   register existing type `WebKitWebResource'
  
g_type = info.get_g_type()
  
   /usr/lib/python2.7/site-packages/gi/module.py:151: Warning:
   g_once_init_leave: assertion `result != 0' failed
  
g_type = info.get_g_type()
  
   /usr/lib/python2.7/site-packages/gi/module.py:155: Warning:
   g_type_get_qdata: assertion `node != NULL' failed
  
type_ = g_type.pytype
  
   /usr/lib/python2.7/site-packages/gi/module.py:195: Warning:
   g_type_get_qdata: assertion `node != NULL' failed
  
g_type.pytype = wrapper
  
   /usr/lib/python2.7/site-packages/gi/module.py:195: Warning:
   g_type_set_qdata: assertion `node != NULL' failed
  
g_type.pytype = wrapper
  
  
   This is a bit of an issue as every web activity crashes :(
  
   Does anyone have any ideas? It didn't crash on 100. I tested
   removing
   the file selector changes but it didn't fix it (yay, wasn't my
   fault :P).
  
  
   Thanks, Sam
  
  
  
   P.S. Does anyone know about these errors in sugar-build:
  
 libEGL warning: DRI2: failed to open swrast (search paths
   /usr/lib64/dri)
  
 libEGL warning: GLX: glXQueryVersion failed
  
   They only appear on sugar-build, not epiphany (another gtk-webkit2
   browser) in gnome.
  
  
  
   --
   Daniel Narvaez
  
  
   ___
   Sugar-devel mailing list
   Sugar-devel@lists.sugarlabs.org
   http://lists.sugarlabs.org/listinfo/sugar-devel
  
  
  
  
   --
   Gonzalo Odiard
  
   SugarLabs - Software for children learning
  
  
  
 
 
  --
  Gonzalo Odiard
 
  SugarLabs - Software for children learning
  ___
  Sugar-devel mailing list
  Sugar-devel@lists.sugarlabs.org
  http://lists.sugarlabs.org/listinfo/sugar-devel




 --
 Gonzalo Odiard

 SugarLabs - Software for children learning

___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] Really bad web activity crashes on XO

2014-04-09 Thread Jerry Vonau
My gut feeling is this is related to the new viewhelp.py and its import of
webkit.

Jerry

 On April 9, 2014 at 6:28 AM Sam Parkinson sam.parkins...@gmail.com
 wrote:


 Cool, bug URL: http://bugs.sugarlabs.org/ticket/4760
 On Apr 9, 2014 9:18 PM, Gonzalo Odiard godi...@sugarlabs.org wrote:

  True. Better use trac.
 
 
  On Wed, Apr 9, 2014 at 8:17 AM, Jerry Vonau m...@jvonau.ca wrote:
 
  How about actually using the preexisting bug tracker:
 
  http://bugs.sugarlabs.org
 
  Jerry
 
   On April 9, 2014 at 6:08 AM Gonzalo Odiard godi...@sugarlabs.org
  wrote:
  
  
   Would be good have these issues documented in the wiki.
  
   Gonzalo
  
  
   On Wed, Apr 9, 2014 at 7:56 AM, Sam Parkinson
   sam.parkins...@gmail.comwrote:
  
Yep, 2048 does have css animations. Memorize web does crash too!
   
But slides doesn't use animations, and the @font-face works a
charm
elsewhere, so I don't know what is going on there :(
   
   
On Wed, Apr 9, 2014 at 8:43 PM, Gonzalo Odiard
godi...@sugarlabs.orgwrote:
   
Are you using css animations?
Manuq reported problems with that in specific hardware
   
     Can you test the Memorize web activity and see if you have the
   same
error,
when the game finish and the pieces rotate?
   
Gonzalo
   
   
On Wed, Apr 9, 2014 at 7:37 AM, Sam Parkinson
sam.parkins...@gmail.comwrote:
   
I am trying to:
* run the 2048 Activity (
http://activities.sugarlabs.org/en-US/sugar/addon/4738 )
* use the 'handwritten' (notebook) theme in sugar slides (
https://github.com/SAMdroid-apps/sugar-slides ). That theme has
2
fonts
to load so maybe that is it?
     On Apr 9, 2014 8:11 PM, Daniel Narvaez dwnarv...@gmail.com
   wrote:
   
The sugar-build errors sounds like missing Mesa/gl bits, which
are probably not part of the platform yet. What are you trying
to
do?
   
On Wednesday, 9 April 2014, Sam Parkinson 
  sam.parkins...@gmail.com
wrote:
   
Hi,
   
I was trying to run a web activity on an XO with the 102
image,
  but
no
matter what activity I run I just get:
   
     1397035392.644876 ERROR root: Using port 56277
   
/usr/lib/python2.7/site-packages/gi/module.py:151: Warning:
cannot
register existing type `WebKitWebResource'
   
     g_type = info.get_g_type()
   
/usr/lib/python2.7/site-packages/gi/module.py:151: Warning:
g_once_init_leave: assertion `result != 0' failed
   
     g_type = info.get_g_type()
   
/usr/lib/python2.7/site-packages/gi/module.py:155: Warning:
g_type_get_qdata: assertion `node != NULL' failed
   
     type_ = g_type.pytype
   
/usr/lib/python2.7/site-packages/gi/module.py:195: Warning:
g_type_get_qdata: assertion `node != NULL' failed
   
     g_type.pytype = wrapper
   
/usr/lib/python2.7/site-packages/gi/module.py:195: Warning:
g_type_set_qdata: assertion `node != NULL' failed
   
     g_type.pytype = wrapper
   
   
This is a bit of an issue as every web activity crashes :(
   
Does anyone have any ideas? It didn't crash on 100. I tested
removing
the file selector changes but it didn't fix it (yay, wasn't my
fault :P).
   
   
Thanks, Sam
   
   
   
P.S. Does anyone know about these errors in sugar-build:
   
      libEGL warning: DRI2: failed to open swrast (search paths
/usr/lib64/dri)
   
      libEGL warning: GLX: glXQueryVersion failed
   
They only appear on sugar-build, not epiphany (another
gtk-webkit2
browser) in gnome.
   
   
   
--
Daniel Narvaez
   
   
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
   
   
   
   
--
Gonzalo Odiard
   
SugarLabs - Software for children learning
   
   
   
  
  
   --
   Gonzalo Odiard
  
   SugarLabs - Software for children learning
   ___
   Sugar-devel mailing list
   Sugar-devel@lists.sugarlabs.org
   http://lists.sugarlabs.org/listinfo/sugar-devel
 
 
 
 
  --
  Gonzalo Odiard
 
  SugarLabs - Software for children learning
 
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] Really bad web activity crashes on XO

2014-04-09 Thread Gonzalo Odiard
I have tested removing the import and webview references in viewhelp.py and
the error continue.

Also, the helpview is in the sugar process, not in the activity process.

Just as a reference, 0.102 images are using the webkit1 implementation.
I have tested it in sugar-build and show the same error too,
this was working recently, then some change broken it recently.

Gonzalo


On Wed, Apr 9, 2014 at 8:35 AM, Jerry Vonau m...@jvonau.ca wrote:

 My gut feeling is this is related to the new viewhelp.py and its import of
 webkit.

 Jerry

  On April 9, 2014 at 6:28 AM Sam Parkinson sam.parkins...@gmail.com
  wrote:
 
 
  Cool, bug URL: http://bugs.sugarlabs.org/ticket/4760
  On Apr 9, 2014 9:18 PM, Gonzalo Odiard godi...@sugarlabs.org wrote:
 
   True. Better use trac.
  
  
   On Wed, Apr 9, 2014 at 8:17 AM, Jerry Vonau m...@jvonau.ca wrote:
  
   How about actually using the preexisting bug tracker:
  
   http://bugs.sugarlabs.org
  
   Jerry
  
On April 9, 2014 at 6:08 AM Gonzalo Odiard godi...@sugarlabs.org
   wrote:
   
   
Would be good have these issues documented in the wiki.
   
Gonzalo
   
   
On Wed, Apr 9, 2014 at 7:56 AM, Sam Parkinson
sam.parkins...@gmail.comwrote:
   
 Yep, 2048 does have css animations. Memorize web does crash too!

 But slides doesn't use animations, and the @font-face works a
 charm
 elsewhere, so I don't know what is going on there :(


 On Wed, Apr 9, 2014 at 8:43 PM, Gonzalo Odiard
 godi...@sugarlabs.orgwrote:

 Are you using css animations?
 Manuq reported problems with that in specific hardware

  Can you test the Memorize web activity and see if you have the
same
 error,
 when the game finish and the pieces rotate?

 Gonzalo


 On Wed, Apr 9, 2014 at 7:37 AM, Sam Parkinson
 sam.parkins...@gmail.comwrote:

 I am trying to:
 * run the 2048 Activity (
 http://activities.sugarlabs.org/en-US/sugar/addon/4738 )
 * use the 'handwritten' (notebook) theme in sugar slides (
 https://github.com/SAMdroid-apps/sugar-slides ). That theme has
 2
 fonts
 to load so maybe that is it?
  On Apr 9, 2014 8:11 PM, Daniel Narvaez dwnarv...@gmail.com
wrote:

 The sugar-build errors sounds like missing Mesa/gl bits, which
 are probably not part of the platform yet. What are you trying
 to
 do?

 On Wednesday, 9 April 2014, Sam Parkinson 
   sam.parkins...@gmail.com
 wrote:

 Hi,

 I was trying to run a web activity on an XO with the 102
 image,
   but
 no
 matter what activity I run I just get:

  1397035392.644876 ERROR root: Using port 56277

 /usr/lib/python2.7/site-packages/gi/module.py:151: Warning:
 cannot
 register existing type `WebKitWebResource'

  g_type = info.get_g_type()

 /usr/lib/python2.7/site-packages/gi/module.py:151: Warning:
 g_once_init_leave: assertion `result != 0' failed

  g_type = info.get_g_type()

 /usr/lib/python2.7/site-packages/gi/module.py:155: Warning:
 g_type_get_qdata: assertion `node != NULL' failed

  type_ = g_type.pytype

 /usr/lib/python2.7/site-packages/gi/module.py:195: Warning:
 g_type_get_qdata: assertion `node != NULL' failed

  g_type.pytype = wrapper

 /usr/lib/python2.7/site-packages/gi/module.py:195: Warning:
 g_type_set_qdata: assertion `node != NULL' failed

  g_type.pytype = wrapper


 This is a bit of an issue as every web activity crashes :(

 Does anyone have any ideas? It didn't crash on 100. I tested
 removing
 the file selector changes but it didn't fix it (yay, wasn't my
 fault :P).


 Thanks, Sam



 P.S. Does anyone know about these errors in sugar-build:

   libEGL warning: DRI2: failed to open swrast (search paths
 /usr/lib64/dri)

   libEGL warning: GLX: glXQueryVersion failed

 They only appear on sugar-build, not epiphany (another
 gtk-webkit2
 browser) in gnome.



 --
 Daniel Narvaez


 ___
 Sugar-devel mailing list
 Sugar-devel@lists.sugarlabs.org
 http://lists.sugarlabs.org/listinfo/sugar-devel




 --
 Gonzalo Odiard

 SugarLabs - Software for children learning



   
   
--
Gonzalo Odiard
   
SugarLabs - Software for children learning
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
  
  
  
  
   --
   Gonzalo Odiard
  
   SugarLabs - Software for children learning
  




-- 
Gonzalo Odiard

SugarLabs - Software for children learning
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org

[Sugar-devel] triage meeting

2014-04-09 Thread Walter Bender
We plan to hold a triage meeting to clean up bugs.sugarlabs.org on
Wednesday, 23 April, beginning at 9AM EST (14 UTC). We will be on
irc.freenode.net #sugar-meeting all day. Please join the fun.

--

Tenemos la intención de celebrar una reunión de triage para limpiar
bugs.sugarlabs.org el miércoles 23 de abril a partir de las 9 a.m. EST
(14 UTC). Estaremos en irc.freenode.net #sugar-meeting todo el día.
Por favor, únase a la diversión.


regards.

-walter

-- 
Walter Bender
Sugar Labs
http://www.sugarlabs.org
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] [Sur] triage meeting

2014-04-09 Thread Gonzalo Odiard
+1!


On Wed, Apr 9, 2014 at 10:10 AM, Walter Bender walter.ben...@gmail.comwrote:

 We plan to hold a triage meeting to clean up bugs.sugarlabs.org on
 Wednesday, 23 April, beginning at 9AM EST (14 UTC). We will be on
 irc.freenode.net #sugar-meeting all day. Please join the fun.

 --

 Tenemos la intención de celebrar una reunión de triage para limpiar
 bugs.sugarlabs.org el miércoles 23 de abril a partir de las 9 a.m. EST
 (14 UTC). Estaremos en irc.freenode.net #sugar-meeting todo el día.
 Por favor, únase a la diversión.


 regards.

 -walter

 --
 Walter Bender
 Sugar Labs
 http://www.sugarlabs.org
 ___
 Lista olpc-Sur
 olpc-...@lists.laptop.org
 http://lists.laptop.org/listinfo/olpc-sur




-- 
Gonzalo Odiard

SugarLabs - Software for children learning
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] triage meeting

2014-04-09 Thread Daniel Narvaez
This is an interesting blog post with a paragraph about GNOME triaging

http://afaikblog.wordpress.com/2014/04/09/enabling-participation/

Interestingly it's pretty much exactly the same approach I followed with
the triaging I had done with 0.100. It would be good to have a simple set
of rule like that written down before the meeting. I think the way we
triage has a huge impact on lowering contribution barriers,

On Wednesday, 9 April 2014, Walter Bender walter.ben...@gmail.com wrote:

 We plan to hold a triage meeting to clean up bugs.sugarlabs.org on
 Wednesday, 23 April, beginning at 9AM EST (14 UTC). We will be on
 irc.freenode.net #sugar-meeting all day. Please join the fun.

 --

 Tenemos la intención de celebrar una reunión de triage para limpiar
 bugs.sugarlabs.org el miércoles 23 de abril a partir de las 9 a.m. EST
 (14 UTC). Estaremos en irc.freenode.net #sugar-meeting todo el día.
 Por favor, únase a la diversión.


 regards.

 -walter

 --
 Walter Bender
 Sugar Labs
 http://www.sugarlabs.org
 ___
 Sugar-devel mailing list
 Sugar-devel@lists.sugarlabs.org javascript:;
 http://lists.sugarlabs.org/listinfo/sugar-devel



-- 
Daniel Narvaez
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] [IAEP] triage meeting

2014-04-09 Thread Gonzalo Odiard
On Wed, Apr 9, 2014 at 11:53 AM, Daniel Narvaez dwnarv...@gmail.com wrote:

 This is an interesting blog post with a paragraph about GNOME triaging

 http://afaikblog.wordpress.com/2014/04/09/enabling-participation/

 Interestingly it's pretty much exactly the same approach I followed with
 the triaging I had done with 0.100. It would be good to have a simple set
 of rule like that written down before the meeting. I think the way we
 triage has a huge impact on lowering contribution barriers,


+1

We need at least verify  all the Unconfirmed tickets. We can start now,
don't need wait until the triage meeting.
I assume, if the bug is confirmed, we should set:
Milestone = 0.102
Status = New

or close them if are not longer present.

Would be good if we can reset all the priorities to Unassigned,
in all the  tickets with module=Sugar,the field content does not have any
sense right now.
Then we can use the triage meeting to finish the confirmation and to set
the priorities.

What you think?

Gonzalo
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] Really bad web activity crashes on XO

2014-04-09 Thread Daniel Narvaez
Ok. Those are probably using OpenGL. I think these days support for gl
should really be in the platform, but we should probably propose and
discuss that explicitly.

On Wednesday, 9 April 2014, Sam Parkinson sam.parkins...@gmail.com wrote:

 I am trying to:
 * run the 2048 Activity (
 http://activities.sugarlabs.org/en-US/sugar/addon/4738 )
 * use the 'handwritten' (notebook) theme in sugar slides (
 https://github.com/SAMdroid-apps/sugar-slides ). That theme has 2 fonts
 to load so maybe that is it?
 On Apr 9, 2014 8:11 PM, Daniel Narvaez 
 dwnarv...@gmail.comjavascript:_e(%7B%7D,'cvml','dwnarv...@gmail.com');
 wrote:

 The sugar-build errors sounds like missing Mesa/gl bits, which
 are probably not part of the platform yet. What are you trying to do?

 On Wednesday, 9 April 2014, Sam Parkinson 
 sam.parkins...@gmail.comjavascript:_e(%7B%7D,'cvml','sam.parkins...@gmail.com');
 wrote:

 Hi,

 I was trying to run a web activity on an XO with the 102 image, but no
 matter what activity I run I just get:

  1397035392.644876 ERROR root: Using port 56277

 /usr/lib/python2.7/site-packages/gi/module.py:151: Warning: cannot
 register existing type `WebKitWebResource'

  g_type = info.get_g_type()

 /usr/lib/python2.7/site-packages/gi/module.py:151: Warning:
 g_once_init_leave: assertion `result != 0' failed

  g_type = info.get_g_type()

 /usr/lib/python2.7/site-packages/gi/module.py:155: Warning:
 g_type_get_qdata: assertion `node != NULL' failed

  type_ = g_type.pytype

 /usr/lib/python2.7/site-packages/gi/module.py:195: Warning:
 g_type_get_qdata: assertion `node != NULL' failed

  g_type.pytype = wrapper

 /usr/lib/python2.7/site-packages/gi/module.py:195: Warning:
 g_type_set_qdata: assertion `node != NULL' failed

  g_type.pytype = wrapper


 This is a bit of an issue as every web activity crashes :(

 Does anyone have any ideas? It didn't crash on 100. I tested removing
 the file selector changes but it didn't fix it (yay, wasn't my fault :P).


 Thanks, Sam



 P.S. Does anyone know about these errors in sugar-build:

   libEGL warning: DRI2: failed to open swrast (search paths
 /usr/lib64/dri)

   libEGL warning: GLX: glXQueryVersion failed

 They only appear on sugar-build, not epiphany (another gtk-webkit2
 browser) in gnome.



 --
 Daniel Narvaez



-- 
Daniel Narvaez
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] Really bad web activity crashes on XO

2014-04-09 Thread Gonzalo Odiard
I found two problems with the web activities using webkit1

The first can be solved with http://ur1.ca/h1lgy

the second with http://ur1.ca/h1lh4

I understand the first problem, but still can't understand the second.

Gonzalo


On Wed, Apr 9, 2014 at 1:44 PM, Daniel Narvaez dwnarv...@gmail.com wrote:

 Ok. Those are probably using OpenGL. I think these days support for gl
 should really be in the platform, but we should probably propose and
 discuss that explicitly.


 On Wednesday, 9 April 2014, Sam Parkinson sam.parkins...@gmail.com
 wrote:

 I am trying to:
 * run the 2048 Activity (
 http://activities.sugarlabs.org/en-US/sugar/addon/4738 )
 * use the 'handwritten' (notebook) theme in sugar slides (
 https://github.com/SAMdroid-apps/sugar-slides ). That theme has 2 fonts
 to load so maybe that is it?
 On Apr 9, 2014 8:11 PM, Daniel Narvaez dwnarv...@gmail.com wrote:

 The sugar-build errors sounds like missing Mesa/gl bits, which
 are probably not part of the platform yet. What are you trying to do?

 On Wednesday, 9 April 2014, Sam Parkinson sam.parkins...@gmail.com
 wrote:

 Hi,

 I was trying to run a web activity on an XO with the 102 image, but no
 matter what activity I run I just get:

  1397035392.644876 ERROR root: Using port 56277

 /usr/lib/python2.7/site-packages/gi/module.py:151: Warning: cannot
 register existing type `WebKitWebResource'

  g_type = info.get_g_type()

 /usr/lib/python2.7/site-packages/gi/module.py:151: Warning:
 g_once_init_leave: assertion `result != 0' failed

  g_type = info.get_g_type()

 /usr/lib/python2.7/site-packages/gi/module.py:155: Warning:
 g_type_get_qdata: assertion `node != NULL' failed

  type_ = g_type.pytype

 /usr/lib/python2.7/site-packages/gi/module.py:195: Warning:
 g_type_get_qdata: assertion `node != NULL' failed

  g_type.pytype = wrapper

 /usr/lib/python2.7/site-packages/gi/module.py:195: Warning:
 g_type_set_qdata: assertion `node != NULL' failed

  g_type.pytype = wrapper


 This is a bit of an issue as every web activity crashes :(

 Does anyone have any ideas? It didn't crash on 100. I tested removing
 the file selector changes but it didn't fix it (yay, wasn't my fault :P).


 Thanks, Sam



 P.S. Does anyone know about these errors in sugar-build:

   libEGL warning: DRI2: failed to open swrast (search paths
 /usr/lib64/dri)

   libEGL warning: GLX: glXQueryVersion failed

 They only appear on sugar-build, not epiphany (another gtk-webkit2
 browser) in gnome.



 --
 Daniel Narvaez



 --
 Daniel Narvaez


 ___
 Sugar-devel mailing list
 Sugar-devel@lists.sugarlabs.org
 http://lists.sugarlabs.org/listinfo/sugar-devel




-- 
Gonzalo Odiard

SugarLabs - Software for children learning
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] triage meeting

2014-04-09 Thread Daniel Narvaez
On Wednesday, 9 April 2014, Gonzalo Odiard godi...@sugarlabs.org wrote:


 On Wed, Apr 9, 2014 at 11:53 AM, Daniel Narvaez 
 dwnarv...@gmail.comjavascript:_e(%7B%7D,'cvml','dwnarv...@gmail.com');
  wrote:

 This is an interesting blog post with a paragraph about GNOME triaging

 http://afaikblog.wordpress.com/2014/04/09/enabling-participation/

 Interestingly it's pretty much exactly the same approach I followed with
 the triaging I had done with 0.100. It would be good to have a simple set
 of rule like that written down before the meeting. I think the way we
 triage has a huge impact on lowering contribution barriers,


 +1

 We need at least verify  all the Unconfirmed tickets. We can start now,
 don't need wait until the triage meeting.
 I assume, if the bug is confirmed, we should set:
 Milestone = 0.102
 Status = New


I wonder about Milestone. It seems like it would only be useful if we
assign different milestones to tickets and I'm not sure we can do that
without being able to allocate resources to fix them. It's also a time
consuming task.


 or close them if are not longer present.

 Would be good if we can reset all the priorities to Unassigned,
 in all the  tickets with module=Sugar,the field content does not have any
 sense right now.


Do we want to use the field? Otherwise maybe there is a way to just get rid
of it.



-- 
Daniel Narvaez
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] triage meeting

2014-04-09 Thread Walter Bender
I added a Needs Design field to the status.

-walter

On Wed, Apr 9, 2014 at 6:29 PM, Daniel Narvaez dwnarv...@gmail.com wrote:
 On Wednesday, 9 April 2014, Gonzalo Odiard godi...@sugarlabs.org wrote:


 On Wed, Apr 9, 2014 at 11:53 AM, Daniel Narvaez dwnarv...@gmail.com
 wrote:

 This is an interesting blog post with a paragraph about GNOME triaging

 http://afaikblog.wordpress.com/2014/04/09/enabling-participation/

 Interestingly it's pretty much exactly the same approach I followed with
 the triaging I had done with 0.100. It would be good to have a simple set of
 rule like that written down before the meeting. I think the way we triage
 has a huge impact on lowering contribution barriers,


 +1

 We need at least verify  all the Unconfirmed tickets. We can start now,
 don't need wait until the triage meeting.
 I assume, if the bug is confirmed, we should set:
 Milestone = 0.102
 Status = New


 I wonder about Milestone. It seems like it would only be useful if we assign
 different milestones to tickets and I'm not sure we can do that without
 being able to allocate resources to fix them. It's also a time consuming
 task.


 or close them if are not longer present.

 Would be good if we can reset all the priorities to Unassigned,
 in all the  tickets with module=Sugar,the field content does not have any
 sense right now.


 Do we want to use the field? Otherwise maybe there is a way to just get rid
 of it.



 --
 Daniel Narvaez




-- 
Walter Bender
Sugar Labs
http://www.sugarlabs.org
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] Really bad web activity crashes on XO

2014-04-09 Thread Daniel Narvaez
Is the server listening on 127.0.0.1? I wonder if the server refuses the
connection because of that. It wouldn't easily explain the fact that it
works with chrome, but maybe libsoup and chrome handles 0.0.0.0 differently.

On Wednesday, 9 April 2014, Gonzalo Odiard godi...@sugarlabs.org wrote:

 I found two problems with the web activities using webkit1

 The first can be solved with http://ur1.ca/h1lgy

 the second with http://ur1.ca/h1lh4

 I understand the first problem, but still can't understand the second.

 Gonzalo


 On Wed, Apr 9, 2014 at 1:44 PM, Daniel Narvaez 
 dwnarv...@gmail.comjavascript:_e(%7B%7D,'cvml','dwnarv...@gmail.com');
  wrote:

 Ok. Those are probably using OpenGL. I think these days support for gl
 should really be in the platform, but we should probably propose and
 discuss that explicitly.


 On Wednesday, 9 April 2014, Sam Parkinson sam.parkins...@gmail.com
 wrote:

 I am trying to:
 * run the 2048 Activity (
 http://activities.sugarlabs.org/en-US/sugar/addon/4738 )
 * use the 'handwritten' (notebook) theme in sugar slides (
 https://github.com/SAMdroid-apps/sugar-slides ). That theme has 2 fonts
 to load so maybe that is it?
 On Apr 9, 2014 8:11 PM, Daniel Narvaez dwnarv...@gmail.com wrote:

 The sugar-build errors sounds like missing Mesa/gl bits, which
 are probably not part of the platform yet. What are you trying to do?

 On Wednesday, 9 April 2014, Sam Parkinson sam.parkins...@gmail.com
 wrote:

 Hi,

 I was trying to run a web activity on an XO with the 102 image, but no
 matter what activity I run I just get:

  1397035392.644876 ERROR root: Using port 56277

 /usr/lib/python2.7/site-packages/gi/module.py:151: Warning: cannot
 register existing type `WebKitWebResource'

  g_type = info.get_g_type()

 /usr/lib/python2.7/site-packages/gi/module.py:151: Warning:
 g_once_init_leave: assertion `result != 0' failed

  g_type = info.get_g_type()

 /usr/lib/python2.7/site-packages/gi/module.py:155: Warning:
 g_type_get_qdata: assertion `node != NULL' failed

  type_ = g_type.pytype

 /usr/lib/python2.7/site-packages/gi/module.py:195: Warning:
 g_type_get_qdata: assertion `node != NULL' failed

  g_type.pytype = wrapper

 /usr/lib/python2.7/site-packages/gi/module.py:195: Warning:
 g_type_set_qdata: assertion `node != NULL' failed

  g_type.pytype = wrapper


 This is a bit of an issue as every web activity crashes :(

 Does anyone have any ideas? It didn't crash on 100. I tested removing the
 file selector changes but it didn't fix it (yay, wasn't my fault :P).


 Thanks, Sam



 P.S. Does anyone know about these errors in sugar-build:

 ___
 Sugar-devel mailing list
 Sugar-devel@lists.sugarlabs.orgjavascript:_e(%7B%7D,'cvml','Sugar-devel@lists.sugarlabs.org');
 http://lists.sugarlabs.org/listinfo/sugar-devel




 --
 Gonzalo Odiard

 SugarLabs - Software for children learning



-- 
Daniel Narvaez
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] triage meeting

2014-04-09 Thread Gonzalo Odiard
On Wed, Apr 9, 2014 at 7:29 PM, Daniel Narvaez dwnarv...@gmail.com wrote:

 On Wednesday, 9 April 2014, Gonzalo Odiard godi...@sugarlabs.org wrote:


 On Wed, Apr 9, 2014 at 11:53 AM, Daniel Narvaez dwnarv...@gmail.comwrote:

 This is an interesting blog post with a paragraph about GNOME triaging

 http://afaikblog.wordpress.com/2014/04/09/enabling-participation/

 Interestingly it's pretty much exactly the same approach I followed with
 the triaging I had done with 0.100. It would be good to have a simple set
 of rule like that written down before the meeting. I think the way we
 triage has a huge impact on lowering contribution barriers,


 +1

 We need at least verify  all the Unconfirmed tickets. We can start now,
 don't need wait until the triage meeting.
 I assume, if the bug is confirmed, we should set:
 Milestone = 0.102
 Status = New


 I wonder about Milestone. It seems like it would only be useful if we
 assign different milestones to tickets and I'm not sure we can do that
 without being able to allocate resources to fix them. It's also a time
 consuming task.


True.




 or close them if are not longer present.

 Would be good if we can reset all the priorities to Unassigned,
 in all the  tickets with module=Sugar,the field content does not have any
 sense right now.


 Do we want to use the field? Otherwise maybe there is a way to just get
 rid of it.



Just to mark they have been  triaged, and based in the querys used in
bugs.sugarlabs.org home.
Do you propose doing in another way?


-- 
Gonzalo Odiard

SugarLabs - Software for children learning
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] triage meeting

2014-04-09 Thread Daniel Narvaez
On Thursday, 10 April 2014, Gonzalo Odiard godi...@sugarlabs.org wrote:




 On Wed, Apr 9, 2014 at 7:29 PM, Daniel Narvaez 
 dwnarv...@gmail.comjavascript:_e(%7B%7D,'cvml','dwnarv...@gmail.com');
  wrote:

 On Wednesday, 9 April 2014, Gonzalo Odiard 
 godi...@sugarlabs.orgjavascript:_e(%7B%7D,'cvml','godi...@sugarlabs.org');
 wrote:


 On Wed, Apr 9, 2014 at 11:53 AM, Daniel Narvaez dwnarv...@gmail.comwrote:

 This is an interesting blog post with a paragraph about GNOME triaging

 http://afaikblog.wordpress.com/2014/04/09/enabling-participation/

 Interestingly it's pretty much exactly the same approach I followed
 with the triaging I had done with 0.100. It would be good to have a simple
 set of rule like that written down before the meeting. I think the way we
 triage has a huge impact on lowering contribution barriers,


 +1

 We need at least verify  all the Unconfirmed tickets. We can start
 now, don't need wait until the triage meeting.
 I assume, if the bug is confirmed, we should set:
 Milestone = 0.102
 Status = New


 I wonder about Milestone. It seems like it would only be useful if we
 assign different milestones to tickets and I'm not sure we can do that
 without being able to allocate resources to fix them. It's also a time
 consuming task.


 True.




 or close them if are not longer present.

 Would be good if we can reset all the priorities to Unassigned,
 in all the  tickets with module=Sugar,the field content does not have
 any sense right now.


 Do we want to use the field? Otherwise maybe there is a way to just get
 rid of it.



 Just to mark they have been  triaged, and based in the querys used in
 bugs.sugarlabs.org home.
 Do you propose doing in another way?


The home queries uses status == unconfirmed for untriaged. The tickets I
set status = new (not that many left) have been confirmed. I had reset
everything to unconfirmed before starting to triage.


-- 
Daniel Narvaez
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] triage meeting

2014-04-09 Thread Daniel Narvaez
Finally, something I think is important is to set enhancement vs defect. It
doesn't take much effort and it's very useful when we are feature frozen.

On Thursday, 10 April 2014, Daniel Narvaez dwnarv...@gmail.com wrote:

 Something else to consider is what to do with priorities. It might make
 sense to set one when confirming bugs, it's hard to get right without
 spending a lot of time really but maybe helpful for contributors even if
 not very accurate.

 On Thursday, 10 April 2014, Daniel Narvaez 
 dwnarv...@gmail.comjavascript:_e(%7B%7D,'cvml','dwnarv...@gmail.com');
 wrote:



 On Thursday, 10 April 2014, Gonzalo Odiard godi...@sugarlabs.org wrote:




 On Wed, Apr 9, 2014 at 7:29 PM, Daniel Narvaez dwnarv...@gmail.comwrote:

 On Wednesday, 9 April 2014, Gonzalo Odiard godi...@sugarlabs.org
 wrote:


 On Wed, Apr 9, 2014 at 11:53 AM, Daniel Narvaez 
 dwnarv...@gmail.comwrote:

 This is an interesting blog post with a paragraph about GNOME triaging

 http://afaikblog.wordpress.com/2014/04/09/enabling-participation/

 Interestingly it's pretty much exactly the same approach I followed
 with the triaging I had done with 0.100. It would be good to have a 
 simple
 set of rule like that written down before the meeting. I think the way we
 triage has a huge impact on lowering contribution barriers,


 +1

 We need at least verify  all the Unconfirmed tickets. We can start
 now, don't need wait until the triage meeting.
 I assume, if the bug is confirmed, we should set:
 Milestone = 0.102
 Status = New


 I wonder about Milestone. It seems like it would only be useful if we
 assign different milestones to tickets and I'm not sure we can do that
 without being able to allocate resources to fix them. It's also a time
 consuming task.


 True.




 or close them if are not longer present.

 Would be good if we can reset all the priorities to Unassigned,
 in all the  tickets with module=Sugar,the field content does not have
 any sense right now.


 Do we want to use the field? Otherwise maybe there is a way to just get
 rid of it.



 Just to mark they have been  triaged, and based in the querys used in
 bugs.sugarlabs.org home.
 Do you propose doing in another way?


 The home queries uses status == unconfirmed for untriaged. The tickets I
 set status = new (not that many left) have been confirmed. I had reset
 everything to unconfirmed before starting to triage.


 --
 Daniel Narvaez



 --
 Daniel Narvaez



-- 
Daniel Narvaez
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] triage meeting

2014-04-09 Thread Walter Bender
On Wed, Apr 9, 2014 at 9:21 PM, Daniel Narvaez dwnarv...@gmail.com wrote:
 Something else to consider is what to do with priorities. It might make
 sense to set one when confirming bugs, it's hard to get right without
 spending a lot of time really but maybe helpful for contributors even if not
 very accurate.

I think we have too many categories for priorities: IMHO, either it is
a blocker or it is not.

-walter


 On Thursday, 10 April 2014, Daniel Narvaez dwnarv...@gmail.com wrote:



 On Thursday, 10 April 2014, Gonzalo Odiard godi...@sugarlabs.org wrote:




 On Wed, Apr 9, 2014 at 7:29 PM, Daniel Narvaez dwnarv...@gmail.com
 wrote:

 On Wednesday, 9 April 2014, Gonzalo Odiard godi...@sugarlabs.org
 wrote:


 On Wed, Apr 9, 2014 at 11:53 AM, Daniel Narvaez dwnarv...@gmail.com
 wrote:

 This is an interesting blog post with a paragraph about GNOME triaging

 http://afaikblog.wordpress.com/2014/04/09/enabling-participation/

 Interestingly it's pretty much exactly the same approach I followed
 with the triaging I had done with 0.100. It would be good to have a 
 simple
 set of rule like that written down before the meeting. I think the way we
 triage has a huge impact on lowering contribution barriers,


 +1

 We need at least verify  all the Unconfirmed tickets. We can start
 now, don't need wait until the triage meeting.
 I assume, if the bug is confirmed, we should set:
 Milestone = 0.102
 Status = New


 I wonder about Milestone. It seems like it would only be useful if we
 assign different milestones to tickets and I'm not sure we can do that
 without being able to allocate resources to fix them. It's also a time
 consuming task.


 True.




 or close them if are not longer present.

 Would be good if we can reset all the priorities to Unassigned,
 in all the  tickets with module=Sugar,the field content does not have
 any sense right now.


 Do we want to use the field? Otherwise maybe there is a way to just get
 rid of it.



 Just to mark they have been  triaged, and based in the querys used in
 bugs.sugarlabs.org home.
 Do you propose doing in another way?


 The home queries uses status == unconfirmed for untriaged. The tickets I
 set status = new (not that many left) have been confirmed. I had reset
 everything to unconfirmed before starting to triage.


 --
 Daniel Narvaez



 --
 Daniel Narvaez




-- 
Walter Bender
Sugar Labs
http://www.sugarlabs.org
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] triage meeting

2014-04-09 Thread Gonzalo Odiard
+1 to check if are enhancements or defects.

About priorities, we can make something like:

blocker: regressions, crashes, serious bugs

major: bugs affecting the usability

minor: other

Just a idea to start to discuss.

Gonzalo



On Wed, Apr 9, 2014 at 10:24 PM, Walter Bender walter.ben...@gmail.comwrote:

 On Wed, Apr 9, 2014 at 9:21 PM, Daniel Narvaez dwnarv...@gmail.com
 wrote:
  Something else to consider is what to do with priorities. It might make
  sense to set one when confirming bugs, it's hard to get right without
  spending a lot of time really but maybe helpful for contributors even if
 not
  very accurate.

 I think we have too many categories for priorities: IMHO, either it is
 a blocker or it is not.

 -walter
 
 
  On Thursday, 10 April 2014, Daniel Narvaez dwnarv...@gmail.com wrote:
 
 
 
  On Thursday, 10 April 2014, Gonzalo Odiard godi...@sugarlabs.org
 wrote:
 
 
 
 
  On Wed, Apr 9, 2014 at 7:29 PM, Daniel Narvaez dwnarv...@gmail.com
  wrote:
 
  On Wednesday, 9 April 2014, Gonzalo Odiard godi...@sugarlabs.org
  wrote:
 
 
  On Wed, Apr 9, 2014 at 11:53 AM, Daniel Narvaez dwnarv...@gmail.com
 
  wrote:
 
  This is an interesting blog post with a paragraph about GNOME
 triaging
 
  http://afaikblog.wordpress.com/2014/04/09/enabling-participation/
 
  Interestingly it's pretty much exactly the same approach I followed
  with the triaging I had done with 0.100. It would be good to have a
 simple
  set of rule like that written down before the meeting. I think the
 way we
  triage has a huge impact on lowering contribution barriers,
 
 
  +1
 
  We need at least verify  all the Unconfirmed tickets. We can start
  now, don't need wait until the triage meeting.
  I assume, if the bug is confirmed, we should set:
  Milestone = 0.102
  Status = New
 
 
  I wonder about Milestone. It seems like it would only be useful if we
  assign different milestones to tickets and I'm not sure we can do that
  without being able to allocate resources to fix them. It's also a time
  consuming task.
 
 
  True.
 
 
 
 
  or close them if are not longer present.
 
  Would be good if we can reset all the priorities to Unassigned,
  in all the  tickets with module=Sugar,the field content does not have
  any sense right now.
 
 
  Do we want to use the field? Otherwise maybe there is a way to just
 get
  rid of it.
 
 
 
  Just to mark they have been  triaged, and based in the querys used in
  bugs.sugarlabs.org home.
  Do you propose doing in another way?
 
 
  The home queries uses status == unconfirmed for untriaged. The tickets I
  set status = new (not that many left) have been confirmed. I had reset
  everything to unconfirmed before starting to triage.
 
 
  --
  Daniel Narvaez
 
 
 
  --
  Daniel Narvaez
 



 --
 Walter Bender
 Sugar Labs
 http://www.sugarlabs.org




-- 
Gonzalo Odiard

SugarLabs - Software for children learning
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel