Test group release notes/2009 and earlier

NOTE: Entering issues on this page does not count as reporting them.

Purpose of Test Group Release Notes
If you are thinking of loading a new image; come to this page first and see if the build you are going to load has any major problems. If it can't even pass the Smoke Test, you probably don't want to use it.

If you don't see anything here on the latest release, please add your notes on smoke test and/or basic functionality to help the next guy.
- Kim

Use Trac to file bugs.

Regression/Smoke Test

This set of test cases represents a quick smoke test that the build should pass:

1. boot into sugar
2. connect to a local mesh and see other XOs (this needs to be in a location with no school server or infrastructure AP)
3. run a collaborative activity (AbiWord, Connect4, or Chat) with another XO
4. run Browse and ensure that library navigation sidebar and index page loads
5. ensure that the journal is able to resume an activity
6. connect to an AP (and/or school mesh) and browse the web
7. connect one XO to an AP; then boot a second XO, which should connect to a local mesh and browse the web through the second XO.

Please add build release notes below and provide info as to whether the build passed the smoke test.

Build 556

ChangeLog 556

Smoke results:

1. Boots into sugar; can see other XOs on school server mesh, can get to internet but the mesh and battery icon aren't correct. The battery icon is white, and the mesh icon remains grey even with a good network connection.
2. I opened and shared an AbiWord doc. Sharing worked pretty well, a little bit of trouble adding images into docs. Two new bugs were filed: Can't use CTL-C, CTL-V to copy and paste an image, and some .jpg images dragged successfully onto the clipboard and some do not.
3. I tried to share a url through browser sharing and the other XOs that see a Browse icon get a new browser window, not the one that I was trying to share. It IS possible to share a url by opening a chat window and using cut&paste to put the link in the chat window.
4. The browse activity did NOT provide the sidebar links to the library; only a google search window.

Build 553

On a B2-1

• Camera activity displays a blank gray screen
• Very slow start on activity like Browser, TamTam

- Luya Tshimbalanga

On a B4: Activities: The following activities do not start (doesn't seem to be low memory, but the problem is undiagnosed):

• Tamtam
• Paint
• Connect
• Calculate

The following activities start but do not function:

• Record (camera)
• Browser (IP connectivity, yet all pages time out)

Other points:

• Presence service seems to work
• Frame can sometimes disappear and be hard to get back
• Journal seems to have a fairly large memory leak

Hello1024 06:08, 23 August 2007 (EDT)

Build 551

On a B2-1

• Camera stops
• Activities are very slow
• 2nd console ctrl+alt+f2 - no console (only error messages)

-Rowen/wenmi

• Still no WPA2

- Zack

Build 547

On a B2-1

• Camera stops
• Browse starts (starting..) but never opened
• 2nd console (Ctrl+alt+f2) - Xwindow error

-wenmi / Rowen

• Can't open Paint activity.

Build 545

On a B2-1

• GX fix worked on camera
• OS Image loaded successfuly
• Very slow due to little memory, we need to enhance memory usage.
• Tamtam Mini has no sound
• Able to resume activity on Journal.

-wenmi

Build 542, Trial-2 Release

• Trial-2 SW Release Notes

• ChangeLog 542

Smoke Test (Some issues with connecting to an AP):

1. Sugar boots up
2. Connected properly to mesh, saw others via link local
3. Shared Abiword, chat, camera successfully
4. Journal was able to resume from an abiword doc successfully
5. I'm currently having trouble connecting to an external AP from within 1CC. This worked at home.
6. Need to test item 6 in a different environment.

Other Notes:

• I had to remove the battery and power adapter for a few seconds after upgrading in order to boot up properly.
• To boot with backup edit the olpc.fth file to change 'false' to 'true' in line 11. This will save the activation key as well as user data (including the nickname and color of the XO). If you have never upgraded to code base with activation keys, you will need a different process. (I will try this soon)
• It is not very difficult to 'hang' the mesh and require a reboot to start again. Not sure of exact steps to repeat -- Walter saw it; I've seen it.

Some Notes for the formal Software Release Notes:

• If you are running Tamtam or another activity that uses the speakers, close the activity before suspending the laptop. You can suspend the laptop by closing the lid or pushing the suspend/resume button. If Tamtam or another sound activity is still running, when the laptop resumes from suspend, it will squeal very loudly. To recover, shut down the laptop by holding the suspend button for >5 seconds or remove the battery and adapter for a few seconds.

• Now that we have made the power button suspend; to shutdown completely, hover over the XO in the home view and click on 'Shutdown'.
• To turn on various activity logs:

1. edit ~/.xinitrc and uncomment the line that imports .sugar.debug
2. in ~/.sugar.debug, add lines like export JOURNAL_DEBUG=yes

• Backup to School Server: To register with a school server and backup data (for build 542):

1. Open a developer's console
2. View the config file to see that you are not registered with any school server; and to get your Serial Number (SN)
3. SSH into the school server (for 1CC this is schoolserver.laptop.org); type 'yes' to accept keys
4. Type 'olpc-register' to register with the server
5. Reboot for this config file to take affect.
6. From the Journal, click on the 'Backup' tab, and then the 'Backup' icon.

Old Release Notes

Old Release Notes