Re: [Sugar-devel] XO-system 1a builds
On 28/10/13 22:12, James Cameron wrote: On Mon, Oct 28, 2013 at 09:01:02PM +1300, Tom Parker wrote: zdextract in the bios-crypto package will unpack it, giving you a disk image, which you can then loopback mount as a filesystem and compare with another filesystem. http://wiki.laptop.org/go/User:Quozl/Remastering is an example use of zdextract for adding files to a build without having to re-run the builder. hasn't been tested since 2012, but it should help you understand zdextract. Thank you! I modified your remastering script to leave the filesystems mounted. Then I used diff to compare them manually. My script is attached, along with another script to unmount and release the loopbacks. The difference between 32049oe4.zd and 32050oe4.zd appears to be a changed flashplayer. 50 and 51 have a bunch of activity and translation changes. mount-zd.sh Description: application/shellscript umount-zd.sh Description: application/shellscript ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Using a new keyboard layout for XO4
On 21/11/13 23:27, Basanta Shrestha wrote: Dear all, We are planing on using a different keyboard layout for XO4. The new layout we think is phonetically based and easier for children. I simply switched the /usr/share/X11/symbols/np file with a new one but did not work. I guess there are some other works that needs to be done before we can use this file. Can you suggest what needs to be done? The layout I want to use is http://nepalinux.org/input/ne We did this for Maori. We used James's Tiny Core Linux based customization stick. See http://carrott.org/git/mktinycorexo_nz.git/blob/HEAD:/scripts/asroot for the script that is run _before the first boot of the laptop_ to insert the Maori keyboard, change the keyboard configuration and update the Maori translations. The Maori keyboard is called mi. You may also be interested in http://carrott.org/git/mktinycorexo_nz.git/blob/HEAD:/scripts/asolpc which changes the user's locale preferences. See http://carrott.org/git/mktinycorexo_nz.git/blob/HEAD:/mknzusb for the script which makes the customization flash drive. Be sure to read and understand it before running as it will wipe your disk and you will be sad if it wipes the wrong one! Clone the whole repo if you like, but my server's bandwidth is not great and there is about 50MB in there, so be patient. I should probably refactor it to use a submodule to get tinycorexo. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] XO-system 1a builds
Hi, I'm not entirely sure if this is the right mailing list, if there is a more appropriate one, please let me know. I'm looking for the URL to download XO-system 1a for XO-4 (build 49). It seems that it is no longer available. http://download.laptop.org.au/XO/F18/13.2.0/XO-system-1a/ has what is likely to be build 50 and http://build.laptop.org.au/xo/os/build-51/ has build 51. I do have a copy of build 49 (which is a good thing, we have a small deployment with that build) but would like a stable URL to refer people to. Does anyone know where the change log for these builds is kept? I'd like to know if there are any important bug fixes we're missing out on. Thanks. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Bug triaging
On 29/06/13 09:47, Daniel Narvaez wrote: On 28 June 2013 23:39, Gonzalo Odiard gonz...@laptop.org mailto:gonz...@laptop.org wrote: If obscure, probably had sense to who fill it, and maintainer at the time. Should be better ask for more information and status in the same ticket. It surely made sense at the time, but now it's just adding to the triaging work that we don't have resources to do. It means I have to add a comment in the ticket to try to get a comment from the owner, block on it to triage and perhaps never get it because the person doesn't see my comment, or doesn't care anymore. Close the ticket with a comment If this is still required, please re-open. We have a closed won't fix state for this kind of thing at work so it's obvious that the issue is closed, but not fixed. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Dextrose] Patch written for Presence not updated, when client disconencts from telepathy-salut
On 11/07/12 02:58, Martin Langhoff wrote: A multicast I'm here would also do it, perhaps with less noise. Either way, we need to nag Salut devs on this. I ran tcpdump (hint, it doesn't work on an XO unless you turn off promiscuous mode) a while ago and investigated the network traffic, my results should be in the auckland testing reports from a few months ago (certainly it was this year). My recollection is that I found saw a broadcast or multicast packet from most or every node every minute or so and I'm fairly sure wireshark thought it was mdns related. My point is that I think there is already a heartbeat and you shouldn't need to send any more packets than are already sent to detect the exit of a laptop. I can't remember how this interacted with suspend-resume, if they were multicast, power saving shouldn't make a difference, if they were broadcast, power saving would cause significant disturbances, right? We also found problems with nodes stopping listening to the multicast socket and the cluster becoming incoherent, but that may not be related to the current discussion. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Dextrose] Patch written for Presence not updated, when client disconencts from telepathy-salut
(sending again reply all rather than reply-list) On 11/07/12 02:58, Martin Langhoff wrote: A multicast I'm here would also do it, perhaps with less noise. Either way, we need to nag Salut devs on this. I ran tcpdump (hint, it doesn't work on an XO unless you turn off promiscuous mode) a while ago and investigated the network traffic, my results should be in the auckland testing reports from a few months ago (certainly it was this year). My recollection is that I found saw a broadcast or multicast packet from most or every node every minute or so and I'm fairly sure wireshark thought it was mdns related. My point is that I think there is already a heartbeat and you shouldn't need to send any more packets than are already sent to detect the exit of a laptop. I can't remember how this interacted with suspend-resume, if they were multicast, power saving shouldn't make a difference, if they were broadcast, power saving would cause significant disturbances, right? We also found problems with nodes stopping listening to the multicast socket and the cluster becoming incoherent, but that may not be related to the current discussion. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] MP4 playback on XO-1.75?
On 04/04/12 09:38, Christoph Derndorfer wrote: thanks a lot for your reply and all the information. I tried compiling ffmpeg on 12.1.0 os6 but it seems gcc or my hardware is buggy because gcc segfaults during the compilation. I used the source rpm from rpmfusion. I'll be posting about this some more on olpc devel. I can also report that Firefox 10 on os6 has a webm codec but it doesn't seem to work on youtube. I haven't looked at why. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] MP4 playback on XO-1.75?
On 02/04/12 10:34, Christoph Derndorfer wrote: To make a long story short: Is there a way to watch MP4 videos on an XO-1.75 at this point in time? :-) The Marvel SOC has hardware accelerated decoding and encoding to the point it can play high definition video. See http://dev.laptop.org/ticket/11686 for enabling this hardware. The Raspberry PI and the cubox both have similar hardware. Look to those projects for hints about where to get the software codecs compiled for ARM. My feeling is the processor will struggle decoding even moderate resolution h.264 without the hardware acceleration. A friend is looking at getting the hardware acceleration stuff working on the XO, it is apparently complicated because the kernel for which Marvel released their drivers is quite different to that in 11.3.1. I'll catch up with him tomorrow and see what progress he has made on the 12.1.0 kernel. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Speak 33 voice chat problem on XO-1 11.3.0
On Tue, 2012-01-31 at 20:11 +1000, David Leeming wrote: I have been trying OLPC release 11.3.0 / build 883 (Sugar 0.94.1) on the XO-1. Has anyone noticed an issue in using voice chat, with the above equipment specification? Maybe it was just me but I was unable to get any audio of a shared chat text on the joined XO(s). Tried with XS server and with XO mesh. I am used to this activity on earlier versions of Speak and have never had any problems. We tested this today and found that on both the XO-1 and XO-1.75 Speak does not speak incoming messages. Outgoing messages were spoken. Is this what you are talking about? We also found two more bugs. When joining a shared session, Speak does not focus the shared chat screen but instead drops the user in the speak what I type screen. When entering Voice chat mode with the activity shared, you get a spoken warning that the activity is offline. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Weekly test request reminders? (was Re: Priorities for testing)
On Wed, 2010-10-13 at 16:10 +0200, Simon Schampijer wrote: I am doing XO builds containing the latest Sugar (0.90) for the XO [2]. So given from your information, that should be a good way for you to test 0.90. Indeed, we are testing these builds. Thanks for preparing them. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Weekly test request reminders? (was Re: Priorities for testing)
On Wed, 2010-09-29 at 14:30 +0200, Simon Schampijer wrote: that would be excellent indeed. We especially need help with 0.90 testing. What hardware and software setup are you using for testing? XOs? Soas? In Auckland we have quite a lot of XO-1s (mostly CL1 models) and a few XO-1.5s (mostly prototypes with the wireless powersaving hardware fault). We have virtualbox and regular laptop hardware, but I don't think we have anything on which wireless works with soas. We also have a schoolserver and good internet connectivity. Wellington has a similar number of XOs, but I'll let Tim describe their soas, virtualbox and other resources. See http://wiki.laptop.org/go/OLPC_New_Zealand Personally, I find XO, SoaS and VirtualBox images easiest to test, we download the night before and re-image our XOs or make new SoaS. For example there is a Sugar 0.90 release email on this list today and I have no idea what I'd do with the source. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Browse-115 stops when pop-up tab closes
On Wed, 2010-08-18 at 10:40 +0100, Lucian Branescu wrote: That should be enough to reproduce it, yes. A tame 9 year old found an easy steps to reproduce. Navigate to http://www.theteddyfactory.co.nz/shop/index.asp?Cat2=28 Click any Bear image. Click close window now in the resulting popup. Browse will disappear. Browse won't start again until your restart sugar. See http://bugs.sugarlabs.org/ticket/2155 for logs. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] setting date and time (was: re: journal sort options)
On Fri, 2010-08-20 at 09:30 +1000, James Cameron wrote: Our deployment was not connected to the internet so I didn't try to work out how the rdate server works and whether it was installed but not enabled. I suggest you test things while you have internet access before you go to where you do not. That is my recommendation too! We prepared where we could, but there were a number of things (setting the time being one) where we didn't know we would like to do them until we were actually there. This was made worse by the deployment running a build we weren't expecting. 3. yet another tool is the Linux date command, but the format of the input is archaic. I do not recommend it. Not only is it archaic, it is undocumented :( Not so, it is certainly documented, just that the format is strange. You can find the documentation in the manual page for the date command, and in the info page. And, at least on my ubuntu box, in date --help. I must say I have stared at that man page in the past and never interpreted the [MMDDhhmm[[CC]YY][.ss]] as instructions for setting the time, but now you point it out, it is fairly obvious. I'm an OpenFirmware release engineer. There are too many commands to document them fully within the scope of the firmware itself, since the documentation could easily exceed the available space for the firmware. I did figure that there would be space issues. However, there is a possibility of adding some additional text, but to do this properly I need to know from you exactly *what* commands you were looking for. The battery related commands were the ones that I was actually looking for -- I didn't know you could set the time in OFW. A list of the possible tests would have saved some time, I had to watch a few test runs cycle through to the touch pad and keyboard tests before I could investigate. That said, there is a workaround (run them all and wait) so documentation for other things would be preferable if you have to choose what to document. Also, when do you plan to upgrade the firmware version so that you have this documentation available? I'm not really asking for improvements for any deadline, just making a suggestion to help future ill-prepared travellers. An alternative would be a way to copy the olpc and sugarlabs wikis -- I tried to do this in Samoa (we made friends with the local ISP) but my time was limited and my spider too naive, so I had to kill it. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] setting date and time (was: re: journal sort options)
On Thu, 2010-08-19 at 11:23 +1000, James Cameron wrote: 1. one tool is rdate, which is on the OLPC builds, but that requires a server nearby that runs the time service on port 37. The command is rdate -s SERVER, where SERVER is the IP address or host name of the server. I tried rdate to the school server, but it wasn't listening. Our deployment was not connected to the internet so I didn't try to work out how the rdate server works and whether it was installed but not enabled. I was going to make it part of my backup or samoan customisation script, as I saw laptops with wildly varying times, but it didn't work and adding a connect to school server network to our workflow was undesirable anyway. 3. yet another tool is the Linux date command, but the format of the input is archaic. I do not recommend it. Not only is it archaic, it is undocumented :( On XO hardware, with security disabled, you can set the time using OpenFirmware: It would be nice if the help screen on the open firmware actually documented all the commands available, rather than just some of them. We didn't manage to work out how to mirror the olpc or sugarlabs wiki onto the school server and found a number of problems that could have been more easily or more better solved if we had access to these resources. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [olpc-nz] Samoa deployments
On Tue, 2010-08-17 at 11:42 -0400, David Farning wrote: Awesome please submit the bug reports to the sl bug tracker with the keyword 'dextrose' or to this ML. We are monitoring the list as it is the best source of feed back in the sugar/olpc ecosystem. We installed os300py on all the laptops and found quite a few bugs. I've raised some tickets: http://bugs.sugarlabs.org/ticket/2186 http://bugs.sugarlabs.org/ticket/2185 http://bugs.sugarlabs.org/ticket/2184 http://bugs.sugarlabs.org/ticket/2183 http://bugs.sugarlabs.org/ticket/2182 I've got some more to raise, but they will have to wait until tomorrow. I also noticed some things that I can't reproduce and probably won't raise tickets for. Every now and again, especially when the laptop was busy, opening a new activity would briefly show in a window frame like you see on an http basic authentication dialog. Usually this would disappear within a couple of seconds and the contents of the window would move up to a normal full screen view but very occasionally it would persist and you would have an activity in a window that you could move around. I'll raise a ticket for this, as it happened quite often (but nearly always the activity went full screen within a couple of seconds). Once, Browse froze due to a modal dialog in another window. I'm not really sure how I managed it, but while starting Browse, two Browse windows started and the background one had a modal dialog. This blocked both windows and gave the impression that browse had frozen. I eventually alt-tabbed (heading for the terminal to investigate there) and noticed the other window. Dismissing the dialog in the background window unlocked browse. Unfortunately I didn't take proper notes at the time as I only had a few minutes to use the internet and I really needed to do something rather than diagnose problems, sorry. I think the popup might have been an http-basic challenge, but extensive testing here couldn't reproduce the lock up with such a challenge. This problem might have been related to the window manager decorations visible problem above but I can't remember. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Browse-115 stops when pop-up tab closes
On Wed, August 18, 2010 2:04 pm, Christoph Derndorfer wrote: Tabitha, if you happen to have access to a configuration similar to mine could you maybe check whether the WiFi login pop-up that you had issues with in Browse-115 works in Browse-108? Sorry, we have left Samoa. The WiFi system was a chillispot http://en.wikipedia.org/wiki/ChilliSpot but it was using https, so I couldn't capture what was going on with tcpdump. I got charles working about 30 minutes too late to man-in-the-middle my session before we left. I saved a few pages using firefox, but the chillispot goes like this 1) Login page 2) enter login details submit 3) Login page becomes logging in page popup window appears displaying logging in 4) Login fails and popup window disappears In Browse, at step 4, everything disappears. This makes it difficult to capture the code that is doing the closing. I'm hoping to have time to try to reproduce using what I was able to record tonight. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Browse-115 stops when pop-up tab closes
On Wed, August 18, 2010 2:06 pm, Christoph Derndorfer wrote: Would a Firefox - Save complete page copy be good enough for this purpose? Even better would be a Charles http://www.charlesproxy.com/ or Fiddler http://www.fiddler2.com/fiddler2/ trace. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Trigger in Measure
As the owner of a real oscilloscope with a broken trigger circuit I thought I would implement a trigger in Measure. I was pleasantly surprised to find that there is a trigger, but the control doesn't work. The trigger itself works perfectly if you hack the code, but the combo box in sound_toolbar.py doesn't appear so the user can never turn it on. I can't see anything obvious in the trigger combo setup -- it all looks the same as the Logging Interval combo which appears and works, but the trigger combo box doesn't appear. If I delete all the logging interval combo setup code, then the trigger combo appears and works as expected. Am I missing something obvious? ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Installing Updated Translations
On Fri, 2010-07-23 at 08:22 -0400, Walter Bender wrote: On Fri, Jul 23, 2010 at 8:17 AM, Tom Parker t...@carrott.org wrote: Is there an easy way to install updated .po files from http://translate.sugarlabs.org onto a running sugar installation? cp physics.po ~/Activities/Physics.activity/po/ cp memorize.po ~/Activities/Memorize.activity/po/ ... If the translations get approved by the maintainers, then they will be automatically pushed into git. It is easy enough (at least in the case of measure) for me to make you a version with your .po file. This doesn't help a lot when you want to install what the translators have done so they can QA their work in a dozen activities. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Memorize Game sharing a Created game
On Thu, 2010-07-22 at 13:24 +1000, David Leeming wrote: I would like to understand the correct procedure to share and invite a Memorize game that has been created on an XO. Whenever we try this it is very difficult to make it work. Using XO-1.0 / 8.2.1 and Memorize-34 We tested the memorize that comes with 8.2.1 and had no trouble. We shared one of the pre-defined games. We made a word/word game and shared that and we made a picture/word game and shared that. We didn't see any problems. 2. Try to invite or share with others. On the XOs that have joined, the game area remains blank (black) and nothing seems to load further We erased the Memorize supplied with 8.2.1 and installed Memorize 34 and find the same issue you report. Unfortunately we didn't make a note of the version supplied with 8.2.1, so I can't tell you which one did work for us. There are some exceptions in the log (why aren't these presented to the user??) and I've raised http://bugs.sugarlabs.org/ticket/2115 ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Memorize Game sharing a Created game
On Fri, July 23, 2010 10:37 am, David Leeming wrote: I can definitely say that we have this issue! It is something that I have done with intermittent success before but in our current workshop we simply cannot make it work. Walter has updated the ticket http://bugs.sugarlabs.org/ticket/2115 saying that Memorize 34 does not work on build 8.2.1 because that build is too old. You'll have to install an older version of Memorize. The version of Memorize shipped with build 8.2.1 works, but I don't know what version that is. We did everything we could think of, restarting, etc etc. Unfortunately, Memorize encountered an unexpected exception but didn't tell you. Can you please give me the step by step method you used to (a) create and share a game and (b) to load the attached game and then share it, using a server or simple mesh (if it makes any difference) then we will attempt to reproduce. I don't have an XO with me so I can't install 8.2.1 and see which version it ships with, but from memory we: Flashed two XO-1.0 with build 8.2.1. Started Memorize on one XO Loaded a game Set sharing to Neighbourhood Found the Memorize in the Neighbourhood on the other XO Joined Memorize with right-click We then installed Memorize 34 and sharing no longer worked. Also, can you let me know if the saved game should be loadable from the Journal or has to be loaded from a started game. Sorry, I don't know. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Memorize Game sharing a Created game
On Fri, July 23, 2010 1:42 pm, David Leeming wrote: Thanks, it is version 33 that was shipped, if you read the wiki carefully. Are you sure? Memorize 33 was released July 14, 2009 according to http://activities.sugarlabs.org/en-US/sugar/addons/versions/4063 Build 8.2.1 was released May 13, 2009 according to http://download.laptop.org/xo-1/custom/g1g1/gg-802-1/ and http://wiki.laptop.org/go/Release_notes/8.2.1 Also, the ticket has been updated by garycmartin saying 33 doesn't work on sugar 0.82 http://bugs.sugarlabs.org/ticket/2115 ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel