Opened 6 years ago

Last modified 14 months ago

#10725 new defect

Sugar Ad-hoc network: reconnect after suspend

Reported by: erikos Owned by: erikos
Priority: normal Milestone:
Component: sugar Version: Development build as of this date
Keywords: Cc:
Blocked By: Blocking:
Deployments affected: Action Needed: diagnose
Verified: no


I slightly other approach than we had in 10.1.3, but the result will be similar for the user.

Pushed fix as: 582f9df1acbff8c71d897f37a4a4e98d4830fd3f

Setting the 'autoconnect' property for the connection will let NM do the reconnection when the device is up. If the Sugar Ad-hoc network is around it will automatically connect to it. The connection is not stored after logging out of Sugar.

The autoconnect functionality inside Sugar is still needed for the cases when we log into Sugar, after a timeout we will connect to an exisiting Ad-hoc network or will default to the Sugar Ad-hoc network on channel 1. I increased the timeout to 60 seconds because during testing I found to get more reliable results like that.

Will be in Sugar 0.92.1

Change History (6)

comment:1 Changed 6 years ago by dsd

  • Action Needed changed from add to build to package

comment:2 Changed 5 years ago by dsd

  • Action Needed changed from package to test in build

test in 11.2.0-17

comment:3 Changed 5 years ago by dsd

  • Action Needed changed from test in build to testcase

Test case, please.

comment:4 Changed 5 years ago by erikos

Hmmm, the autoconnet does not seem to happen, right away. I thought it was like that back when I wrote it. Have to check.

comment:5 Changed 5 years ago by dsd

  • Action Needed changed from testcase to diagnose

comment:6 Changed 14 months ago by Quozl

  • Milestone 11.3.0 deleted

Milestone 11.3.0 deleted

Note: See TracTickets for help on using tickets.