[Bugs] #2218 UNSP: os851 xo1 - with #1610 fix applied, XO never joins existing mesh network
Sugar Labs Bugs
bugtracker-noreply at sugarlabs.org
Sat Aug 21 19:21:08 EDT 2010
#2218: os851 xo1 - with #1610 fix applied, XO never joins existing mesh network
------------------------------------------------------------------+---------
Reporter: mikus | Owner:
Type: defect | Status: new
Priority: Unspecified by Maintainer | Milestone: Unspecified by Release Team
Component: untriaged | Version: 0.84.x
Severity: Unspecified | Keywords:
Distribution: Other (name your distribution in the description) | Status_field: Unconfirmed
------------------------------------------------------------------+---------
BACKGROUND: Had exisitng mesh connection (using channel 1) between
several XO-1s (none with #1610 fix). Brought up another XO-1 (os850, with
#1610 fix). That XO automatically put parentheses around (i.e., auto-
connected) the ad-hoc icon for channel 1 in its Neighborhood. I did not
want that, so I clicked on 'Disconnect' in that icon's palette. I then
clicked on the "Mesh" icon for channel 1 in that XO's Neighborhood.
Except for that "Mesh" icon pulsing, nothing further happened. My
patience ran out, so I changed the gconf /desktop/sugar/network/adhoc
value to 'false' - that made the ad-hoc icons disappear from that system's
Neighborhood, but its "Mesh" icon for channel 1 kept on pulsing -- without
connecting.
PROBLEM: I rebooted the os851 (with #1610 fix) XO-1 (which now had the
gconf adhoc value set false), and clicked on the "Mesh" icon for channel 1
in that system's Neighborhood. Although that icon kept on pulsing,
despite me waiting for many many minutes that system did not connect to
the existing mesh network. Took system dump.
--
Ticket URL: <http://bugs.sugarlabs.org/ticket/2218>
Sugar Labs <http://sugarlabs.org/>
Sugar Labs bug tracking system
More information about the Bugs
mailing list