Re: Proposal: the 'faster' branch.

[david]

On Fri, 8 Feb 2008, C. Scott Ananian wrote:

> So: welcome the 'faster' branch, a repository for all these unsafe
> ideas.  It will be completely untested and may eat your machine.  But
> let's see how fast we could make things if we allowed all our evil
> hacks, and *then* step back and evaluate which of these turned out to
> be useful and which of these are (still) too expensive or ugly to try.
> Nothing in 'faster' in guaranteed to make it into our stable branch,
> ever.  But perhaps it will help show us the way forward.
>
> Faster is set up like joyride.  Put rpms in dev:~/public_rpms/faster.
> Please keep your ugly hacks safely separate from code you intend real
> people to use.  Discuss.  Enjoy.
> --scott

so what do g1g1 testers need to do to upgrade to these builds? is there a 
olpc-update incantation that will install these?

will the announcements for releases here be sent out like the joyride 
builds are?

David Lang
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: New update.1 build 691

[Kim Quirk]

Mako and Bert,
I added a note to the Roadmap for Update.1, to discuss these items for
inclusion in the final release of Update.1. If it doesn't take place before
the Wed SW meeting, it should happen then. 2pm EST, irc.

Dennis,
I think it would be best if you could help drive this process for the items
that people have marked as Request for Update.1, but may have fallen through
the cracks. Would it be possible for you to find the 'request for Update1'
items a few days ahead of time and try to figure out what is needed for them
to make it (such as a critical trac bug); and if there is questions on
whether or not it should go in, then you can a least alert the person to the
discussion so they have a chance to argue their case.

Is this reasonable? Or another suggestion?

We hope to have the final release candidate by the end of next week -- so I
think that means we only want one more build.

Also, the items that are still open on the Roadmap are going to get their
final review and be moved to the next release unless someone is willing to
make a good argument. Please review.

Thanks,
Kim



On Feb 8, 2008 9:46 PM, Jim Gettys <[EMAIL PROTECTED]> wrote:

> Did you do a "request for update" in trac? Without that, we have no way
> to know if your testing in joyride has completed.
>  - Jim
>
> On Fri, 2008-02-08 at 19:53 -0500, Benj. Mako Hill wrote:
> > 
> > > http://pilgrim.laptop.org/~pilgrim/olpc/streams/update.1/build691
> >
> > Is there a reason that the approved olpc-library-common and -core
> > packages were not in? The fixes aren't to critical bugs but they are
> > also not to software.
> >
> > As #6371 says, they clean up CSS and text in the content pacakges.  It's
> > not clear to me if this is being treated like software or like
> > translations but it would be good to have it communicated either way
> > and in the build as soon as possible.
> >
> > Regards,
> > Mako
> >
> >
> > ___
> > Devel mailing list
> > Devel@lists.laptop.org
> > http://lists.laptop.org/listinfo/devel
> --
> Jim Gettys
> One Laptop Per Child
>
>
> ___
> Devel mailing list
> Devel@lists.laptop.org
> http://lists.laptop.org/listinfo/devel
>
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: New update.1 build 691

[Kim Quirk]

Ricardo,
Can you add this 'enable wireless debug' info to the Test Config Notes:
http://wiki.laptop.org/go/Test_Config_Notes

Thanks!
Kim


On Feb 8, 2008 7:35 PM, Ricardo Carrano <[EMAIL PROTECTED]> wrote:

>
> Ricardo,
> > Can you tell us what method of update (cleaninstall or network upgrade)
> > you did and if your WEP and WPA just came up working, or if there is any
> > sort of reboots, etc. needed.
> >
>
> I updated via network (olpc-update) and no extra reboots were necessary.
> WEP, which was broken since 656, worked immediately.
>
> WPA _continued_ to work. If an update to 691 _causes_ WPA to work, then it
> is a question of what was the previous version.
>
> But more important, I believe, is the fact that WPA not always work for
> some APs. Though this is not unusual in  many devices (not only on the XO)
> the next step would be to determine which APs and WPA versions (encryption
> and authentication methods) are problematic.
>
> So, enabling debug...
> echo 0x6180 > /sys/module/libertas/parameters/libertas_debug
>
> ... and sending dmesg outputs  to a filed WPA bug, can be useful.
>
> -- RC
>
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: New update.1 build 691

[Jim Gettys]

Did you do a "request for update" in trac? Without that, we have no way
to know if your testing in joyride has completed.
  - Jim

On Fri, 2008-02-08 at 19:53 -0500, Benj. Mako Hill wrote:
> 
> > http://pilgrim.laptop.org/~pilgrim/olpc/streams/update.1/build691
> 
> Is there a reason that the approved olpc-library-common and -core
> packages were not in? The fixes aren't to critical bugs but they are
> also not to software.
> 
> As #6371 says, they clean up CSS and text in the content pacakges.  It's
> not clear to me if this is being treated like software or like
> translations but it would be good to have it communicated either way
> and in the build as soon as possible.
> 
> Regards,
> Mako
> 
> 
> ___
> Devel mailing list
> Devel@lists.laptop.org
> http://lists.laptop.org/listinfo/devel
-- 
Jim Gettys
One Laptop Per Child


___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: New update.1 build 691

[Benj. Mako Hill]

> http://pilgrim.laptop.org/~pilgrim/olpc/streams/update.1/build691

Is there a reason that the approved olpc-library-common and -core
packages were not in? The fixes aren't to critical bugs but they are
also not to software.

As #6371 says, they clean up CSS and text in the content pacakges.  It's
not clear to me if this is being treated like software or like
translations but it would be good to have it communicated either way
and in the build as soon as possible.

Regards,
Mako


-- 
Benjamin Mako Hill
[EMAIL PROTECTED]
http://mako.cc/


signature.asc
Description: Digital signature
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: New update.1 build 691

[Ricardo Carrano]

> Ricardo,
> Can you tell us what method of update (cleaninstall or network upgrade)
> you did and if your WEP and WPA just came up working, or if there is any
> sort of reboots, etc. needed.
>

I updated via network (olpc-update) and no extra reboots were necessary.
WEP, which was broken since 656, worked immediately.

WPA _continued_ to work. If an update to 691 _causes_ WPA to work, then it
is a question of what was the previous version.

But more important, I believe, is the fact that WPA not always work for some
APs. Though this is not unusual in  many devices (not only on the XO) the
next step would be to determine which APs and WPA versions (encryption and
authentication methods) are problematic.

So, enabling debug...
echo 0x6180 > /sys/module/libertas/parameters/libertas_debug

... and sending dmesg outputs  to a filed WPA bug, can be useful.

-- RC
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: Please test update.1 rc2.

[Kim Quirk]

Calling all Testers!

This release candidate is available and ready for serious testing, build
691. Before Chih-yu left the office she pulled together some wiki pages with
test cases and a place to record some results.

Please take a look - help refine and create test cases - or help test and
record some results!!

http://wiki.laptop.org/go/Update.1

Also see (and add to) the high level release notes - add info that is
helpful to others who are thinking about testing.
http://wiki.laptop.org/go/Test_Group_Release_Notes

Please add real bugs to TRAC.

Thanks!!
Kim


On Feb 8, 2008 6:01 PM, C. Scott Ananian <[EMAIL PROTECTED]> wrote:

> Signed builds for update.1 rc2 (build 691) are now available at:
>   http://download.laptop.org/xo-1/os/candidate/691/jffs2/
>
> You can also 'olpc-update candidate-691', which will get the signed build.
>
> Release notes at:
>
> http://wiki.laptop.org/go/Test_Group_Release_Notes#Build_691_Q2D13_.28RC2.29
>
> Please test and file bugs!
>  --scott
>
> --
> ( http://cscott.net/ )
> ___
> Devel mailing list
> Devel@lists.laptop.org
> http://lists.laptop.org/listinfo/devel
>
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: status of startup speedup

[Tomeu Vizoso]

On Fri, 2008-02-08 at 14:23 -0500, Michael Stone wrote:
> Tomeu,
> 
> > The only remaining issue is that activities cannot update their journal
> > entries. They are able to create the entries in the datastore, but the
> > second call to the DS service fails. 
> 
> Please publish the traceback so that I can help you debug the situation.

Well, it just times out and the message doesn't arrive to the DS
service. But I'll reproduce and attach the traceback tomorrow.

> Next, some notes and some questions about your patch:

I guess I was not clear on this, but this patch is not something I would
ask to be applied to upstream rainbow. I just intended to experiment
with the idea of a launcher process and see which improvements and
problems we would find.

> * In the second hunk, I'd like to replace the big os.environ block with
>   something like:
> 
> for key in (...):
> os.environ[key] = env[key]
> 
>   That being said, is there a good reason for selectively using values from
>   os.environ instead of using everything?

No, I just wanted to know which env vars were really needed. We can add
all of those if you think it's better.

> * By convention, the first argument to log() should be a format string.
> 
> * I think your patch breaks rainbow's strace support. Strace support can
>   probably be fixed by forking a second time, then instructing strace to trace
>   to the pid of the parent; however, this will lead to interleaved writes to
>   the shared file descriptors.
> 
> * Why is it necessary to import gtk twice?

Well, we import first in the parent process so the initialization is
inherited by all children. The second time is just because we need to
reopen the connection to X (and need a gtk name in that scope).

> * I am extremely uncomfortable importing all of telepathy, sugar, dbus, and 
> gtk
>   into the main rainbow process before it has dropped privilege. 
> Unfortunately,
>   we must drop privilege after forking and the imports must be done before
>   forking. (Also, unfortunately, all of sugar, telepathy, and the datastore
>   have root access through sudo. I'll be trying to change this in coming
>   weeks.)

Of course. I guess we could have a launcher process that does the
preloading of expensive modules and then fork?

> * Rainbow is currently made available under the MIT license. You offered your
>   sugaractivity.py file under the GPL2+ license. Are you willing to offer it
>   under the MIT license?

That's not my code, it is mostly Marco's. I don't have any problem with
having my work as MIT.

> Anyhow, thanks very much for your hard work,

Thanks for your help.

Tomeu

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Please test update.1 rc2.

[C. Scott Ananian]

Signed builds for update.1 rc2 (build 691) are now available at:
   http://download.laptop.org/xo-1/os/candidate/691/jffs2/

You can also 'olpc-update candidate-691', which will get the signed build.

Release notes at:
   http://wiki.laptop.org/go/Test_Group_Release_Notes#Build_691_Q2D13_.28RC2.29

Please test and file bugs!
 --scott

-- 
 ( http://cscott.net/ )
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: New update.1 build 691

[Bert Freudenberg]

On Feb 8, 2008, at 19:13 , Dennis Gilmore wrote:

>> On Fri, 2008-02-08 at 08:56 -0600, Dennis Gilmore wrote:
>>> On Friday 08 February 2008, Bert Freudenberg wrote:
 This cannot possibly be RC2 because not all approved packages  
 are in.
 Etoys for example.
>>>
>>> I held etoys out because i dont know what critical bug it fixes.
>>>
>>> Dennis
> That is a perfectly acceptable reason  the bug report did not state  
> anything
> other than please include it.
>
> It will get picked up in the next build along with all the other  
> translations.


Fine.

However, why did you ask that question only after the build was made,  
when the package was approved one week ago? There would have been  
enough time to discuss it.

And secondly, what *is* the current policy of package inclusion? I  
was under the impression that getting approval from Jim/Kim/Walter  
was enough. But now we have to convince you, too? What could be  
possibly broken in the system by a new activity release? And who else  
would be authoritative on whether that activity works as intended if  
not its authors?

- Bert -

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: New update.1 build 691

[Gary Oberbrunner]

Kim Quirk wrote:
> Gary,
> Did you upgrade to 691 via olpc-update?

Yes.  It said there were some inconsistencies and had to do a 
longer-form installation; I then thought I saw some other errors but 
unless they're logged somewhere, they're gone.  But the update did 
appear to succeed (new firmware, other fixes etc.)

> If so, can you remove your /home/olpc/.sugar/default/nm/network.cfg file 
> and reboot? I had to do this to get my WPA connection to work. I haven't 
> been able to test WEP with this build, but I wouldn't be surprised if it 
> is similar.

At some point I did do this.  I'm now using a "fresh" network.cfg, and 
things are mostly good (except as I said on each initial startup).

-- Gary

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: New update.1 build 691

[Kim Quirk]

Gary,
Did you upgrade to 691 via olpc-update?

If so, can you remove your /home/olpc/.sugar/default/nm/network.cfg file and
reboot? I had to do this to get my WPA connection to work. I haven't been
able to test WEP with this build, but I wouldn't be surprised if it is
similar.

Ricardo,
Can you tell us what method of update (cleaninstall or network upgrade) you
did and if your WEP and WPA just came up working, or if there is any sort of
reboots, etc. needed.


I have added some note in the "Test Group Release Notes":
http://wiki.laptop.org/go/Test_Group_Release_Notes

To capture the high level of what works. Please add / modify as needed.

Thanks,
Kim


On Feb 7, 2008 10:33 PM, Gary Oberbrunner <[EMAIL PROTECTED]> wrote:

> ffm wrote:
> > I take it this is RC2?
> >
> > Does WEP work yet?
>
> Actually it mostly does for me, now.  (WPA actually).  I had to reboot a
> few times after the upgrade, but after that clicking on the WPA ap
> usually works.  It doesn't autoconnect after a reboot (it tries though).
>  But after that I can click on the AP and it connects OK usually.
>
> -- Gary
> ___
> Devel mailing list
> Devel@lists.laptop.org
> http://lists.laptop.org/listinfo/devel
>
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Proposal: the 'faster' branch.

[C. Scott Ananian]

There are a number of high risk changes which seem necessary to get
the performance we would like from our builds.   In addition to
tomeu's recent rainbow patches, I could list: partitioning the root
filesystem, using logfs/jffs3/ufs instead of jffs2 for our
filesystems, starting X as early as possible in the boot process,
radically trimming the udev rule list, radically trimming the
initscript and rc.sysinit, rewriting portions of sugar in C, and
others.

There are all "bad ideas" in various ways: they may introduce
divergences from upstream, their savings are unproven, they may add to
our support problems in the field, they may involve immature
technologies.  But (IMO) it's time to stop being scared and see what
we could do if all the fetters were off.

So: welcome the 'faster' branch, a repository for all these unsafe
ideas.  It will be completely untested and may eat your machine.  But
let's see how fast we could make things if we allowed all our evil
hacks, and *then* step back and evaluate which of these turned out to
be useful and which of these are (still) too expensive or ugly to try.
 Nothing in 'faster' in guaranteed to make it into our stable branch,
ever.  But perhaps it will help show us the way forward.

Faster is set up like joyride.  Put rpms in dev:~/public_rpms/faster.
Please keep your ugly hacks safely separate from code you intend real
people to use.  Discuss.  Enjoy.
 --scott

p.s. Michael Stone asked me a question before I'd managed to send this
out, so I'll answer him here for all of you: 'Faster' code is not
intended to be put into joyride or stable ever.  The idea is, don't
waste (too much) time (yet) doing things the "right" way.  Just hack
up the code and show us what's possible.  Once we're convinced that we
can get (say) boot time down to less than a second, we can figure out
how to clean up the hacks and make things work for real/in a
maintainable fashion.  But 'faster' is specifically for dirty hacks
and proofs-of-concept.

-- 
 ( http://cscott.net/ )
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: status of startup speedup

[C. Scott Ananian]

These changes seem appropriate for the 'faster' build (see next
message on devel@).
 --scott

-- 
 ( http://cscott.net/ )
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: [Localization] Updating translations for release...

[Rafael Enrique Ortiz Guerrero]

Hi all,

Talking about Spanish fuzzy strings i have been working  to unfuzzy  all of
them,,
i have  a few that still need reviewing but the majority are now unfuzzy.
i expect to complete the process or most of it before monday.




On Feb 8, 2008 2:17 PM, Jim Gettys <[EMAIL PROTECTED]> wrote:

> Seems like a plan.
>
> Translators, please unfuzz your strings!  This is particularly important
> for Spanish, which seems to be suffering with a lot of time...
> - Jim
>
> On Fri, 2008-02-08 at 22:38 +0530, Sayamindu Dasgupta wrote:
> > Hi,
> >
> > On Feb 8, 2008 5:10 PM, Jim Gettys <[EMAIL PROTECTED]> wrote:
> > > The time has come to get the activities updated with Update.1
> > > translations.  How do we stand?
> > >
> >
> > I have done extensive testing with Spanish and Mongolian, and they
> > seem to be good to go.
> >
> > > We can't wait any longer to speak of. I think we need to pick a
> definite
> > > date and time for the completion of this, no later than, say, Monday,
> > > and anything untranslated stays untranslated.  We have to be able to
> > > move on to working on our next release.
> > >
> >
> > Agree thoroughly. Monday is the date.
> >
> > > 1) Can the activities be updated by you updating the packages, or will
> > > this require work by the activity developers?
> > >
> >
> > Yes one can simply do a git pull from dev.laptop.org and the latest
> > translations will go in.
> >
> > > 2) I gather we have to update Sugar to fix a problem or two to get the
> > > translations to stick.  Are there any other activities in a similar
> > > situation, that will require code updates as well as translations?
> > >
> >
> > Not that I know of (except for Sugar). TurtleArt has a spelling
> > mistake which you might want to fix. However, the build system does
> > not pick up all translations - see #6179
> >
> > > 3) Fuzzy strings.  What's left to un-fuzz them?
> > >
> >
> > It depends on the translators - I request all translators to got
> > through their fuzzy strings during the weekend if possible, and unfuzz
> > them. Messages which remain fuzzy on Monday  will not be compiled in.
> >
> > > 4) fonts: are there any additional fonts that need to be added?  If
> so,
> > > what are their packages, their licenses, and their sizes?  Does Dennis
> > > know what languages are to go into the image?
> > >
> >
> > Depends on #6179 (ie, which languages go into the image). I believe we
> > cover all the languages that are currently defined in Sugar Control
> > Panel - but I'll stilll go through them and verify by Sunday.
> >
> > > 5) I noticed some mail go by that certain mis-coding could cause
> > > activities to crash.  How do we get those fixed?
> > >
> >
> > Hmm - tough question :-). I'll try to fix those by hand (most of them
> > are syntax errors). But this will take some time, and I'll probably
> > finish by Sunday night (IST). So any package update has to be _after_
> > that. Does that sound viable ?
>
> Yes.
>
> >
> >
> > Thank you,
> > Sayamindu
> >
> >
> --
> Jim Gettys
> One Laptop Per Child
>
>
> ___
> Localization mailing list
> [EMAIL PROTECTED]
> http://lists.laptop.org/listinfo/localization
>



