Opened 6 years ago

Closed 6 years ago

Last modified 21 months ago

#10672 closed defect (fixed)

Can not connect to adhoc network in a specific situation

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


  • the Sugar Ad-hoc icons are displayed
  • they indicate as well if a network has members
  • but you can not connect to a network

The error message is: logging.error('Failed to create Ad-hoc network: %s', err): Device not Found

(I just found that one on a second machine that came out of suspend)

Change History (6)

comment:1 Changed 6 years ago by erikos

  • Action Needed changed from diagnose to add to build

Pushed to sugar as 06e3c9898c90fe180df602ceca984d2f5b8b6bdb, will be in 0.92.1

comment:2 Changed 6 years ago by dsd

  • Action Needed changed from add to build to package

comment:3 Changed 6 years ago by dsd

  • Action Needed changed from package to test in build

test in 11.2.0-17

comment:4 Changed 6 years ago by erikos

  • Priority changed from normal to high

comment:5 Changed 6 years ago by greenfeld

  • Action Needed changed from test in build to no action
  • Resolution set to fixed
  • Status changed from new to closed

I've tried various sorts of suspends (forced, timeouts, etc.) which turn off the network card with known APs assigned in Sugar as well as no known APs, and we do not seem to have trouble reconnecting to the Ad-hoc network from suspend as necessary in 11.2.0-22.

comment:6 Changed 21 months ago by Quozl

  • Milestone 11.2.0-M4 deleted

Milestone 11.2.0-M4 deleted

Note: See TracTickets for help on using tickets.