[Bugs] #1883 UNSP: doesn't automatically connect to network at startup anymore (on XO-1)
Sugar Labs Bugs
bugtracker-noreply at sugarlabs.org
Wed Mar 31 15:01:34 EDT 2010
#1883: doesn't automatically connect to network at startup anymore (on XO-1)
------------------------------------------+---------------------------------
Reporter: sascha_silbe | Owner: tomeu
Type: defect | Status: new
Priority: Unspecified by Maintainer | Milestone: 0.88.x
Component: sugar | Version: Git as of bugdate
Severity: Minor | Keywords:
Distribution: Unspecified | Status_field: New
------------------------------------------+---------------------------------
Recently Sugar stopped connecting to the network automatically at startup.
Log messages suggest that NetworkManager tries to connect automatically
(once Sugar is started up and can provide the necessary secrets), but Mesh
support kicks in and cancels the connection attempt:
{{{
Mar 31 18:21:06 xo-sascha NetworkManager: <info> Activation (eth0)
starting connection 'Auto xonet'
Mar 31 18:21:06 xo-sascha NetworkManager: <info> (eth0): device state
change: 3 -> 4 (reason 0)
Mar 31 18:21:06 xo-sascha NetworkManager: <info> Activation (eth0) Stage
1 of 5 (Device Prepare) scheduled...
[...]
Mar 31 18:21:06 xo-sascha NetworkManager: <info> Activation (eth0) Stage
2 of 5 (Device Configure) complete.
Mar 31 18:21:06 xo-sascha NetworkManager: <info> Config: set interface
ap_scan to 1
Mar 31 18:21:06 xo-sascha NetworkManager: <info> (eth0): supplicant
connection state: inactive -> scanning
Mar 31 18:21:06 xo-sascha NetworkManager: <info> Activation (msh0)
starting connection 'olpc-mesh-1'
Mar 31 18:21:06 xo-sascha NetworkManager: <info> (msh0): device state
change: 3 -> 4 (reason 0)
Mar 31 18:21:06 xo-sascha NetworkManager: <info> Activation (msh0) Stage
1 of 5 (Device Prepare) scheduled...
Mar 31 18:21:06 xo-sascha NetworkManager: <info> Activation (msh0) Stage
1 of 5 (Device Prepare) started...
Mar 31 18:21:06 xo-sascha NetworkManager: <WARN>
real_act_stage1_prepare(): disconnecting companion device
Mar 31 18:21:06 xo-sascha NetworkManager: <info> (eth0): device state
change: 5 -> 3 (reason 2)
Mar 31 18:21:06 xo-sascha NetworkManager: <info> (eth0): deactivating
device (reason: 2).
Mar 31 18:21:06 xo-sascha NetworkManager: <WARN>
real_act_stage1_prepare(): companion disconnected
Mar 31 18:21:06 xo-sascha NetworkManager: <info> Activation (msh0) Stage
1 of 5 (Device Prepare) complete.
}}}
Do we trigger mesh support explicitly during Sugar startup or is this a
NetworkManager bug?
--
Ticket URL: <https://bugs.sugarlabs.org/ticket/1883>
Sugar Labs <http://sugarlabs.org/>
Sugar Labs bug tracking system
More information about the Bugs
mailing list