Test group release notes/2009 and earlier

From OLPC
Jump to navigation Jump to search

Build 488

Change log:

Base OS:

  • NetworkManager 1:0.6.5-0.8.svn2627.olpc2
    • fix assert when selecting mesh network
  • dbus-python 0.82.0-2.olpc2
    • fix cpu hogging issues
  • telepathy-salute 0.1.3.1-0.1.20070705darcs.olpc2
    • enable the extra OLPC bits for tubes
  • avahi-autoipd 0.6.20-3.fc7
    • have a Require(pre) on shadow-utils so /usr/bin/adduser doesn't fail during install
    • this should fix connection to the mesh when there are no school servers or mesh portals
  • /etc/asound.conf
    • fix the capture source to be the mic
  • pull in gnome-python2-gnomevfs
  • make ext3 build slightly smaller than 1G so it fits on 1G flash drives

Activities:

  • TamTam
  • Journal integration
  • New sounds
  • Beats per page in edit
  • Keyboard recording in edit
  • Network not yet working


  • From home with a B2, and no connection to a mesh; I had to add a wep key a few times to get it to connect to AP. Then I tried to open etoys and it will never open.
  • J5 said he was able to open eToys with this code on a B3 with no problem. Not sure what his network connection was.
  • Mesh connectivity issue: From work, my B2 successfully connected to the mesh and I browsed the internet, but the mesh icon continues to blink the full inside circle (which used to mean it hasn't finished connecting); and in the home view, the mesh is still grey.
  • eToys doesn't start for me at work either. It continues to fade in and out as if it is trying to start, but never gets past that. The Journal never records that eToys was running.

- Kim

Build 486

Change log:

  • Base OS:
    • ext3 qemu builds
      • now boot again
      • have a scalled grub option for running on smaller screens

- John


- Zack

Build 485

Change log:

  • Base OS:
    • NetworkManager - 1:0.6.5-0.8.svn2626.olpc2
    • Make anycast addresses configurable though /etc/NetworkManager/anycast.conf
    • Fix manual reactivation of the mesh device to start at step 1
    • Make sure dhclient is stopped before switching mesh channels
  • sugar-datastore - 0.2.2-0.5.20070703gita248b5cb79.olpc2
    • Support for binary properties
    • Indexer fixes
    • External devices fixes
  • sugar - 0.65-0.4.20070703gitcc2b8884c0.olpc2
    • Use the new palette widget everywhere in the UI
    • Do not always show the shutdown palette on startup
    • Implement primary and secondary state for palettes
    • Fix several frame/zoom level bugs
  • Actvities:
    • Call - taken out of builds for now
    • Chat -New version added fixes
    • Etoys - back in build


- John

Build 482

NOTE: This build will allow laptops to only communicate with other laptops with 482 or higher. Also, the school server needs to have upgraded to the latest marvell firmware and anycast needs to be turned on.


Change Log: <http://olpc.download.redhat.com/olpc/streams/development/build482/devel_jffs2/ChangeLog>

This build doesn't include avahi-autoip, so it will not get on the mesh. There should be another build today (7/3) or tomorrow (7/4) that can get on the mesh. It can connect to an infrastructure access point. (Unless it is WPA AP, which are increasingly common... -Zack)


- Zack


- kim

Build 478, RC1 notes

Change log since 472:
Base OS:

  • Add avahi-autoipd
  • Fix up keysymbols for keyboard
  • NetworkManager
    • Autoip work
  • Sugar
    • Better palette positioning
    • Reject invalid nick names in the intro screen
    • Make startup notification work from the journal and clipboard
    • Do not create a new object when resuming from the journal

Activities:

  • Web
    • Arabic translation
  • Journal
    • Button to copy objects to the clipboard.
    • Spanish and Arabic translations.
    • Palette positioning fix.
  • I was able to connect to my home AP with WEP key. One XO worked the first time and one of them took about 3 tries of entering the WEP key (and I'm pretty confident I used the right key).
  • On another XO, when it wouldn't connect to my AP, I logged in as root, typed 'ifconfig' and saw that there was no eth0 interface. I typed 'ifup eth0' twice (the first time it failed). And then it connected to my AP. (I'll write this up as a bug)
  • After the first XO connected to the infrastructure AP, I tried to connect the second XO via the Mesh. That was never able to connect, but I did see that an 'olpc-mesh' ad-hock network shows up on iStumbler.
  • I was able to open a number of activities (pretty much one at a time) and do some basic testing. Everything responded very slowly and gets incredibly slow after only a few minutes of trying to test. When it got to the point of no response in about 60 seconds (for something that usually takes only a few seconds), then I would reboot.
  • I'm not sure how to close some activities.
  • At this point I think we can start adding bugs to trac.

- Kim

  • The B2 essentially can't run build 478 for whatever reason. Takes extremely long to do the most basic things, and hangs a lot. It also runs noticeably slower than other builds on the B3 in terms of load times and lag (especially noticeable when tabbing between programs). One of the most noticeable things is the cursor frequently lagging and then "catching up."
  • Switching between the console and Sugar causes a lot more lag than in other builds. On the B2, it was enough lag to hang the system permanently.
  • On one bootup, the mouseclick and keyboard stopped working, though the mouse still scrolled. Anything that should have triggered a dropdown menu or tooltip did not. Rebooting solved the problem.
  • If you switch from Neighborhood view to Home view while moused over a wireless access point or mesh portal icon, the icon's tooltip will persist through the switch and stay on the screen, even after you open activities. They will go away if clicked.
  • Graphics and icons frequently get "stuck" in the upper right hand corner. Often, if there is a tab or some other icon in the upper right corner, the tab will persist, either in its original form, or as a grey box of the same size, when you switch views.
  • There are a number of graphical glitches that occur only on B2s. For many icons and images, half will appear properly, but the other half is corrupted.
  • Journal no longer opens automatically. The icon appears on the donut, but the window doesn't open until the donut icon is clicked. I think this is intentional? It's a good change, as it was a pain to have to wait for the Journal to load before doing anything else.
  • When tabbing back into Journal, large portions of the window are obscured/grey.
  • That Chat icon in Journal does not match the Chat icon on the taskbar.
  • Switching between photos and videos in Camera is very unintuitive right now. Looks like part of the GUI is broken. The only way to switch between them is to use the two arrow buttons under the Camera tab and keep pressing the eye until it turns red, even though the first arrow button never becomes deselected. The word "Activity" in the Activity tab changes colors as you do this for some reason. Eventually, if you've tabbed around for long enough, the GUI will correct itself and behave normally.
  • Lots of activities can only be quit with alt-C.
  • Overall, the most notable problems (aside from some major holdovers from previous builds like the Paint donut bug) are performance issues and graphical glitches. Tabbing between different views and programs both lags the system and messes up icons and tabs.

- John

- Zack


Build 472 notes

  • XO is not getting on the mesh.

==> (J5) For now if you want you can log into root at a terminal and type: 

 chmod +x /etc/NetworkManager/callouts/*
  • Some activities loaded and started up... the camera keeps hanging for me; I did get a picture out of it before the activity got hung up.
  • The activities that did start up showed up in the journal, and provided a more detailed view. Resume worked for me on the newsreader activity which had started up properly.

- Kim

  • Like Kim said, the mesh is very broken. It couldn't successfully connect to begin with, so I had no internect connection. Also, if you go to Neighborhood and right-clicked on the Mesh icon, it (as well as all the wireless access points) disappeared from the view.
  • Additionally, right-clicking on a wireless access point icon got me stuck in Neighborhood view - couldn't open frames or switch views.
  • The biggest improvement seems to be that Journal appears to be working a lot better. Resume and preview work now, and search appears to at least open up a search window, though it doesn't find much (unless I type nothing in the text field).
  • Shared activities now appear on the mesh.
  • I can't quit out of journal anymore, which is good.
  • If the user is supposed to be able to click with the trackpad, the sensitivity is still off. On at least one occasion I moused over the "shutdown" option in the middle of the screen and phantom-clicked it. Actually, that does highlight a potential flaw with the click-shutdown icon being in the middle of the screen - even without the trackpad problem, the chance of accidentally clicking it when, say, trying to click an icon on the donut, would be considerable.
  • Didn't have any problems with Camera - all activities loaded fine for me except Paint and Call - but the real-time display is still not functional.
  • Chat and Call have the same activity icon.
  • Paint, rotate screen, and frame toggle are still broken in all the same ways as 466.
  • When left idle for ~20 minutes, the screen's display bugged out. Looked like it was trying to go into suspend, but messed up.

- John

Build 466 notes

  • Search feature in Journal is broken, and you cannot Resume from Journal.
  • Journal is not on the taskbar, but unlike 465 it opens properly upon boot now. However, since I can still quit out of it with alt-C, there should either be a) a way to open it from the taskbar or b) no way to quit out of it.

==> Quit out of it with ctl c.

  • Opening Paint completely breaks the activity donut (this was a problem in 465 too). Once Paint is opened, icons no longer appear on the donut, and clicking the spaces on the donut will not switch you to that activity. All the icons for activities you open appear clipped on the left side of the screen. Also, Paint itself doesn't open properly either.
  • Frequently, activities will open when I mouse over them on the taskbar but don't click them. This was an issue in 465 and it seems even more prevalent now.
  • Mouse speed is still much higher than before (is this intentional?)
  • Frame Toggle key does not work.
  • Rotate screen key does not do anything.
  • Cannot power down by pressing the power button - you must either use the option from the XO icon at the center of the donut, or hold down the power button.
  • Read now has an icon for opening files (as opposed to 465), but it doesn't work.
  • Camera still has no real-time display and the video function is still broken.

- John

  • When you press the power button, nothing happens (if you hold it down for >5 seconds it shuts down immediately). This is going to be suspend soon...so think of it as a feature.
  • To shut down, now you can use the icon on the home page. When you hover over your XO icon you will get see a shutdown flyover. This worked for me.
  • I opened Abiword, wrote some text, then went to the journal. It showed a new entry, after another click or two I saw a third Abiword entry. None of them let me resume.
  • I tried opening other activities (camera, calc, paint) and they would show up in the donut while it was trying to open, then just disappear.
  • After closing the journal with CTL C, I was able to open another activity (paint).
  • After some inactivity, the screen went into a suspend mode and resumed when I hit a key! (I believe that is the proper behavior)

- Kim

Retrieved from "http://wiki.laptop.org/mediawiki/index.php?title=Test_group_release_notes/2009_and_earlier&oldid=48028"