Re: unable to share Activities on XO-1.5
G'day Adam, http://laptop.org/7.1.0/gettingstarted/sharing.shtml is correct as far as it goes, and is the method I've used to test sharing between two XO-1.5 running os116. I didn't experience any difficulty, but the sharing does depend on the environment. I've had it working via ad-hoc "Create new wireless network" and via access point. I've no cable available. There are several ways it can fail, but the sample problem report suggests that a slow or lossy network (Abiword in two minutes) was the main problem. The usual causes of a slow or lossy network are radiofrequency interference or other wireless traffic nearby. I'd like to know if the XO-1 was tested in the same location and at the same time, and if so whether the XO-1's were configured or had settled on mesh channel 1. Further diagnosis of the problem is certainly possible using shell tools in the Terminal window, but I'm not sure if you want that level of detail. -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: New XO-1.5 10.2.0 build 116
Hi, > First problem I have run into is that I see a problem with > wireless networks after rebuilding. They showed up for about 30 > seconds and then disappeared. >From http://wiki.laptop.org/go/XO_1.5_B2#Software_Limitations : * If you have a B2 without hardware mods, you must disable suspend using Control Panel->Power->Automatic power management, else your wireless device will disconnect on suspend and not come back until the next reboot. - Chris. -- Chris Ball One Laptop Per Child ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
unable to share Activities on XO-1.5
Many people here in DC tried to share Sugar Activities (during the XO-1.5 Getting Started Documentation Sprint this weekend), but were unable to proceed, and unable to take the required screenshots to document this functionality. Below is a sample problem report. What workarounds might they try? Thanks! We (GH & SU) had access to multiple XO-1.5's for the first time. Attempting to upgrade the manual page http://laptop.org/7.1.0/gettingstarted/sharing.shtml we were (consistently) unable to make this Activity sharing happen. Whereas we've both succeeded with the XO-1, several times. Testing setup: 2 XO-1.5, both SKU99 (early production units) Software: Build 116 Sugar 0.84.14 Firmware Q3A35 Wireless Firmware 9.70.7.p0 We tested this with cable and wifi both. Chat was never really working on the joining computer. Greatest success (like in the picture) was the message that the other host connected, but no actual text transmitted... Abiword worked but only after 2min of waiting (and only with wifi). The invitation mode never worked. <>___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: (fwd) Re: powerd on XO-1 (was Re: New release ... OS13 )
p...@laptop.org said: > please file tickets for the problems you're seeing, and attach dmesg output, > as well as powerd.trace. (enable powerd tracing with "sudo powerd-config > =trace-on".) http://dev.laptop.org/ticket/10092 If that's not the info you need, let me know and I'll try again. -- These are my opinions, not necessarily my employer's. I hate spam. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: New XO-1.5 10.2.0 build 116
On Wed, Mar 24, 2010 at 2:18 PM, Chris Ball wrote: > http://wiki.laptop.org/go/F11_for_1.5 > http://build.laptop.org/10.2.0/os116 > > Compressed image size: 678.37mb (+0.01mb since build 115) > > Description of changes in this build: > * powerd: fix auto-reconnection after an idle-suspend (#10086) > * pull F11 updates > > Package changes since build 115: > > -bind-libs-9.6.2-1.fc11.i586 > +bind-libs-9.6.2-2.P1.fc11.i586 > -bind-utils-9.6.2-1.fc11.i586 > +bind-utils-9.6.2-2.P1.fc11.i586 > -olpc-powerd-13-1.fc11.i586 > +olpc-powerd-15-1.fc11.i586 > -openssl-0.9.8k-5.fc11.i686 > +openssl-0.9.8m-1.fc11.i686 I finally got my XO-1.5 back from my 9 year old to do some updates and testing. It was running the final from January so has not been updated in a while. I updated first the firmware to q3a35.rom and then the OS to os116.zd First problem I have run into is that I see a problem with wireless networks after rebuilding. They showed up for about 30 seconds and then disappeared. From the lack of yellow lights on the wireless I believe it quit scanning at that point. I then did a soft reboot and saw that the network did not seem to come back. I need to troubleshoot that so any help would be appreciated. [ A complete power cycle brought back the radio and I was able to reconnect with WPA2 again. However about 60 seconds later the radio light went off the screen and networking went away. The dmesg shows a mmc2 dump and lines saying "mmc2: Got data interrupt 0x0010 even though no data operation was in progress.] Next problem was touching the power button caused the screen to go 'crazy' for a bit. [As it it were at the wrong sync rate on an old monitor. I touched the power button again and it went to sleep. Not sure if that is expected or not. Do I need to go back to a different firmware? -- Stephen J Smoogen. Ah, but a man's reach should exceed his grasp. Or what's a heaven for? -- Robert Browning ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: ANNOUNCE: New F11 XO-1build 115 Paraguay
On Sat, 2010-03-27 at 13:44 +0100, Martin Langhoff wrote: > On Sat, Mar 27, 2010 at 7:58 AM, Yioryos Asprobounitis > wrote: > > I'll go with Mikus on that. > > With at least 3 development streams some qualifier is needed in the naming. > > eg os115x1/os115x15/os115py > > +1 -- and remember to keep it all 8.3 :-) Done: the next image will be called something like "os117py.img" I've always wondered why the XO builds don't have a real name. Everyone seems to generically refer to them as "OS". For some time, I've been calling it "xoos", then I realized I was the only one and gave up. Analogously, f11-xo1 is hardly pronounceable and f11-xo1-py is even worse. Where's Steve Jobs when we need him? -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: New release of F11 for the XO-1 is available for testing - OS13
On Sun, 2010-03-28 at 15:51 -0500, Mikus Grinbergs wrote: > Another question, if I may -- os13 comes with a 2010/03/13 XO-1 kernel > (commit bfcaa33). Is it ok to install the newer 2010/03/22 XO-1 kernel > (commit 3f93d90) in my os13 system ? Please try and let me know. I froze on that version because some XO-1 specific bugs had appeared in the following revisions. Those may have gone by now. To install a kernel on the XO-1, you need to do some trickery: rpm -i kernel-* rsync -a /boot/ /versions/running/boot/ This is due to the odd filesystem layout used to implement the alternate boot scheme (I wonder how many people actually use it and if it's still worth keeping). -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: problems with an XO
On Sun, Mar 28, 2010 at 01:48:20PM -0400, Rodolfo D. Arce S. wrote: > Checking > Writing > Error, SPI Flash ID 0 > ok <- this is the prompt.. This is bad. Something went wrong while writing to the chip that contains the firmware. (If anybody else gets this error during flashing and your laptop is still on, don't turn it off, leave it powered on while you try to contact us for help.) That it doesn't boot the firmware any longer is consistent with the error above. That laptop will need a repair; http://wiki.laptop.org/go/SPI_FLASH_Recovery -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] Journal Backup/Restore UI
On Sun, 2010-03-28 at 21:22 -0300, Bernie Innocenti wrote: > Oh, well, indeed. Though we need to figure out how to glue it to the > rsync back-end. > > The easy part is binding rsync to Python: this was already done in > duplicity by wrapping librsync with simple C and Python code which we > could steal. Wait, I had overlooked this note: librsync does not speak the (hairy) application-specific protocol used by rsync. They only share an algorithm, not any code. This rules it out for our usecase, unless we also want to rewrite the xs backend. -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] Journal Backup/Restore UI
On Sun, 2010-03-28 at 20:08 +0200, Martin Langhoff wrote: > On Sun, Mar 28, 2010 at 2:29 PM, Bernie Innocenti wrote: > > On Sun, 2010-03-28 at 14:14 +0200, Tomeu Vizoso wrote: > >> I'm a bit confused, is the problem reliable full restore with limited > >> local space or the DS having the xapian DB open while the copy > >> happens? Or both? > > > > Both, but somehow we managed to solve them in a quick & dirty way: > > Doesn't copy-to-journal skip all the ugly? Oh, well, indeed. Though we need to figure out how to glue it to the rsync back-end. The easy part is binding rsync to Python: this was already done in duplicity by wrapping librsync with simple C and Python code which we could steal. Then it starts to get hard: the files are probably going to come down from the xs in some random order. librsync provides a sophisticated callback interface, but there seems to be also a whole-file interface. This approach also opens other interesting possibilities such as restoring individual files or merging the backup with the current journal contents. However, it looks like it would take a couple of months of effort to get something like this done. For the time being, we could keep using the plain rsync and maybe just add a stop/resume interface to the datastore? -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: powerd on XO-1 (was Re: New release ... OS13 )
On Sat, Mar 27, 2010 at 16:42, Paul Fox wrote: > steven m. parrish wrote: > > OS13 is now available for testing. I just tried it and am encountering a very annoying issue: if I don't do anything, the screen dims, and everything just freezes this way. Screen remains dim, keyboard and mouse don't respond. Is this a known issue? Any idea how I could help debugging it? -- Mathieu Bridon ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [IAEP] ANNOUNCE: New F11 XO-1build 115 Paraguay
:) Good job!! Claudia On Fri, Mar 26, 2010 at 3:17 PM, Martin Langhoff wrote: > On Fri, Mar 26, 2010 at 6:47 PM, Bernie Innocenti > wrote: > > Our short-term goal is to meet a release criteria of "no > > regressions against build 801". Once this is done, we'll re-sync with > > the latest improvements from our upstreams, F11-XO1.5 and F11-XO1. > > Bravo. To Stephen, to all the ParaguayEduca folks pushing for this. To you. > > cheers, > > > > m > -- > martin.langh...@gmail.com > mar...@laptop.org -- School Server Architect > - ask interesting questions > - don't get distracted with shiny stuff - working code first > - http://wiki.laptop.org/go/User:Martinlanghoff > ___ > IAEP -- It's An Education Project (not a laptop project!) > i...@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/iaep > ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: New release of F11 for the XO-1 is available for testing - OS13
Thanks for explaining about os13 not using the Feb 2010 NetworkManager. Another question, if I may -- os13 comes with a 2010/03/13 XO-1 kernel (commit bfcaa33). Is it ok to install the newer 2010/03/22 XO-1 kernel (commit 3f93d90) in my os13 system ? mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] Journal Backup/Restore UI
On Sun, Mar 28, 2010 at 2:29 PM, Bernie Innocenti wrote: > On Sun, 2010-03-28 at 14:14 +0200, Tomeu Vizoso wrote: >> I'm a bit confused, is the problem reliable full restore with limited >> local space or the DS having the xapian DB open while the copy >> happens? Or both? > > Both, but somehow we managed to solve them in a quick & dirty way: Doesn't copy-to-journal skip all the ugly? m -- martin.langh...@gmail.com mar...@laptop.org -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sur] XO para ciegos y disminuidos visuales.
2010/3/28 Tomeu Vizoso : > was wondering if you were already aware of this request from the field. The wording of the request is a bit confusing, so to clarify, I think Walter means that we're missing the dots on the keys F J and 5 (in num keypad). But actually... they are present, and I can feel them. So it's a feature request for something we have... m -- martin.langh...@gmail.com mar...@laptop.org -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: problems with an XO
Hello: Machine SKU26, Serial: SHF8220176E Model XO-1 I can't say it stoped in the middle of the upgrade, it failed after everything finished.. it was like this.. i got the q2e41.rom file in a sd card, i ran the command ok flash sd:\q2e41.rom checking.. writing.. checking.. and than something else.. and apparently finished.. cuase i didn't came back until about 15 min later.. (i went to the grocery store.. haha).. and when i came back.. the screen showed: Checking Writing Error, SPI Flash ID 0 ok <- this is the prompt.. But i was not allowed to write anymore.. nor to reboot or anything.. y unplugged the AC power, but the led remained on.. that's where i figured it REALLY failed, 'cause if it failed in one of the testings or such, during firmware installation if it fails it still maintains the old firmware, and the prompt works.. but that didn't happen in this occasion I tryed to reboot with the prompt, didn't work, I tryed to turn off using power button, didn't work, y disconected power (again), didn't work.. so I removed the battery.. and it powered off.. when i turned on.. nothing.. black screen of Firmware death (bricked).. but it didn't happen during upgrade.. it happened when upgrade aparently finished cheers.. R El 28 de marzo de 2010 13:28, Raúl Gutiérrez Segalés escribió: > But I agree with Bernie, question is why it died half way through.. > > On Sun, 2010-03-28 at 14:28 -0300, Raúl Gutiérrez Segalés wrote: > > I pretty much think the laptop has been bricked. And if I recall > > correctly that is an XO-1 (MP: mass production). If the upgrade process > > of the firmware dies in the middle, you are definitively bricked :( > > > > On Sat, 2010-03-27 at 21:59 -0400, Rodolfo D. Arce S. wrote: > > > Hello: > > > > > > I have problems with an XO. I tried to install the latest build on it, > > > but had the firmware version q2e18, so I upgraded it to the q2e41 > > > > > > I used the q2e41.rom file.. and at the end of the upgrade i threw an > > > error somthing that said "Error, SPI Flash ID 0" it didn't enable the > > > prompt again, nor any of the buttons (power, check, circle, square, > > > etc) > > > > > > When i rebooted, the machine doesn't start on fimrware.. it just shows > > > a black (no backlight) screen > > > > > > Was there an issue regarding upgrade from q2e18 to q2e41? on the page > > > even showed an example of the q2e18 upgrade > > > > > > http://wiki.laptop.org/go/OLPC_Firmware_q2e41 > > > > > > could you guys point me in the right way regarding this problem? > > > > > > cheers.. R > > > > > > -- > > > Rodolfo D. Arce S. > > > www.rodolfoarce.com > > > > > -- Rodolfo D. Arce S. www.rodolfoarce.com ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: New release of F11 for the XO-1 is available for testing - OS13
hal wrote: > > ber...@codewiz.org said: > > We'll deploy this to ~4000 kids really-soon-now. Bugs reported within 1-2 > > weeks have a chance of being fixed in time. > > os115 doesn't include powerd. Is your plan to ship it that way or do you > want help testing suspend/resume? given the release schedule, i'm not at all surprised that bernies is sticking with ohmd. > > I ran it for a day or two before switching to os13. I didn't notice any > troubles. > > os13 includes powerd. My network gets confused/broken quickly. It > recovers, > but that takes a minute. That's not useful for me. and indeed, it sounds like the ohmd may be the right choice. ;-) paul > > The good news is that the keyboard now works after resume so I can poke > around. > > I don't know if the keyboard/cursor/resume quirk is really fixed. My cursor > just stopped working. (The keyboard was OK.) > > I haven't noticed any troubles when powerd is disabled. > > > -- > These are my opinions, not necessarily my employer's. I hate spam. > > > > ___ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/devel =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: (fwd) Re: powerd on XO-1 (was Re: New release ... OS13 )
yioryos wrote: > So SLEEP basically drops connections and then the XO-1 fails > to DIM or BLANK. Setting SLEEP time _after_ DIM and BLANK has sounds like something's going wrong for you that isn't going wrong for me: dim and blank happen correctly after sleep for me. > the expected behavior. In all cases the XO fails to reconnect > to the preferred network after wakeup from SLEEP. I settled i haven't tested networking robustness on os13, so can't speak to this. please file tickets for the problems you're seeing, and attach dmesg output, as well as powerd.trace. (enable powerd tracing with "sudo powerd-config =trace-on".) paul > in DIM=180, BLANK=480, SLEEP=600. No huge power savings but > at least the build is usable. > > > --- On Sat, 3/27/10, Paul Fox wrote: > > > From: Paul Fox > > Subject: Re: (fwd) Re: powerd on XO-1 (was Re: New release ... OS13 ) > > To: "Yioryos Asprobounitis" > > Cc: "OLPC Devel" , "fedora-olpc-list" > > > Date: Saturday, March 27, 2010, 1:26 PM > > yioryos wrote: > > > I guess the question is: is os13 usable at this > > stage? > > > Should power management be be inactivated in the > > control panel? > > > Are there appropriate/recommended powerd.conf > > settings for the XO-1 at this > > > stage? > > > > maybe, i don't know, and i don't know. > > > > paul > > =- > > paul fox, p...@laptop.org > > > > > =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: problems with an XO
Adding Mitch Bradley and olpc-devel to Cc. On Sat, 2010-03-27 at 21:59 -0400, Rodolfo D. Arce S. wrote: > Hello: > > I have problems with an XO. I tried to install the latest build on it, > but had the firmware version q2e18, so I upgraded it to the q2e41 > > I used the q2e41.rom file.. and at the end of the upgrade i threw an > error somthing that said "Error, SPI Flash ID 0" it didn't enable the > prompt again, nor any of the buttons (power, check, circle, square, > etc) > > When i rebooted, the machine doesn't start on fimrware.. it just shows > a black (no backlight) screen > > Was there an issue regarding upgrade from q2e18 to q2e41? on the page > even showed an example of the q2e18 upgrade > > http://wiki.laptop.org/go/OLPC_Firmware_q2e41 > > could you guys point me in the right way regarding this problem? Was that a B1 pre-production unit, perhaps? If I remember correctly, the current versions of the Open Firmware do not support those ancient boards any longer. Flashing a B1 may very well result in a brick :-( Mitch may know better. -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] Journal Backup/Restore UI
On Sun, 2010-03-28 at 14:14 +0200, Tomeu Vizoso wrote: > I'm a bit confused, is the problem reliable full restore with limited > local space or the DS having the xapian DB open while the copy > happens? Or both? Both, but somehow we managed to solve them in a quick & dirty way: 1) our script kills the datastore process before starting the restore. Then, at the end of the procedure, we restart Sugar. 2) we restore the journal in place, using the --delete-before option of rsync in order to free up space in the filesystem beforehand I've tested this procedure yesterday in a school, and it worked egregiously with two different laptops. The code is here: http://trac.paraguayeduca.org/browser/scripts/os-modifications/diario-restaurar Now we're "just" missing a nice GUI for end-users: a control panel icon or a button in the journal toolbar. Someone has to file a feature request and discuss it with the Design team. Would anyone like to get started on this while we're still busy fixing the few remaining high-priority bugs in Sugar 0.84? -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] Journal Backup/Restore UI
I'm a bit confused, is the problem reliable full restore with limited local space or the DS having the xapian DB open while the copy happens? Or both? Thanks, Tomeu On Fri, Mar 26, 2010 at 00:51, Bernie Innocenti wrote: > In Paraguay, we started discussing the topic of improving backup and > restore procedures. Let's compare notes with a wider audience. > > We started from an existing backup/restore procedure written by Daniel > Drake one year ago. It's meant to be invoked from the Terminal and uses > a transactional approach: > > 1) the technician runs a script to restore the journal from the school > server into a temporary directory while Sugar is still running; > > 2) then, you restart Sugar (by killing the sugar-shell process); > > 3) on startup, the olpc-session script notices the temporary directory > and replaces the datastore with it almost atomically. > > The problem with this approach was that it only works as long as there's > a enough free space in the filesystem, which is rarely the case with > laptops that are actually in use. Transactional behavior would be good > to have, but I don't see how we could implement it reliably. Even an > rsync in-place would have to be done with --delete-before to ensure it > works all the time. > > This opens the question of how we stop the datastore from accessing the > journal and mess it up while we're still updating it. We're currently > doing it quite a gross way: kill the datastore process before beginning > the restore, then restart Sugar: > > http://trac.paraguayeduca.org/browser/scripts/os-modifications/diario-restaurar > > We'll thoroughly test this new kludge tomorrow. I'm confident it will > work, but it's a shame that users need to call tech support in order to > restore a backup. > > Perhaps it's time to add integrated backup/restore functionality to the > datastore itself, with a nice UI in the Journal or in the control panel. > The underlying mechanism could be as simple as the one we're testing > now, but with proper synchronization with the datastore and no need to > restart Sugar. > > Shall we go on and write a feature page, targeting 0.90? If it's done as > a control panel item, it may be sufficiently self-contained to backport > it all the way back to 0.84. > > For the time being, I might add the backup and restore scripts to > olpc-utils. Or, better, create a new sugar-utils package for these > things that are generally useful on any platform. > > Suggestions? > > -- > // Bernie Innocenti - http://codewiz.org/ > \X/ Sugar Labs - http://sugarlabs.org/ > > ___ > Sugar-devel mailing list > sugar-de...@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Fwd: [Sur] XO para ciegos y disminuidos visuales.
Hi John, was wondering if you were already aware of this request from the field. Regards, Tomeu -- Forwarded message -- From: Rafael Enrique Ortiz Guerrero Date: 2010/3/26 Subject: Re: [Sur] XO para ciegos y disminuidos visuales. To: "OLPC para usuarios, docentes, voluntarios y administradores" 2010/3/25 Walter Bender : > 2010/3/25 Walter Alan Mirwald : >> El teclado qwerty de las computadoras o celulares usualmente viene con 3 >> teclas marcada para el uso de personas ciegas o con disminución visual, la >> letra F, la letra J, y 5 del teclado numérico. Me parece importante ver la >> posibilidad de modificar el teclado de las XO pues no están marcadas. Eso >> ayudaría a las personas C y DV ubicarse rápidamente en el teclado. >> > > F y J tienen protuberancias en el teclado XO. Pero tal vez son > demasiado sutiles. Estoy de acuerdo estas marcas son solo ''puntos'' en las XO, en laptops normales son mas apreciables. > -walter > >> >> Me interesa conocer mas de los proyectos educativos, desarrollo de softh y >> actividades para sujetos con necesidades educativas especiales Por favor. >> Gracias. >> >> >> >> Walter Mirwald >> >> La Rioja - Argentina >> >> profeespecialwal...@hotmail.com >> >> >> >> >> >> >> Tu Hotmail guarda el borrador que estás escribiendo para que no pierdas tu >> mensaje. Conocé cómo >> ___ >> Lista olpc-Sur >> olpc-...@lists.laptop.org >> http://lists.laptop.org/listinfo/olpc-sur >> >> > > > > -- > Walter Bender > Sugar Labs > http://www.sugarlabs.org > ___ > Lista olpc-Sur > olpc-...@lists.laptop.org > http://lists.laptop.org/listinfo/olpc-sur > ___ Lista olpc-Sur olpc-...@lists.laptop.org http://lists.laptop.org/listinfo/olpc-sur ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: To Gnome or not to Gnome
On Fri, Mar 26, 2010 at 13:04, Bernie Innocenti wrote: > On Fri, 2010-03-26 at 03:47 -0700, Yioryos Asprobounitis wrote: >> > You mean the blacked out GTK buttons and corrupt graphics >> > in some web pages? We have a temporary workaround for these now! >> >> No, actually I was referring to an XO-1.5 bug (#10084) > > Ah, it's a different one. Yesterday I closed #7830 and #10076, though > with a temporary work-around. > > The ultimate fix for all these bugs would have been a complete > refactoring of the geode driver. Last time I looked at that codebase, it > was full of magic numbers, with no bounds checking in some cases. We're > very lucky if it works so well :-) > > >> > Sounds right, but I'm not sure *who* is going to put their >> > time into it. >> >> What about "Gnome people". I would guess they will not be indifferent >> to the OLPC/XO. Couldn't they be "formally" asked for support? >> (I know is upstream but...) > > Do you have good contacts within the Gnome community? We could talk about this with the GNOME Foundation's board, they have interest in pushing GNOME in developing countries. But the most they could do (AFAIK) is motivating contributors to give some attention to the issues we care about, but not more. If anybody wants to take ownership of this area, I can give contacts and introduce them to the board. Regards, Tomeu > I reported only one bug in the Gnome bug tracker, but so far nobody > replied: > > https://bugzilla.gnome.org/show_bug.cgi?id=613852 > > In this case, we're using current software which is shipped also by > Fedora 12 and Karmic. > > -- > // Bernie Innocenti - http://codewiz.org/ > \X/ Sugar Labs - http://sugarlabs.org/ > > ___ > olpc mailing list > o...@lists.fedoraproject.org > https://admin.fedoraproject.org/mailman/listinfo/olpc > ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
