doesn't automatically connect to network at startup anymore (on XO-1)

[sascha_silbe]

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?

[erikos]

if we have connections we start the timer and see if there is some activity, otherwise we automesh directly

[erikos]

If we have connections in the settings (have been connected to an AP before) we set a timeout to check if there is connectivity on those connection after a while. If there is no activity we try to setup a mesh network then. If there are no connections we setup a mesh network directly.

[quozl]

Tested on os240py, this does indeed fix the problem.

[sascha_silbe]

Wow, didn't expect the fix to be that easy. Works fine, thanks!

[erikos]

James, Sascha, thanks for testing! I guess I can merge, Sascha - happy with the code, too? ;p

[erikos]

Approved on irc by Tomeu. Pushed to the 0.88 branch.

 http://git.sugarlabs.org/projects/sugar/repos/mainline/commits/e9bc53279851db9811e59d9b4ba8e4d088fcd1e7

[sascha_silbe]

Thanks!