-- 
Rafael Enrique Ortiz Guerrero
One Laptop Per Child
[EMAIL PROTECTED]
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: status of startup speedup

[Michael Stone]

Tomeu,

> The only remaining issue is that activities cannot update their journal
> entries. They are able to create the entries in the datastore, but the
> second call to the DS service fails. 

Please publish the traceback so that I can help you debug the situation.

Next, some notes and some questions about your patch:

* In the second hunk, I'd like to replace the big os.environ block with
  something like:

for key in (...):
os.environ[key] = env[key]

  That being said, is there a good reason for selectively using values from
  os.environ instead of using everything?

* By convention, the first argument to log() should be a format string.

* I think your patch breaks rainbow's strace support. Strace support can
  probably be fixed by forking a second time, then instructing strace to trace
  to the pid of the parent; however, this will lead to interleaved writes to
  the shared file descriptors.

* Why is it necessary to import gtk twice?

* I am extremely uncomfortable importing all of telepathy, sugar, dbus, and gtk
  into the main rainbow process before it has dropped privilege. Unfortunately,
  we must drop privilege after forking and the imports must be done before
  forking. (Also, unfortunately, all of sugar, telepathy, and the datastore
  have root access through sudo. I'll be trying to change this in coming
  weeks.)
  
* Rainbow is currently made available under the MIT license. You offered your
  sugaractivity.py file under the GPL2+ license. Are you willing to offer it
  under the MIT license?

Anyhow, thanks very much for your hard work,

Michael


___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: Updating translations for release...

[Jim Gettys]

Seems like a plan.

Translators, please unfuzz your strings!  This is particularly important
for Spanish, which seems to be suffering with a lot of time...
 - Jim

On Fri, 2008-02-08 at 22:38 +0530, Sayamindu Dasgupta wrote:
> Hi,
> 
> On Feb 8, 2008 5:10 PM, Jim Gettys <[EMAIL PROTECTED]> wrote:
> > The time has come to get the activities updated with Update.1
> > translations.  How do we stand?
> >
> 
> I have done extensive testing with Spanish and Mongolian, and they
> seem to be good to go.
> 
> > We can't wait any longer to speak of. I think we need to pick a definite
> > date and time for the completion of this, no later than, say, Monday,
> > and anything untranslated stays untranslated.  We have to be able to
> > move on to working on our next release.
> >
> 
> Agree thoroughly. Monday is the date.
> 
> > 1) Can the activities be updated by you updating the packages, or will
> > this require work by the activity developers?
> >
> 
> Yes one can simply do a git pull from dev.laptop.org and the latest
> translations will go in.
> 
> > 2) I gather we have to update Sugar to fix a problem or two to get the
> > translations to stick.  Are there any other activities in a similar
> > situation, that will require code updates as well as translations?
> >
> 
> Not that I know of (except for Sugar). TurtleArt has a spelling
> mistake which you might want to fix. However, the build system does
> not pick up all translations - see #6179
> 
> > 3) Fuzzy strings.  What's left to un-fuzz them?
> >
> 
> It depends on the translators - I request all translators to got
> through their fuzzy strings during the weekend if possible, and unfuzz
> them. Messages which remain fuzzy on Monday  will not be compiled in.
> 
> > 4) fonts: are there any additional fonts that need to be added?  If so,
> > what are their packages, their licenses, and their sizes?  Does Dennis
> > know what languages are to go into the image?
> >
> 
> Depends on #6179 (ie, which languages go into the image). I believe we
> cover all the languages that are currently defined in Sugar Control
> Panel - but I'll stilll go through them and verify by Sunday.
> 
> > 5) I noticed some mail go by that certain mis-coding could cause
> > activities to crash.  How do we get those fixed?
> >
> 
> Hmm - tough question :-). I'll try to fix those by hand (most of them
> are syntax errors). But this will take some time, and I'll probably
> finish by Sunday night (IST). So any package update has to be _after_
> that. Does that sound viable ?

