desktop-packages team mailing list archive

[Tony Espy <1425172@xxxxxxxxxxxxxxxxxx>]

I suspect there my be deeper issues with scanning.  Bug #1445134 reports
that NM 0.9.10.0 is not periodically scanning.

I'm seeing the same thing on krillin and mako running the latest stable
( OTA5 ) images:

If I start wpa_cli ( as root ) on a system running utopic ( NM 0.9.8.x
), I see periodic scan events reported:

<3>CTRL-EVENT-SCAN-STARTED 
<3>CTRL-EVENT-SCAN-RESULTS 

I also can see the updated scan results using the wpa_cli 'scan_results'
command.

If I perform the same test on krillin or mako ( NM 0.9.10.0 ), I don't
see any periodic scan happening.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1425172

Title:
  Network indicator lists the non-exist AP (timeout for the AP to be
  removed is too big, ~6min)

Status in Canonical System Image:
  Confirmed
Status in indicator-network package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu RTM:
  Invalid

Bug description:
  Summary: Network indicator lists the non-exist AP
  Steps to reproduce:
  1. Boot to system
  2. Scroll down the Network indicator
  3. It lists about 10 AP (In Taipei office)
  4. Go to another place and check network indicator again

  Expected Result:
  It should not list non-exist AP and only show available AP

  Actual Result:
  It shows about 12 AP on the screen but only two are real AP for connecting, and others 10 are from last list.

  This is reproducible on mako/krillin on both RTM and vivid.

  The main issue is that the timeout for the AP to be removed from the
  known AP list is too big when comparing with other phones.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1425172/+subscriptions