[Testing] Notes from an impromptu 8.2.1 Release Mtg.

[Daniel Drake]

Hi Hal,

I'm having trouble comprehending your mail

2009/1/30 Hal Murray <hmurray at megapathdsl.net>:
> [Context is WAP connection not getting set via NetworkManager]
>
> I expected this to get fixed in build 24.  I grabbed build 25 since that
> announcement came by before I started pulling things over.
>
> I expected it to fix the startup problem (#9222), but it doesn't seem to be
> working for me.

#9222 is unrelated to startup problems. It represents a total
inability to connect to WEP networks at any point in time. Are you
using a WEP network?

> I've rebooted a half-dozen times.  It has never connected automatically.  It
> works if I poke the icon.  I don't think I could tell the difference between
> this one and 1352.

What is 1352? joyride-1352? Ticket 1352?

Have you ever connected to the network successfully (using
staging-25)? If not, it will not attempt to connect on further boots.
If yes, did you wait sufficiently long enough (perhaps as long as 5
minutes) for the XO to check mesh channels for school servers before
consulting the history of infrastructure networks?

If you did, then here are some diagnostics you can do:
Firstly, you can check if the AP is marked as a favourite when it
appears on the network view. It should have a star against the
circular icon.
Secondly, you can check that it is correctly represented in
/home/olpc/.sugar/default/nm/networks.cfg
Thirdly, you can share /var/log/messages. It is possible that during
boot, you hit the bug (#8104) where a successful connection to your AP
is established, but an internal failure in communications means that
NM mistakenly believes the connection failed. This results in the XO
trying other network connections (e.g. going back to meshing).

I just attempted to reproduce on 2 laptops through this procedure:
1. Install staging-25
2. Boot, enter name and choose colour
3. Connect to our office infrastructure network
4. Reboot
5. A couple of minutes after booting, confirm that it has reconnected
to the same infrastructure network.

No problems found.

Thanks,
Daniel