Yes.

> 
> 
> Thank you,
> Sayamindu
> 
> 
-- 
Jim Gettys
One Laptop Per Child


___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

New joyride build 1664

[Build Announcer v2]

http://xs-dev.laptop.org/~cscott/olpc/streams/joyride/build1664

Changes in build 1664 from build: 1658

Size delta: 3.28M

+TurtleArtwithSensors 3

--- Included TurtleArtwithSensors version 3 ---

--
This mail was automatically generated
See http://dev.laptop.org/~rwh/announcer/joyride-pkgs.html for aggregate logs
See http://dev.laptop.org/~rwh/announcer/joyride_vs_update1.html for a 
comparison
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

status of startup speedup

[Tomeu Vizoso]

Hi,

attached is a patch to rainbow for executing python activities inside a
forked child.

This saves quite a bit of the initializing code, taking a 7s. activity
to start in 3. Perhaps we could preload some more initializations.

Haven't even looked yet at possible memory savings.

The only remaining issue is that activities cannot update their journal
entries. They are able to create the entries in the datastore, but the
second call to the DS service fails. Tomorrow will look at this if
nobody beats me to it.

Thanks,

Tomeu




0001-Some-hacks-for-preloading-some-modules-and-then-exec.patch
Description: application/mbox
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: New update.1 build 691

[Dennis Gilmore]

On Friday 08 February 2008, Jim Gettys wrote:
> An updated etoys to pick up as much Spanish (and other languages) as we
> can will is definitely necessary; whether we call this update.1 RC3 or
> update.1.1 is all the same to me: updating all the activities to pick up
> the languages is in the immediate future.
>   - Jim
>
> On Fri, 2008-02-08 at 08:56 -0600, Dennis Gilmore wrote:
> > On Friday 08 February 2008, Bert Freudenberg wrote:
> > > Am Feb 8, 2008 um 0:46 schrieb "C. Scott Ananian" <[EMAIL PROTECTED]>:
> > > > 2008/2/7 ffm <[EMAIL PROTECTED]>:
> > > >> I take it this is RC2?
> > > >>
> > > >> Does WEP work yet?
> > > >
> > > > This will be RC2
> > >
> > > This cannot possibly be RC2 because not all approved packages are in.
> > > Etoys for example.
> >
> > I held etoys out because i dont know what critical bug it fixes.
> >
> > Dennis
That is a perfectly acceptable reason  the bug report did not state anything 
other than please include it.  

It will get picked up in the next build along with all the other translations.

Dennis


signature.asc
Description: This is a digitally signed message part.
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

sugar-core for Update.1 - was: [sugar] What's left for Update.1

[Simon Schampijer]

Things I find worth looking at for update.1 (at least the things that 
are in joyride or we have a fix for):

* In joyride and tested
  - #6046 Browse is slow (rainbow.noarch 0:0.7.9-1.olpc2, 
fontconfig.i386 0:2.4.2-5.olpc2)
  - #5904 Grouping in mesh view: sugar-0.75.11-2.olpc2.i386.rpm
  - #4781 Video/Audio files from Record don't show up on clipboard: 
sugar-base-0.2.2-1.olpc2.i386.rpm

* Have a patch and tested
  - #6127 Browse can't register handler (fix in sugar git master)
  - #6108 Browse crash when X refuses / patch for hulahop attached to ticket

* Unresolved
  - #6133 controls not right in xulrunner beta-2
  - #6308 Browse does not release sound device
  - #6170 Write crash

Best,
Simon


Jim Gettys wrote:
> For comment and discussion, here are the showstoppers I know of for
> getting Update.1 finished.  If you think there are others, please speak
> up now (and modify the subject line to start another thread).
> 
> Activity developers: note we'll be asking you to upload updated
> activities to pick up all the recent flurry of translation work very
> soon.
> 
>  1 - wireless firmware and driver support 
>   (to fix problems with WEP and WPA)
>  2 - q2d11 OFW - to fix battery problems
>  3 - update activities to pick up translation work, Spanish 
>   in particular, but not missing other languages we may need.
>  4 - UI fix for registration with the school server.
> http://dev.laptop.org/ticket/6136
>  5 - switch to gabble from salut at school.
>  6 -testing and fixing anything critical!
> 
> If we don't want to hold up an RC2 to pick up translation, then we
> should anticipate an RC4 might be necessary (as we may have issues that
> come up with updated activities).
> 
> 4 - we previously (without Dave Woodhouse being available to add to the
> discussion) thought we could/should punt #6135 and release note.
> However, talking with him about what we should really fix given his
> experience in Mongolia, the lack of positive confirmation that the
> laptop actually was registered is a real issue.  The teachers are not
> familiar with English (or computers), and the subtlety of a menu entry
> going away isn't good enough.
> 
> I think we need to seriously discuss about possibly/probably being
> update.1 fodder is the "kids arrive at school in the morning" problem.
> 
> 5 - Use of mesh in large, crowded environments
> If everyone arrives at school running local link and resumed quickly,
> the network might melt from mdns mesh traffic's interaction with the
> mesh's implementation of mutlicast.  We've upped the multicast bitrate
> for multicast as a band aid, until we can dynamically adjust the
> bitrate.  But the fundamental issue comes that in large, dense school
> environments, can't expect multicast to scale far enough, and should be
> using unicast to a presence server (jabber in our current case) to
> handle this problem.
> 
> Dave Woodhouse has suggested may be to try to get a response to the
> school server's anycast address, and if we get a response from a school
> server, switch from Salut to Gabble for presence service automatically.
> 
> This is also somewhat mitigated by having working power management, as
> machines that have suspended due to idle stop sending mdns packets, and
> the kids presumably will want internet access and switch over when they
> arrive.  But I'm not very confident that this will always work in large
> environment.
> 
> Another temporary solution would be to have Ohm ask NM to reconnect if
> the machine is suspended for more than some interval, say, 30 minutes.
> 

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: New update.1 build 691

[Stephen Reilly]

WEP appears to work

Ricardo Carrano wrote:
> In preliminary and quick tests, both WPA and WEP are working.
>
> 2008/2/7 ffm <[EMAIL PROTECTED] >:
>
> I take it this is RC2?
>
> Does WEP work yet?
>
>
> On Feb 7, 2008 5:53 PM, Build Announcer v2 <[EMAIL PROTECTED]
> > wrote:
>
> http://pilgrim.laptop.org/~pilgrim/olpc/streams/update.1/build691
> 
>
> Changes in build 691 from build: 690
>
> Size delta: 0.13M
>
> -kernel 2.6.22-20080110.1.olpc.940c801838dbaf2
> +kernel 2.6.22-20080131.2.olpc.f150813900a7eec
> -libertas-usb8388-firmware 2:5.110.20.p49-1.fc7
> +libertas-usb8388-firmware 2:5.110.22.p1-1.fc7
> -olpcrd 0.39-0
> +olpcrd 0.40-0
> -olpcupdate 2.1-0
> +olpcupdate 2.3-0
> -bootfw q2d10-1.olpc2.unsigned
> +bootfw q2d13-1.olpc2.unsigned
> -olpccontents 2.0-0
> +olpccontents 2.1-0
> -Web 84
> +Web 85
> -Record 50
> +Record 51
> -Journal 83
> +Journal 85
>
> --- Changes for bootfw q2d13-1.olpc2.unsigned from
> q2d10-1.olpc2.unsigned ---
>  + update to q2d13 this is an unsigned image
>  + 791 + 803 + 812 + 813 + WLAN firmware 5.110.22.p1
>  + EC is pq2d13
>  + OFW Changes since q2d12:
>  + OLPC security - block exceptions during secure startup.
>  + EC Changes since q2d12:
>  + Version bump only
>
> --- Changes for Web 85 from 84 ---
>  + Remove canceled download from active downloads list #6018
>
> --- Changes for Record 51 from 50 ---
>  + #4525 defensive workaround
>  + #5899 fix
>  + tags
>
> --- Changes for Journal 85 from 83 ---
>  + #6190 Don't crash when an activity has its icon missing.
>  + #6029 Don't fail when the mount point is already occupied.
>
> --
> This mail was automatically generated
> See http://dev.laptop.org/~rwh/announcer/update.1-pkgs.html
> 
> for aggregate logs
> See
> http://dev.laptop.org/~rwh/announcer/joyride_vs_update1.html
> 
> for a comparison
> ___
> Devel mailing list
> Devel@lists.laptop.org 
> http://lists.laptop.org/listinfo/devel
>
>
>
> ___
> Devel mailing list
> Devel@lists.laptop.org 
> http://lists.laptop.org/listinfo/devel
>
>
> 
>
> ___
> Devel mailing list
> Devel@lists.laptop.org
> http://lists.laptop.org/listinfo/devel
>   
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: screen dims and brightens

