Ticket #2589 (closed defect: fixed)

Opened 7 years ago

Last modified 7 years ago

Neighborhood view isn't updating APs often enough

Reported by: Zack Owned by: AlexL
Priority: high Milestone: Not Triaged
Component: network manager Version:
Keywords: Cc: hugsie, cjb, Zack
Action Needed: Verified: yes
Deployments affected: Blocked By:
Blocking:

Description

I was testing #2019 at home, and then left to come to 1CC, far out of range of my AP at home. But my AP was still listed, and even iwconfig still thought it was connected to it.

Let me know if you need more information.

Change History

Changed 7 years ago by jg

  • cc hugsie, cjb added
  • milestone changed from Untriaged to Trial-3

We should probably have OHM have NM reassociate after a lid close event.

Changed 7 years ago by Zack

  • cc Zack added

Well, when I got to 1CC my XO wasn't suspended and the battery had gone down significantly.

Changed 7 years ago by kimquirk

  • owner changed from dcbw to AlexL

Alex, Can you please retest this on laptops to see if it is still a problem?

Changed 7 years ago by AlexL

  • status changed from new to closed
  • verified set
  • resolution set to fixed

Build 616 Q2C28

Booted the laptop in Cosi and saw all the wireless networks there. Then walked across the street and went back up to the OLPC office. It took about 30 seconds for the laptop to see all the wireless networks in the OLPC office, and connect to the school server.

Note: See TracTickets for help on using tickets.