automatic reminder of 'software update' when installing a new build
Visited a friend, and helped him install a new build in his XO. The
first time the new build completed booting, he was presented with an
action bar (to request "software update") near the top of Home View.
It so happened that the XO had not automatically connected to my
friend's wireless AP - but he did not realize this. Being
well-meaning, he clicked the rightmost button ('Check now') in the
action bar -- there was some software processing and then a "Could
not access the network" message -- he needed to exit through Control
Panel to get back to Home View (and never saw the action bar again).
The "software update" facility assumes that a connection to the
network is already available when it gets to run. If conditions are
such that the network connection has *not* been set up when booting
completes, should the action bar to request "software update" still
be automatically presented as the first thing the user sees ?
mikus
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
Re: New Browse ready for Emilianio?
Howdy, The back (left arrow) and forward (right arrow) and stop/resume buttons don't work in Browse 101 on 767. Also get 'page not found' for perfectly good addresses. ¡Humbug! genesee -- View this message in context: http://n2.nabble.com/New-Browse-ready-for-Emilianio--tp1694156p1801991.html Sent from the Software development mailing list archive at Nabble.com. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Auto-suspend and Presence Service
In 9.1.0, auto-suspend is going to be on by default, which we estimate will roughly triple our battery life. We're working on fixing all the bugs that would prevent that. One of them is not strictly a bug -- it's a performance issue. The Presence Service sends packets frequently, for tracking the presence of your friends and any shared activities. Many of these are multicast packets (some are probably unicast jabber packets, too). In 8.2.0, with auto-suspend enabled, you have to run a specific command to enable suspended laptops to awaken when multicast packets arrive; see bug #6818 and run "ethtool -s msh0 wol um". This will become the default in 9.1.0. The problem I can foresee is that the Presence Service will send packets so frequently that everyone's laptop will always be waking up, negating the power-stretching abilities of auto-suspend. This seems to occur with only a few laptops around (in my tests at home); yet we need to make it work with dozens of laptops within range, for our deployments. I hope that the Collabora team is running in this mode now, and working out ways to reduce packet traffic to let sleeping laptops lie. The cellular phone industry went through several cycles of design improvements like this, enabling today's remarkable phone battery life, without impact on our ability to rapidly communicate whenever desired. OLPC hasn't yet done the first round of such improvements, and I hope it WILL do so before 9.1.0. We could all use those long battery lives -- especially the kids in the rural deployments. We don't want to tell them to turn off collaboration if they want their laptop to last all day; it's one of our key features. John ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Minutes of Power in 9.1.0 meeting
> Also, who is tracking the added ability to shut off power to the radio > interface and its logic when the radio is set to off in its control > panel (requirement 2)? The difference between "Radio Off" and "Extreme Power Management" should become that "Radio Off" still leaves the USB bus functioning, though it will power-off the WiFi chip. This would allow airplane users to still use USB sticks or USB keyboards, for example. Both settings should have similar impacts on power, since I think the big power hog is the WiFi chip, not the USB bus itself). I don't think anyone has quantified how much power difference there would be, tho. I added a section to the wiki page, mentioning related tickets, and also filed a new ticket for the exact issue (#9145). I'm beginning to think that if we just fix #6995 (mesh icon in Frame that allows picking Mesh channel and disabling it), then this control panel item won't be needed, and the Frame will provide all the controls needed. If you disable the mesh and you disconnect from any access point, the WiFi will power down. Simple. It powers up when you turn on either the mesh or try to connect to an access point (enter the Network screen). We'd have to fix the Network screen so that if you go there, look at the pretty icons, maybe even try a few, then leave the page, if you aren't connected to an access point (or mesh) when you leave, it should power down the radio again. John ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
9.1.0 meeting minutes
Sayamindu, Michael, Paul, Brian, CJL and maybe others met on Xmas eve! We scrapped the agenda and did Q&A with Michael doing the Q. Concerns that people aren't working on the release. Review power and languages and they are both doing well. Sayamindu said he will update localization feature pages this week: http://wiki.laptop.org/go/Feature_roadmap/Page_of_all_features_that_target_9.1.0 Paul said he will share his power button menu design more widely. Comments on design welcome: http://wiki.laptop.org/go/Feature_roadmap/Shutdown_menu Code and demo version coming. Michael asked about testing joyride. Discussed the plan to fire up the Friends in testing/weekly build strategy. Brian is ready. We will start with a dry run of the test process on an 8.2.1 release. Michael kicked that off via this e-mail: http://lists.laptop.org/pipermail/devel/2008-December/022083.html We're on for next week Wed. December 31, 2PM US ET IRC freenode.net #olpc-meeting channel. Back to the regular agenda: 5 minutes - review last weeks action items. 10 minutes XO Camp status 25 minutes - 9.1.0 page and feature development status. Also activity compatibility and activity set selection. Lastly, Trac conventions and scrub status. 10 minutes - Synchronizing with Sugar release cycle 10 minutes - set action items and agenda for next week. Have a great Christmas! Thanks, Greg S ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: 8.2.1 Smoke Testing
P.S. - I know that Mel & volunteers have done some awesome work on systematic testing for 8.2.1 here: http://wiki.laptop.org/go/Test_cases_8.2.1 and that results from the Old Smokey of OLPC testing, http://wiki.laptop.org/go/1_hour_smoke_test would be truly appreciated. P.P.S. - If I forgot anything else important, or if you have questions or improvements of your own to contribute, don't hesitate one second to reply. Thanks again! Michael ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
8.2.1 Smoke Testing
Hey folks.
We could use your help testing our first real 8.2.1 integration build,
named
'staging-7'
You can find it at
http://xs-dev.laptop.org/~cscott/xo-1/streams/staging/build7/devel_jffs2/
The tickets which people think it fixes are here:
http://tinyurl.com/8r6clm
If you can't find the testcase for one of these changes, please push it
back into the 'testcase' workflow state. ("next action field").
(See http://wiki.laptop.org/go/Trac_ticket_workflow for more details.)
Thanks very much!
Michael
P.S. - I expect that Brian Pepple, our new Friends-in-Testing (FiT)
coordinator will be improving
http://wiki.laptop.org/go/Friends_in_testing
to reflect this information shortly.
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
Weekly report and meeting reminder
Hi All, I am on for a 9.1.0 meeting at 2PM US ET today (wed. 12/24). IRC freenode.net #olpc-meeting. Minutes from last week and agenda for today are here: http://lists.laptop.org/pipermail/devel/2008-December/021947.html Here's my weekly report for week ending 12/19 is below. Merry Christmas and Happy New Year! ** XO Camp will be held at OLPC Headquarters, January 12 - 16, 2009. This is an open meeting for technical design review of 9.1.0 features. See the agenda and sign up to participate here: http://wiki.laptop.org/go/XOCamp_2 9.1.0 target features are here: http://wiki.laptop.org/go/9.1.0_requirements#Top_Priority Greg's user links of the week: English: Update on pilot in Nicaragua and links to two beautiful videos by the great team at Waveplace: http://waveplace.com/sm/mailing/mail.jsp?id=13&msg=1174 Spanish: New blog for XO deployment in Colombia: http://educacionitagui.blogspot.com/ Detailed deployment wiki for Paraguay including training materials, educational strategy, active e-mail lists and more: http://wiki.paraguayeduca.org/index.php/Portada ** New feature of the weekly report: Open source contributor of the week This week its: S (sometimes called Skierpage) S built queryable and sortable pages using Semantic wiki for Activities, Tests, Releases, and now Features. He also documented it and created "todo lists" so other people can make their own or extend his work. That's what I call first class software engineering! See his work at: http://wiki.laptop.org/go/Semantic_MediaWiki * Status of progress towards last weeks goals: 1 - Finish collection of all main features on Feature Roadmap page: http://wiki.laptop.org/go/Feature_roadmap. Stretch goal to make that a Semantic query with each feature having its own page. GS - Done! All major feature requests have a page and show in the Semantic query. I cleaned up all notes left by engineers and recorded my changes on the discussion page. Please add any more feature requests as described here: 2 - Update 9.1.0 page a detailed list of sub-requirements. Add detail to the schedule and get sign off on it from engineering and QA. Engage engineers to get specifications and plans documented for each feature. GS - Done! Top four categories breaks out in to ~13 Top priority features: http://wiki.laptop.org/go/9.1.0_requirements#Top_Priority. See them all on one page at: http://wiki.laptop.org/go/Feature_roadmap/Page_of_all_features_that_target_9.1.0 Next up is tracking secondary priorities which are also target for 9.1. 3 - Start triage of full feature roadmap to flag 9.1.0 items and prioritize all items. GS - Done! I chose the priorities myself so send me a note if anyone who has suggestions or differences of opinion based on the release goals. 4 - Create basic presentation on plans for 9.1.0 and run it by main customers and other stakeholders. GS - Partially done. Created second draft but haven't presented it yet. 5 - Update School Server documentation with links to Readme file for each main feature. Comment on XS roadmap and Moodle plan. GS - Not done. ** Goals for next week: 1 - Move technical discussion forward on all Top Priority 9.1. items. Update feature pages as needed. Choose second level 9.1.0 priorities. 2 - Finish setting detailed schedule for technical section of XO Camp and promote the event. 3 - Update School Server documentation with links to Readme file for each main feature. Comment on XS roadmap and Moodle plan. 4 - Add detail to 9.1.0 schedule and improve activities section. 5 - Add School server feature requests to Trac Thanks, Greg S ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: New Browse ready for Emilianio?
Hi Emiliano, On Wed, Dec 24, 2008 at 6:19 PM, Emiliano Pastorino wrote: > Hi, everyone > > We've tested it on 767 and it works great. We've followed the test case and > I think the problem is solved. > Great to hear that. > It doesn't work on 656, but that's not important since we're planning to > upgrade > to 767 (or later) in the next months. > > Thanks, Sayamindu! > You are more than welcome :-) Warm regards, and merry Christmas to everyone, Thanks, Sayamindu -- Sayamindu Dasgupta [http://sayamindu.randomink.org/ramblings] ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: New joyride build 2605
On Wednesday 24 December 2008 02:48:33 am Peter Robinson wrote: > >>> +sugar-base 0.83.2-2.olpc4 > >> > >> Good to see this up-leveled -- the previous version of this package > >> as distributed in Joyride was more than a month old. > >> > >> However, that still leaves several packages which appear to be more > >> > >> recent in 'olpc3' than in 'olpc4'. Output of 'yum check-update' : > >> | pyabiword.i386 0.6.1-4.olpc3 > >> | python-telepathy.noarch 0.15.3-1.olpc3 > >> | sugar-journal.noarch 100-1.olpc3 > >> | xorg-x11-drv-evdev.i386 2.0.8-1.fc9 > > > > I can comment on a couple of these, but I'm not sure how to fix them: > > > > * pyabiword is newer in olpc3 than fc10, but the spec files are > > basically the same - the olpc3 one seems to have had a no-change > > rebuild which bumped the version number higher than the fc10 version. > > There's no olpc4 version as we do not need to fork from the F-10 > > version - so we should get the fc10 version into joyride. > > > > * python-telepathy has the same version 0.15.3-1 in fc10 and olpc3. We > > should also be using the fc10 version here as we have rebased on F-10 > > and olpc3 was built on F-9. There's no need for an olpc4 fork of the > > package as we are using the same version as Fedora. > > > > * sugar-journal is no longer a separate package in Sugar 0.83, so > > there should not be a sugar-journal included in Joyride at all. The > > sugar package includes the journal functionality now. > > Basically I think these just need to be untagged in koji. I can look > at doing these in a couple of days when I get a proper internet > connection back. it needs to be blocked in koji, and pilgrim needs to be told not to include it. Dennis ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Devel Digest, Vol 34, Issue 86
mitch wrote: > d...@laptop.org wrote: > > On Tue, Dec 23, 2008 at 8:08 PM, wrote: > > > >> ssh host keys are probably generated on first boot as well. > >> > >> with partitioning support, it should be possible to have a r.o. root > >> overlaid by a unionfs writeable mount, so machine-specific changes > >> don't modify the released partition. this would make cloning quite a > >> bit easier, i'd think. i have no idea what the performance hit of > >> a unionfs setup would be, nor how such a partitioning would fit > >> into the rest of the update strategy (e.g. olpc-update). > >> > > > > unionfs isn't upstream and was quite unreliable last time I use it. > > > Puppy Linux has used unionfs for some time, apparently with good results. > > > And it adds the challenge of differentiating state that must be > > discarded for the cloned image, and state that must not be. > > > > Uh, is it really unionfs that adds that challenge? I would think that > the need to differentiate between wanted and unwanted state is a > fundamental requirement of the cloning approach, regardless of whether > or not unionfs is part of the implementation strategy. right. the process of preparing an image which is suitable for distribution will always be more complex than simply booting, configuring, and shutting down. it might involve mounting an external copy of the image and modifying it without running it, for instance. but once the image has initially been made suitable for cloning, using something like unionfs would allow that image to _remain_ suitable for cloning -- clonable from any laptop on which it's installed. paul =- paul fox, p...@laptop.org give one laptop, get one laptop --- http://www.laptop.com/xo ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Scratch on XO is frozen after standby
Hi Chris et al, I added this bug ID to the specification for power saving in 9.1 at: http://wiki.laptop.org/go/Feature_roadmap/Improved_battery_life Can you make sure to address that in the work on power save modes? I also updated the ticket with John's steps to reproduce. Thanks, Greg S > Date: Wed, 24 Dec 2008 12:36:04 +0100 > From: Bert Freudenberg > Subject: Re: Scratch on XO is frozen after standby > To: Philipp Kocher > Cc: John Maloney ,channeang ken > , OLPC Development > > Message-ID: <365f8fd3-def3-44bc-88c3-3f66db40d...@freudenbergs.de> > Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes > > This is a long-standing kernel bug. Sleep/resume is supposed to be > transparent to user-space processes. Could you add your findings to > the ticket, please? > > http://dev.laptop.org/ticket/6201 > > - Bert - > > On 24.12.2008, at 07:43, Philipp Kocher wrote: > >> Hi John >> >> Etoys has exactly the same problem (etoys is frozen and the line >> "snd_pcm_writei returned -86" gets written endlessly into the etoys >> logfile). >> >> Sorry, I don't know anything about DBus. >> >> To reproduce with Etoys: >> 1. Open etoys on the Xo >> 2. Click on "make A Project" >> 3. Click on "Supplies" >> 4. Drag and drop the "Sound recorder" >> 5. Record a sound >> 6. Play the recording >> 7. Press XO power button (just short so the XO goes in standby mode >> with dark screen) >> 8. Press XO power button (again just short) >> 9. Etoys is frozen >> >> Scratch: >> We have the frozen Scratch problem very often at the moment because >> we are using Scratch and record sounds (about 3-5 students of 30 per >> lesson). It really bad since saving the project is not possible >> anymore. >> >> First I thought it is because we switched on experimental Power >> Management. But now it is switched off and the problem is still here. >> >> It is just Scratch that freezes, Sugar is still working fine. >> I don't remember having seen this problem on older sugar builds e.g. >> 656 or 708 and we used Scratch intensively on this builds. >> >> Regards, >> Philipp >> >> John Maloney wrote: >>> Wow, first I've heard about this problem. I wonder if Etoys has the >>> same problem? >>> The problem appears to be have something to do with having the ALSA >>> sound output port open when the XO goes to sleep. This may actually >>> be an ALSA/sleep issue but it may be easier to work around it than >>> to fix ALSA. >>> Is there a DBus message or event that says when the machine is >>> about to go to sleep? >>>-- John >>> On Dec 23, 2008, at 9:56 PM, Philipp Kocher wrote: Hi John We have a big problem with Scratch version 11 and 12 on the XO (build 767). After not using the XO for some minutes Scratch freezes completely (no drag and drop and no buttons can be pressed anymore). The following line gets written in the scratch logfile in an endless loop (if scratch doesn't get killed, the logfile uses multiple MB): snd_pcm_writei returned -86 The problem can be reproduced easily: 1. Start Scratch 2. Record sound and play the sound 3. Press XO power button (just short so the XO goes in standby mode with dark screen) 4. Press XO power button (again just short) 5. Scratch is frozen Regards, Philipp Pepyride School Cambodia PS: Are you using the bug tracking page on dev.laptop.org for XO related bugs of Scratch? > > ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: New Browse ready for Emilianio?
Hi, everyone We've tested it on 767 and it works great. We've followed the test case and I think the problem is solved. It doesn't work on 656, but that's not important since we're planning to upgrade to 767 (or later) in the next months. Thanks, Sayamindu! On Tue, Dec 23, 2008 at 2:06 PM, Sayamindu Dasgupta wrote: > Hi Greg, > It has not passed through formal QA (yet), but there is a test case on > http://dev.laptop.org/ticket/9112 > I tried it out on 767, and it seems to work fine. I did not test on 656. > The bundle can be downloaded from > http://dev.laptop.org/raw-attachment/ticket/9112/Browse-101.xo > Thanks, > Sayamindu > > > On Tue, Dec 23, 2008 at 8:54 PM, Greg Smith > wrote: > > Hi Sayamindu, > > > > Do you think the new browse version (101?) has been shown to solve the > > problem Emliano raised here? > > http://www.mail-archive.com/devel@lists.laptop.org/msg14839.html > > > > Has it been tested with build 656 or only 767 (8.2)? > > > > If we have verified that it solves the issue raised, let's ask him to try > it > > out. > > > > Thanks, > > > > Greg S > > > > > > -- > Sayamindu Dasgupta > [http://sayamindu.randomink.org/ramblings] > ___ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/devel > -- Emiliano Pastorino LATU - Plan Ceibal Av. Italia 6201 CP: 11500, Montevideo, Uruguay Tel: (598 2) 601 3724 int.: 469 ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: New staging build 7
Hi Reinier, IMHO it would be beneficial to use the previous release as base for these logs, like I did in my scripts: http://dev.laptop.org/~bert/staging-pkgs.html Otherwise it's hard to tell what actually changed while staging. - Bert - On 24.12.2008, at 01:03, Build Announcer v2 wrote: > http://xs-dev.laptop.org/~cscott/xo-1/streams/staging/build7 > > Changes in build 7 from build: 0 > > Size delta: 245.36M > > +olpc-library-common 1-30 > +openssh-server 5.1p1-2.fc9 > +pyabiword 0.6.1-4.olpc3 > +python-alsaaudio 0.3-1.fc9 > +pygtksourceview 2.2.0-1.fc9 > +pygame 1.8.0-1.olpc3.3 > +olpc-netutils 0.7-1.fc9 > +olpc-utils 0.89-5.olpc3 > +olpcsudo 1.4-1 > +olpcsound 5.08.92-11.olpc3 > +openssh-clients 5.1p1-2.fc9 > +olpcrd 0.49-0 > +olpc-licenses 8.2.0.0-1.olpc3 > +ntp-ntpdate 4.2.4p4-7.olpc3 > +ohm 0.1.1-6.21.20080921git.olpc3 > +nano 2.0.6-4.fc9 > +lrzsz 0.12.20-23.fc9 > +ltrace 0.5-10.45svn.fc9 > +nafees-web-naskh-fonts 1.0-1.fc8 > +mtd-utils 1.2.0-1.fc9 > +mailcap 2.1.28-1.fc9 > +gtk2-engines 2.14.3-1.fc9 > +gnash-plugin 0.8.3-1.olpc3.2 > +kernel 2.6.25-20080925.1.olpc.f10b654367d7065 > +libXdamage 1.1.1-4.fc9 > +libxml2-python 2.7.1-1.fc9 > +libertas-usb8388-firmware 2:5.110.22.p23-1.olpc3 > +lohit-fonts-hindi 2.2.1-2.fc9 > +iptables-ipv6 1.4.1.1-2.fc9 > +hulahop 0.4.6-1.olpc3 > +gzip 1.3.12-6.fc9 > +eject 2.1.5-11.fc9 > +bootanim 1.3-1 > +espeak 1.31-5.fc9 > +etoys 3.0.2153-1 > +gettext 0.17-4.fc9 > +gdb 6.8-21.fc9 > +file 4.23-5.fc9 > +cerebro 2.9.16-1.olpc3 > +bzip2 1.0.5-2.fc9 > +compat-libstdc++-33 3.2.3-63 > +anacron 2.3-59.fc9 > +diffutils 2.8.1-21.fc9 > +ds-backup-client 0.8.1-1.olpc3 > +dejavu-lgc-fonts 2.24-3.fc9 > +dbus-x11 1.2.1-1.fc9 > +PolicyKit-olpc 1.2-1.fc9 > +alsa-utils 1.0.17-2.fc9 > +Mothanna-fonts 0.02-3.olpc3 > +abyssinica-fonts 1.0-2.fc8 > +Thabit-fonts 0.02-3.fc9 > +avahi-dnsconfd 0.6.22-10.fc9 > +xorg-x11-drv-cirrus 1.2.0-1.fc9 > +xorg-x11-drv-fbdev 0.3.1-7.fc9 > +xorg-x11-drv-geode 2.10.1-1.fc9 > +xorg-x11-drv-vmware 10.16.0-1.fc9 > +xorg-x11-utils 7.4-2.olpc3 > +xorg-x11-xinit 1.0.9-1.fc9 > +yum 3.2.19-3.1.olpc3 > +ConsoleKit 0.2.10-3.fc9 > +ConsoleKit-libs 0.2.10-3.fc9 > +ConsoleKit-x11 0.2.10-3.fc9 > +GConf2 2.22.0-1.fc9 > +MAKEDEV 3.23-5.fc9 > +NetworkManager 1:0.6.5-0.12.svn3246.olpc3 > +ORBit2 2.14.12-3.fc9 > +PolicyKit 0.8-3.fc9 > +SDL 1.2.13-4.fc9.1 > +SDL_Pango 0.1.2-8 > +SDL_image 1.2.6-6.fc9 > +SDL_mixer 1.2.8-8.olpc3.1 > +SDL_ttf 2.0.9-4.fc9 > +acl 2.2.47-2.fc9 > +agg 2.5-6.fc9 > +alsa-lib 1.0.17-2.fc9 > +atk 1.22.0-1.fc9 > +atlas 3.6.0-15.fc9 > +audit-libs 1.7.5-1.fc9 > +avahi 0.6.22-10.fc9 > +avahi-autoipd 0.6.22-10.fc9 > +avahi-glib 0.6.22-10.fc9 > +avahi-gobject 0.6.22-10.fc9 > +avahi-tools 0.6.22-10.fc9 > +basesystem 8.1-1 > +bash 3.2-22.fc9 > +blas 3.1.1-4.fc9 > +boost 1.34.1-15.fc9 > +bootfw q2e24-1.olpc2.unsigned > +bzip2-libs 1.0.5-2.fc9 > +cairo 1.6.4-1.fc9 > +chkconfig 1.3.37-2 > +coreutils 6.10-30.fc9 > +cpio 2.9-8.fc9 > +cpp 4.3.0-8 > +cracklib 2.8.12-2 > +cracklib-dicts 2.8.12-2 > +cronie 1.0-7.fc9 > +crontabs 1.10-19.fc9 > +cryptsetup-luks 1.0.6-2.fc9 > +cups-libs 1:1.3.7-8.fc9 > +cyrus-sasl-lib 2.1.22-15.fc9 > +db4 4.6.21-6.fc9 > +dbus 1.2.1-1.fc9 > +dbus-glib 0.74-8.fc9 > +dbus-libs 1.2.1-1.fc9 > +dbus-python 0.83.0-3.fc9 > +desktop-file-utils 0.15-1.fc9 > +rainbow 0.7.24-1.fc9 > +python-json 3.4-3.fc9 > +python-sqlite2 1:2.3.3-3.fc9 > +rdesktop 1.6.0-1.fc9 > +strace 4.5.16-5.fc9 > +sugar-evince-python 2.20.1.1-3.olpc3 > +sugar-journal 100-1.olpc3 > +sugar-update-control 0.17.1-1 > +tar 2:1.19-4.fc9 > +thaifonts-scalable 0.4.9-3.fc9 > +totem-mozplugin 2.23.4-1.olpc3.6 > +tree 1.5.0-9.fc9 > +unzip 5.52-9.fc9 > +vim-minimal 2:7.1.291-1.fc9 > +vnc 4.1.2-31.fc9 > +vte 0.16.13-1.fc9 > +which 2.19-3.fc9 > +wvdial 1.60-5.fc9 > +device-mapper 1.02.24-11.fc9 > +device-mapper-libs 1.02.24-11.fc9 > +dhclient 12:4.0.0-17.fc9 > +dhcp 12:4.0.0-17.fc9 > +dirmngr 1.0.1-2.fc9 > +djvulibre-libs 3.5.20-2.fc9 > +dmidecode 1:2.9-1.30.1.fc9 > +dnsmasq 2.41-0.8.fc9 > +e2fsprogs 1.40.8-3.fc9 > +e2fsprogs-libs 1.40.8-3.fc9 > +elfutils-libelf 0.135-1.fc9 > +enchant 1:1.4.2-2.fc9 > +ethtool 6-1.fc9 > +expat 2.0.1-5 > +fedora-release 9-5.transition.1 > +file-libs 4.23-5.fc9 > +filesystem 2.4.13-1.fc9 > +findutils 1:4.2.33-3.fc9 > +flac 1.2.1-4.fc9 > +fontconfig 2.5.0-2.fc9 > +freetype 2.3.5-6.fc9 > +fribidi 0.19.1-2.fc9 > +gamin 0.1.9-5.fc9 > +gawk 3.1.5-17.fc9 > +gdbm 1.8.0-28.fc9 > +glib2 2.16.5-1.fc9 > +glibc 2.8-8 > +glibc-common 2.8-8 > +gmp 4.2.2-7.fc9 > +gnash 0.8.3-1.olpc3.2 > +gnome-mime-data 2.18.0-2.fc7 > +gnome-python2 2.22.1-3.olpc3 > +gnome-python2-gnomevfs 2.22.1-3.olpc3 > +gnome-python2-libwnck 2.22.0-4.fc9 > +gnome-python2-rsvg 2.22.0-4.fc9 > +gnome-vfs2 2.22.0-3.olpc3 > +gnupg2 2.0.9-1.fc9 > +gnutls 2.0.4-3.fc9 > +gpgme 1.1.6-3.fc9 > +grep 2.5.1-59.fc9 > +gstreamer 0.10.12-3.olpc3 > +gstreamer-plugins-base 0.10.12-4.olpc3.4 > +gstreamer-plugins-flumpegdemux 0.10.15-2.fc9 > +gstreamer-plugins-good 0.10.5-7.olpc3.1 > +gstreamer-python 0.10.7-2.olpc3.1 >
Re: Scratch on XO is frozen after standby
This is a long-standing kernel bug. Sleep/resume is supposed to be transparent to user-space processes. Could you add your findings to the ticket, please? http://dev.laptop.org/ticket/6201 - Bert - On 24.12.2008, at 07:43, Philipp Kocher wrote: > Hi John > > Etoys has exactly the same problem (etoys is frozen and the line > "snd_pcm_writei returned -86" gets written endlessly into the etoys > logfile). > > Sorry, I don't know anything about DBus. > > To reproduce with Etoys: > 1. Open etoys on the Xo > 2. Click on "make A Project" > 3. Click on "Supplies" > 4. Drag and drop the "Sound recorder" > 5. Record a sound > 6. Play the recording > 7. Press XO power button (just short so the XO goes in standby mode > with dark screen) > 8. Press XO power button (again just short) > 9. Etoys is frozen > > Scratch: > We have the frozen Scratch problem very often at the moment because > we are using Scratch and record sounds (about 3-5 students of 30 per > lesson). It really bad since saving the project is not possible > anymore. > > First I thought it is because we switched on experimental Power > Management. But now it is switched off and the problem is still here. > > It is just Scratch that freezes, Sugar is still working fine. > I don't remember having seen this problem on older sugar builds e.g. > 656 or 708 and we used Scratch intensively on this builds. > > Regards, > Philipp > > John Maloney wrote: >> Wow, first I've heard about this problem. I wonder if Etoys has the >> same problem? >> The problem appears to be have something to do with having the ALSA >> sound output port open when the XO goes to sleep. This may actually >> be an ALSA/sleep issue but it may be easier to work around it than >> to fix ALSA. >> Is there a DBus message or event that says when the machine is >> about to go to sleep? >>-- John >> On Dec 23, 2008, at 9:56 PM, Philipp Kocher wrote: >>> Hi John >>> >>> We have a big problem with Scratch version 11 and 12 on the XO >>> (build 767). >>> >>> After not using the XO for some minutes Scratch freezes completely >>> (no drag and drop and no buttons can be pressed anymore). The >>> following line gets written in the scratch logfile in an endless >>> loop (if scratch doesn't get killed, the logfile uses multiple MB): >>> snd_pcm_writei returned -86 >>> >>> The problem can be reproduced easily: >>> 1. Start Scratch >>> 2. Record sound and play the sound >>> 3. Press XO power button (just short so the XO goes in standby >>> mode with dark screen) >>> 4. Press XO power button (again just short) >>> 5. Scratch is frozen >>> >>> Regards, >>> Philipp >>> Pepyride School >>> Cambodia >>> >>> PS: Are you using the bug tracking page on dev.laptop.org for XO >>> related bugs of Scratch? ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: New joyride build 2605
>>> +sugar-base 0.83.2-2.olpc4 >> >> Good to see this up-leveled -- the previous version of this package >> as distributed in Joyride was more than a month old. >> >> However, that still leaves several packages which appear to be more >> recent in 'olpc3' than in 'olpc4'. Output of 'yum check-update' : >> >> | pyabiword.i386 0.6.1-4.olpc3 >> | python-telepathy.noarch 0.15.3-1.olpc3 >> | sugar-journal.noarch 100-1.olpc3 >> | xorg-x11-drv-evdev.i386 2.0.8-1.fc9 > > I can comment on a couple of these, but I'm not sure how to fix them: > > * pyabiword is newer in olpc3 than fc10, but the spec files are > basically the same - the olpc3 one seems to have had a no-change > rebuild which bumped the version number higher than the fc10 version. > There's no olpc4 version as we do not need to fork from the F-10 > version - so we should get the fc10 version into joyride. > > * python-telepathy has the same version 0.15.3-1 in fc10 and olpc3. We > should also be using the fc10 version here as we have rebased on F-10 > and olpc3 was built on F-9. There's no need for an olpc4 fork of the > package as we are using the same version as Fedora. > > * sugar-journal is no longer a separate package in Sugar 0.83, so > there should not be a sugar-journal included in Joyride at all. The > sugar package includes the journal functionality now. Basically I think these just need to be untagged in koji. I can look at doing these in a couple of days when I get a proper internet connection back. Peter ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
New joyride build 2608
http://xs-dev.laptop.org/~cscott/olpc/streams/joyride/build2608 Changes in build 2608 from build: 2607 Size delta: 0.00M -audit-libs 1.7.9-1.fc10 +audit-libs 1.7.10-1.fc10 -- 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