[ffm]

On Feb 8, 2008 10:42 AM, Mikus Grinbergs <[EMAIL PROTECTED]> wrote:

> I'm using a wired connection for my G1G1.  To preserve that
> connection, I've entered 'touch /etc/ohm/inhibit-suspend'.
>
> With the more recent firmware updates, my screen periodically dims
> (around 55 seconds from one dim to the next) and brightens (about
> six seconds after it has dimmed).
>

That's been happening for me all the time on my B4, which cannot suspend at
all since 650 (intentional). This occurs often in any suspend-inhibited XO
using any version of the software after 650.

-FFM
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: New update.1 build 691

[Jim Gettys]

An updated etoys to pick up as much Spanish (and other languages) as we
can will is definitely necessary; whether we call this update.1 RC3 or
update.1.1 is all the same to me: updating all the activities to pick up
the languages is in the immediate future.
  - Jim

On Fri, 2008-02-08 at 08:56 -0600, Dennis Gilmore wrote:
> On Friday 08 February 2008, Bert Freudenberg wrote:
> > Am Feb 8, 2008 um 0:46 schrieb "C. Scott Ananian" <[EMAIL PROTECTED]>:
> > > 2008/2/7 ffm <[EMAIL PROTECTED]>:
> > >> I take it this is RC2?
> > >>
> > >> Does WEP work yet?
> > >
> > > This will be RC2
> >
> > This cannot possibly be RC2 because not all approved packages are in.
> > Etoys for example.
> I held etoys out because i dont know what critical bug it fixes.
> 
> Dennis
> ___
> Devel mailing list
> Devel@lists.laptop.org
> http://lists.laptop.org/listinfo/devel
-- 
Jim Gettys
One Laptop Per Child


___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: Association test

[Dan Williams]

On Fri, 2008-02-08 at 14:58 -0200, Ricardo Carrano wrote:
> I installed d-feet on an XO. But when I run './d-feet -l'  I get:
> 
> Traceback (most recent call last):
>   File "/usr/bin/d-feet", line 47, in 
> app = DFeetApp.DFeetApp()
>   File "/usr/lib/python2.5/site-packages/dfeet/DFeetApp.py", line 29,
> in __init__
> ui = UILoader(UILoader.UI_MAINWINDOW) 
>   File "/usr/lib/python2.5/site-packages/dfeet/_ui/uiloader.py", line
> 34, in __init__
> self.ui = gtk.Builder()
> AttributeError: 'module' object has no attribute 'Builder'
> 
> What am I doing or assuming wrong?

It needs a newer GTK that supports GtkBuilder.  2.6.12 or later I think.

Dan

> Thanks!
> 
> You could use d-feet to view the interfaces then:
> 
> https://hosted.fedoraproject.org/d-feet/
> 
> Marco
> 
> ___
> Devel mailing list
> Devel@lists.laptop.org
> http://lists.laptop.org/listinfo/devel

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: Updating translations for release...

[Sayamindu Dasgupta]

Hi,

On Feb 8, 2008 5:10 PM, Jim Gettys <[EMAIL PROTECTED]> wrote:
> The time has come to get the activities updated with Update.1
> translations.  How do we stand?
>

I have done extensive testing with Spanish and Mongolian, and they
seem to be good to go.

> We can't wait any longer to speak of. I think we need to pick a definite
> date and time for the completion of this, no later than, say, Monday,
> and anything untranslated stays untranslated.  We have to be able to
> move on to working on our next release.
>

Agree thoroughly. Monday is the date.

> 1) Can the activities be updated by you updating the packages, or will
> this require work by the activity developers?
>

Yes one can simply do a git pull from dev.laptop.org and the latest
translations will go in.

> 2) I gather we have to update Sugar to fix a problem or two to get the
> translations to stick.  Are there any other activities in a similar
> situation, that will require code updates as well as translations?
>

Not that I know of (except for Sugar). TurtleArt has a spelling
mistake which you might want to fix. However, the build system does
not pick up all translations - see #6179

> 3) Fuzzy strings.  What's left to un-fuzz them?
>

It depends on the translators - I request all translators to got
through their fuzzy strings during the weekend if possible, and unfuzz
them. Messages which remain fuzzy on Monday  will not be compiled in.

> 4) fonts: are there any additional fonts that need to be added?  If so,
> what are their packages, their licenses, and their sizes?  Does Dennis
> know what languages are to go into the image?
>

Depends on #6179 (ie, which languages go into the image). I believe we
cover all the languages that are currently defined in Sugar Control
Panel - but I'll stilll go through them and verify by Sunday.

> 5) I noticed some mail go by that certain mis-coding could cause
> activities to crash.  How do we get those fixed?
>

Hmm - tough question :-). I'll try to fix those by hand (most of them
are syntax errors). But this will take some time, and I'll probably
finish by Sunday night (IST). So any package update has to be _after_
that. Does that sound viable ?


Thank you,
Sayamindu


-- 
Sayamindu Dasgupta
[http://sayamindu.randomink.org/ramblings]
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: Association test

[Ricardo Carrano]

I installed d-feet on an XO. But when I run './d-feet -l'  I get:

Traceback (most recent call last):
  File "/usr/bin/d-feet", line 47, in 
app = DFeetApp.DFeetApp()
  File "/usr/lib/python2.5/site-packages/dfeet/DFeetApp.py", line 29, in
__init__
ui = UILoader(UILoader.UI_MAINWINDOW)
  File "/usr/lib/python2.5/site-packages/dfeet/_ui/uiloader.py", line 34, in
__init__
self.ui = gtk.Builder()
AttributeError: 'module' object has no attribute 'Builder'

What am I doing or assuming wrong?

Thanks!

You could use d-feet to view the interfaces then:
>
> https://hosted.fedoraproject.org/d-feet/
>
> Marco
>
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

screen dims and brightens

[Mikus Grinbergs]

I'm using a wired connection for my G1G1.  To preserve that 
connection, I've entered 'touch /etc/ohm/inhibit-suspend'.

With the more recent firmware updates, my screen periodically dims 
(around 55 seconds from one dim to the next) and brightens (about 
six seconds after it has dimmed).

In particular, I'm seeing this behavior on build 691 with Q2D13.

mikus

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: New update.1 build 691

[Ricardo Carrano]

In preliminary and quick tests, both WPA and WEP are working.

2008/2/7 ffm <[EMAIL PROTECTED]>:

> I take it this is RC2?
>
> Does WEP work yet?
>
>
> On Feb 7, 2008 5:53 PM, Build Announcer v2 <[EMAIL PROTECTED]> wrote:
>
> > http://pilgrim.laptop.org/~pilgrim/olpc/streams/update.1/build691
> >
> > Changes in build 691 from build: 690
> >
> > Size delta: 0.13M
> >
> > -kernel 2.6.22-20080110.1.olpc.940c801838dbaf2
> > +kernel 2.6.22-20080131.2.olpc.f150813900a7eec
> > -libertas-usb8388-firmware 2:5.110.20.p49-1.fc7
> > +libertas-usb8388-firmware 2:5.110.22.p1-1.fc7
> > -olpcrd 0.39-0
> > +olpcrd 0.40-0
> > -olpcupdate 2.1-0
> > +olpcupdate 2.3-0
> > -bootfw q2d10-1.olpc2.unsigned
> > +bootfw q2d13-1.olpc2.unsigned
> > -olpccontents 2.0-0
> > +olpccontents 2.1-0
> > -Web 84
> > +Web 85
> > -Record 50
> > +Record 51
> > -Journal 83
> > +Journal 85
> >
> > --- Changes for bootfw q2d13-1.olpc2.unsigned from
> > q2d10-1.olpc2.unsigned ---
> >  + update to q2d13 this is an unsigned image
> >  + 791 + 803 + 812 + 813 + WLAN firmware 5.110.22.p1
> >  + EC is pq2d13
> >  + OFW Changes since q2d12:
> >  + OLPC security - block exceptions during secure startup.
> >  + EC Changes since q2d12:
> >  + Version bump only
> >
> > --- Changes for Web 85 from 84 ---
> >  + Remove canceled download from active downloads list #6018
> >
> > --- Changes for Record 51 from 50 ---
> >  + #4525 defensive workaround
> >  + #5899 fix
> >  + tags
> >
> > --- Changes for Journal 85 from 83 ---
> >  + #6190 Don't crash when an activity has its icon missing.
> >  + #6029 Don't fail when the mount point is already occupied.
> >
> > --
> > This mail was automatically generated
> > See 
> > http://dev.laptop.org/~rwh/announcer/update.1-pkgs.htmlfor
> >  aggregate logs
> > See 
> > http://dev.laptop.org/~rwh/announcer/joyride_vs_update1.htmlfor
> >  a comparison
> > ___
> > Devel mailing list
> > Devel@lists.laptop.org
> > http://lists.laptop.org/listinfo/devel
> >
>
>
> ___
> Devel mailing list
> Devel@lists.laptop.org
> http://lists.laptop.org/listinfo/devel
>
>
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: New update.1 build 691

[Dennis Gilmore]

On Friday 08 February 2008, Bert Freudenberg wrote:
> Am Feb 8, 2008 um 0:46 schrieb "C. Scott Ananian" <[EMAIL PROTECTED]>:
> > 2008/2/7 ffm <[EMAIL PROTECTED]>:
> >> I take it this is RC2?
> >>
> >> Does WEP work yet?
> >
> > This will be RC2
>
> This cannot possibly be RC2 because not all approved packages are in.
> Etoys for example.
I held etoys out because i dont know what critical bug it fixes.

Dennis
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: Updating translations for release...

[Jim Gettys]

Yes.
   - Jim

On Fri, 2008-02-08 at 16:27 +0200, Morgan Collett wrote:
> On Feb 8, 2008 1:40 PM, Jim Gettys <[EMAIL PROTECTED]> wrote:
> > 2) I gather we have to update Sugar to fix a problem or two to get the
> > translations to stick.  Are there any other activities in a similar
> > situation, that will require code updates as well as translations?
> 
> There's a bug fix for Chat that you said could go in when we pick up
> the translations: https://dev.laptop.org/ticket/6066
> 
> Is this still OK to go in?
-- 
Jim Gettys
One Laptop Per Child


___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: Updating translations for release...

[Gary Oberbrunner]

> On Feb 8, 2008 1:40 PM, Jim Gettys <[EMAIL PROTECTED]> wrote:
>> 2) I gather we have to update Sugar to fix a problem or two to get the
>> translations to stick.  Are there any other activities in a similar
>> situation, that will require code updates as well as translations?

I know I'm just a G1G1 tester and this is not really a translation issue
as such, and I'm sorry to whine about it, but could someone just fix the 
title of the "TurteArt" activity so it doesn't contain a typo (missing 
"l")?  It looks so lame, and it's right on the home screen.  See trac #5941.

-- Gary

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: Updating translations for release...

[Morgan Collett]

On Feb 8, 2008 1:40 PM, Jim Gettys <[EMAIL PROTECTED]> wrote:
> 2) I gather we have to update Sugar to fix a problem or two to get the
> translations to stick.  Are there any other activities in a similar
> situation, that will require code updates as well as translations?

There's a bug fix for Chat that you said could go in when we pick up
the translations: https://dev.laptop.org/ticket/6066

Is this still OK to go in?
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: [sugar] python activities startup

[Tomeu Vizoso]

On Fri, 2008-02-08 at 14:44 +0100, Tomeu Vizoso wrote:
> On Fri, 2008-02-08 at 13:41 +0100, Tomeu Vizoso wrote:
> > On Thu, 2008-02-07 at 16:46 +, Simon McVittie wrote:
> > > A better solution would be for Rainbow to avoid SessionBus()
> entirely,
> > > and instead use an instance of the superclass,
> dbus.bus.BusConnection. This
> > > does not have the weird caching behaviour at all (one call to the
> > > constructor = one instance = one D-Bus connection). The code that
> gets run
> > > after forking is still free to use the shared SessionBus.
> > 
> > Rainbow is not using the session bus at all, just the system one.
> > 
> > But when the child tries to instantiate a SessionBus object, I get
> this stack trace:
> > 
...
> > 
> > : 
> > org.freedesktop.DBus.Error.NoServer: Failed to connect to socket 
> > /tmp/dbus-7dk02BRXOZ: Connection refused
> > 
> > 
> > This is the value of the DBUS_SESSION_BUS_ADDRESS env var:
> > unix:path=/tmp/olpc-session-bus,guid=fdf37ebd35a585d12382a50047ac3034
> > 
> > unix:path=/tmp/olpc-session-bus is specified
> > in /etc/dbus-1/session-olpc.conf:
> > 
> > 
> >   
> >   session
> > 
> >   unix:path=/tmp/olpc-session-bus
> > 
> >   
> > ...
> 
> When running inside rainbow, strace shows this:
> 
> [pid  2370] connect(0, {sa_family=AF_FILE, path=@/tmp/dbus-XQcfxlvcoY}, 23) = 
> -1 ECONNREFUSED (Connection refused)
> 
> But on the console (works fine):
> 
> connect(3, {sa_family=AF_FILE, path="/tmp/olpc-session-bus"}, 23) = 0

I'm sorry about the noise.

When Rainbow was started, the env var DBUS_SESSION_BUS_ADDRESS wasn't
set until the clone() happened. By looking at dbus code, the bus
addresses are initialized at startup, so it kept using the bad address.

Setting DBUS_SESSION_BUS_ADDRESS before running Rainbow fixed this
issue.

So, no known D-Bus problems right now.

Tomeu

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: python activities startup

[Tomeu Vizoso]

On Fri, 2008-02-08 at 13:41 +0100, Tomeu Vizoso wrote:
> On Thu, 2008-02-07 at 16:46 +, Simon McVittie wrote:
> > A better solution would be for Rainbow to avoid SessionBus() entirely,
> > and instead use an instance of the superclass, dbus.bus.BusConnection. This
> > does not have the weird caching behaviour at all (one call to the
> > constructor = one instance = one D-Bus connection). The code that gets run
> > after forking is still free to use the shared SessionBus.
> 
> Rainbow is not using the session bus at all, just the system one.
> 
> But when the child tries to instantiate a SessionBus object, I get this stack 
> trace:
> 
> /usr/lib/python2.5/site-packages/sugar/presence/presenceservice.py in 
> __init__(self= (sugar+presence+presenceservice+PresenceService at 0x86f1370)>, 
> allow_offline_iface=False)
>  73 
>  74 # Get a connection to the session bus
> ---> 75 self._bus = dbus.SessionBus()
> self._bus = undefined
> global dbus.SessionBus = 
>  76 self._bus.add_signal_receiver(self._name_owner_changed_cb,
>  77 signal_name="NameOwnerChanged",
> 
> /usr/lib/python2.5/site-packages/dbus/_dbus.py in __new__(cls= 'dbus._dbus.SessionBus'>, private=False, mainloop=None)
> 211 """
> 212 return Bus.__new__(cls, Bus.TYPE_SESSION, private=private,
> --> 213mainloop=mainloop)
> mainloop = None
> 214 
> 215 class StarterBus(Bus):
> 
> /usr/lib/python2.5/site-packages/dbus/_dbus.py in __new__(cls= 'dbus._dbus.SessionBus'>, bus_type=0, private=False, mainloop=None)
> 100 raise ValueError('invalid bus_type %s' % bus_type)
> 101 
> --> 102 bus = BusConnection.__new__(subclass, bus_type, 
> mainloop=mainloop)
> bus = undefined
> global BusConnection.__new__ = 
> subclass = 
> bus_type = 0
> mainloop = None
> 103 
> 104 bus._bus_type = bus_type
> 
> /usr/lib/python2.5/site-packages/dbus/bus.py in __new__(cls= 'dbus._dbus.SessionBus'>, address_or_type=0, mainloop=None)
> 123 
> 124 def __new__(cls, address_or_type=TYPE_SESSION, mainloop=None):
> --> 125 bus = cls._new_for_bus(address_or_type, mainloop=mainloop)
> bus = undefined
> cls._new_for_bus =  0x8256f44>
> address_or_type = 0
> mainloop = None
> 126 
> 127 # _bus_names is used by dbus.service.BusName!
> 
> : org.freedesktop.DBus.Error.NoServer: 
> Failed to connect to socket /tmp/dbus-7dk02BRXOZ: Connection refused
> 
> 
> This is the value of the DBUS_SESSION_BUS_ADDRESS env var:
> unix:path=/tmp/olpc-session-bus,guid=fdf37ebd35a585d12382a50047ac3034
> 
> unix:path=/tmp/olpc-session-bus is specified
> in /etc/dbus-1/session-olpc.conf:
> 
> 
>   
>   session
> 
>   unix:path=/tmp/olpc-session-bus
> 
>   
> ...

When running inside rainbow, strace shows this:

[pid  2370] connect(0, {sa_family=AF_FILE, path=@/tmp/dbus-XQcfxlvcoY}, 23) = 
-1 ECONNREFUSED (Connection refused)

But on the console (works fine):

connect(3, {sa_family=AF_FILE, path="/tmp/olpc-session-bus"}, 23) = 0

Tomeu

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: python activities startup

[Tomeu Vizoso]

On Thu, 2008-02-07 at 16:46 +, Simon McVittie wrote:
> A better solution would be for Rainbow to avoid SessionBus() entirely,
> and instead use an instance of the superclass, dbus.bus.BusConnection. This
> does not have the weird caching behaviour at all (one call to the
> constructor = one instance = one D-Bus connection). The code that gets run
> after forking is still free to use the shared SessionBus.

Rainbow is not using the session bus at all, just the system one.

But when the child tries to instantiate a SessionBus object, I get this stack 
trace:

/usr/lib/python2.5/site-packages/sugar/presence/presenceservice.py in 
__init__(self=, 
allow_offline_iface=False)
 73 
 74 # Get a connection to the session bus
---> 75 self._bus = dbus.SessionBus()
self._bus = undefined
global dbus.SessionBus = 
 76 self._bus.add_signal_receiver(self._name_owner_changed_cb,
 77 signal_name="NameOwnerChanged",

/usr/lib/python2.5/site-packages/dbus/_dbus.py in __new__(cls=, private=False, mainloop=None)
211 """
212 return Bus.__new__(cls, Bus.TYPE_SESSION, private=private,
--> 213mainloop=mainloop)
mainloop = None
214 
215 class StarterBus(Bus):

/usr/lib/python2.5/site-packages/dbus/_dbus.py in __new__(cls=, bus_type=0, private=False, mainloop=None)
100 raise ValueError('invalid bus_type %s' % bus_type)
101 
--> 102 bus = BusConnection.__new__(subclass, bus_type, 
mainloop=mainloop)
bus = undefined
global BusConnection.__new__ = 
subclass = 
bus_type = 0
mainloop = None
103 
104 bus._bus_type = bus_type

/usr/lib/python2.5/site-packages/dbus/bus.py in __new__(cls=, address_or_type=0, mainloop=None)
123 
124 def __new__(cls, address_or_type=TYPE_SESSION, mainloop=None):
--> 125 bus = cls._new_for_bus(address_or_type, mainloop=mainloop)
bus = undefined
cls._new_for_bus = 
address_or_type = 0
mainloop = None
126 
127 # _bus_names is used by dbus.service.BusName!

: org.freedesktop.DBus.Error.NoServer: 
Failed to connect to socket /tmp/dbus-7dk02BRXOZ: Connection refused


This is the value of the DBUS_SESSION_BUS_ADDRESS env var:
unix:path=/tmp/olpc-session-bus,guid=fdf37ebd35a585d12382a50047ac3034

unix:path=/tmp/olpc-session-bus is specified
in /etc/dbus-1/session-olpc.conf:


  
  session

  unix:path=/tmp/olpc-session-bus

  
...

Any ideas?

Thanks,

Tomeu


___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: Association test

[Marco Pesenti Gritti]

On Feb 8, 2008 11:30 AM, Ricardo Carrano <[EMAIL PROTECTED]> wrote:
> Marco,
>
> Thank you for the message.
>
> This seems to be the same we find at:
> http://people.redhat.com/dcbw/NetworkManager/NetworkManager%20DBUS%20API.txt
>
> It does not seems updated or complete. I know, from a Dan Williams email,
> that there is, for example a setWirelessEnabled method that is not there.
>

You could use d-feet to view the interfaces then:

https://hosted.fedoraproject.org/d-feet/

Marco
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Updating translations for release...

[Jim Gettys]

The time has come to get the activities updated with Update.1
translations.  How do we stand?

We can't wait any longer to speak of. I think we need to pick a definite
date and time for the completion of this, no later than, say, Monday,
and anything untranslated stays untranslated.  We have to be able to
move on to working on our next release.

1) Can the activities be updated by you updating the packages, or will
this require work by the activity developers?

2) I gather we have to update Sugar to fix a problem or two to get the
translations to stick.  Are there any other activities in a similar
situation, that will require code updates as well as translations?

3) Fuzzy strings.  What's left to un-fuzz them?

4) fonts: are there any additional fonts that need to be added?  If so,
what are their packages, their licenses, and their sizes?  Does Dennis
know what languages are to go into the image?

5) I noticed some mail go by that certain mis-coding could cause
activities to crash.  How do we get those fixed?

Anything else I've missed?

Thanks for everyone's help!
 - Jim Gettys

-- 
Jim Gettys
One Laptop Per Child


___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: Association test

[Ricardo Carrano]

Yeah, it seems promising! Thank you!


> You could use d-feet to view the interfaces then:
>
> https://hosted.fedoraproject.org/d-feet/
>
> Marco
>
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: Joyride builds are incomplete

[Simon Schampijer]

A new working joyride build is out: 
http://xs-dev.laptop.org/~cscott/olpc/streams/joyride/build1658/

Best,
Simon

Mark Bauer wrote:
> I would like to try the latest builds, but all builds (6 of them)  
> after joyride-1643
> are incomplete?
> 
> dev.laptop.org/~bert/joyride-pkgs.html and the
> rsync rsync://updates.laptop.org
> 
> both show only up to 1643 as good?
> 
> Is there a better place to look?
> 
> Thanks
> 
> Mark
> 
> 
> 
> ___
> Devel mailing list
> Devel@lists.laptop.org
> http://lists.laptop.org/listinfo/devel

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: Association test

[Ricardo Carrano]

Wad,

This script is meant to test infra-structure association, so I believe it
can only indirectly help with #6287 (mesh association). But of course we can
always make a new one for the mesh forming and for the school server
association.

I should comment this (and I will) on the ticket, but I believe #4975 is not
present in recent builds. At least in my tests, the association happens at
the first attempt (or it won't happen at all because of any other transient
issue, like WEP or WPA support).

On Feb 7, 2008 9:29 PM, John Watlington <[EMAIL PROTECTED]> wrote:

>
> I don't know the answer to your question.   But the test you've proposed
> would help figure out #6287 and #4975.   In my case, it may be problems
> associating with a new mesh after suspending, or after 24+ hours.
>
> We eagerly anticipate it.
>
> wad
>
> On Feb 7, 2008, at 4:21 PM, Ricardo Carrano wrote:
>
> > As part of the wireless test suite, I am writing a test script for
> > the association process.  Basically you write a configuration file
> > with the info on some essids; the script parses the file and tries
> > to associate to each of the APs in loop.
> >
> > The only drawback is that the script kills NetworkManager, so it
> > does not test all the components involved (only firmware and driver).
> > I suspect it is possible to send dbus-messages to NM asking for it
> > to associate, and then listen to the bus and wait for an answer.
> >
> > My question is whether this mechanism is documented somewhere.
> >
> > Comments in the idea are also welcome, of course.
> > Any help you be appreciated. Thanks!
> >
> > --
> > Ricardo Carrano
> > ___
> > Devel mailing list
> > Devel@lists.laptop.org
> > http://lists.laptop.org/listinfo/devel
>
>
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: Association test

[Ricardo Carrano]

Marco,

Thank you for the message.

This seems to be the same we find at:
http://people.redhat.com/dcbw/NetworkManager/NetworkManager%20DBUS%20API.txt

It does not seems updated or complete. I know, from a Dan Williams email,
that there is, for example a setWirelessEnabled method that is not there.

But thanks anyway.


On Feb 7, 2008 9:15 PM, Marco Pesenti Gritti <[EMAIL PROTECTED]> wrote:

> This might be useful:
>
>
> http://svn.gnome.org/viewvc/NetworkManager/branches/nm-0-6-olpc/docs/NetworkManager%20DBUS%20API.txt?revision=2474&view=markup
>
> Marco
>
> 2008/2/7 Ricardo Carrano <[EMAIL PROTECTED]>:
> > As part of the wireless test suite, I am writing a test script for the
> > association process.  Basically you write a configuration file with the
> info
> > on some essids; the script parses the file and tries to associate to
> each of
> > the APs in loop.
> >
> > The only drawback is that the script kills NetworkManager, so it does
> not
> > test all the components involved (only firmware and driver).
> > I suspect it is possible to send dbus-messages to NM asking for it to
> > associate, and then listen to the bus and wait for an answer.
> >
> > My question is whether this mechanism is documented somewhere.
> >
> > Comments in the idea are also welcome, of course.
> > Any help you be appreciated. Thanks!
> >
> > --
> > Ricardo Carrano
> >
> > ___
> > Devel mailing list
> > Devel@lists.laptop.org
> > http://lists.laptop.org/listinfo/devel
> >
> >
>
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: Include olpc-audit in olpc-utils?

[Bernardo Innocenti]

Michael Stone wrote:

> olpc-audit is a filesystem-status-verifier written for us by Marcus
> Leech. I think it would be decent to include in olpc-utils because,
> analogous to the network and battery status detectors, it's handy for
> figuring out if people have done funny things to their filesystem. Also,
> I'd like to be able to run it from inside pilgrim or puritan chroots
> before releasing builds.

Sure!

> Anyway, I've prepared patches to include it in olpc-utils in the
> 'master' branch of 
> 
>   http://dev.laptop.org/git/users/mstone/olpc-utils
>   (and the other usual urls)
>
> Would you consider merging them?

The patches look fine, but next time don't manually bump
the package revision and edit the spec file log: I have
a Makefile rule to automate this.

Also, would you mind doing the committing and package
rebuilding on your own?  I'm still wandering around in
Australia and I don't seem to find a decent Internet connection
anywhere.

(or I can do it later if it's not urgent)

-- 
 \___/
 |___|   Bernardo Innocenti - http://www.codewiz.org/
  \___\  One Laptop Per Child - http://www.laptop.org/
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Translation updates (was Re: New update.1 build 691)

[Morgan Collett]

On Feb 8, 2008 1:46 AM, C. Scott Ananian <[EMAIL PROTECTED]> wrote:
> This will be RC2; WEP/WPA are believed working but please test.

When do we update activity translations? I see Spanish translations
have been done for Chat, but the pootle commits include other
languages too. Must I cherry-pick the least set of commits that
include Spanish, or include them all?
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

FAQ Interactive, Fusionbox Creates Online Video Q&A Tool

[william rockt]

FAQ Interactive, Fusionbox Creates Online Video Q&A Tool

http://www.faqinteractive.com/ 1-866-268-5588


Denver, CO (PRWeb) March 12, 2007 -- Fusionbox, a Denver web design
and development company has launched a revolutionary
video question and answer tool called Jabbits .

The online tool allows users to upload questions in the form of video that
they record with their webcams. Users can then upload answers to the
questions of others. The Flash tool connects directly to the user's webcam
in order to record and upload video content. Users can rate, email and even
embed the tool on their blog, MySpace page or website.

"The online question and answer space has really gotten popular in the last
year," said Alexander Groth, President of Fusionbox. "Yahoo, LinkedIn and
MSN all have Q&A features but none of them use a video component." The site
was developed by Fusionbox using Flash and open source technologies (PHP,
MySQL). The Flash tool uploads converts, encodes and optimizes a variety of
different video file formats.

Jabbits not only serves as a unique tool for users, but it is a highly
effective tool for market researchers. Jabbits allows market researchers to
connect with their target audience in various locations without leaving
their offices. Jabbits is also more cost effective and provides faster
results than traditional focus groups.

ABOUT Fusionbox, Inc. - Fusionbox is a Denver web
designand development company. Fusionbox offers
custom web software development,
web design, search engine marketing, content management solutions and
e-commerce solutions.

###
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: New update.1 build 691

[Bert Freudenberg]

Am Feb 8, 2008 um 0:46 schrieb "C. Scott Ananian" <[EMAIL PROTECTED]>:

> 2008/2/7 ffm <[EMAIL PROTECTED]>:
>> I take it this is RC2?
>>
>> Does WEP work yet?
>
> This will be RC2

This cannot possibly be RC2 because not all approved packages are in.  
Etoys for example.

- Bert -
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel