touch-packages team mailing list archive

[Launchpad Bug Tracker <1445134@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package network-manager - 0.9.10.0-4ubuntu19

---------------
network-manager (0.9.10.0-4ubuntu19) wily; urgency=medium

  [ Tony Espy ]
  * debian/patches/add_ofono_settings_support.patch: remove code
    that added APN, USERNAME and PASSWORD to NM_SETTING_GSM object.
    NM doesn't actually need access to these settings, and USERNAME/
    PASSWORD can cause issues with NM's secrets needed logic.
  * debian/patches/0001-wwan-add-support-for-using-oFono-as-a-modem-manager.patch,
    debian/patches/lp1461593-add-nm-settings-connection-reset-retries-methods.patch,
    debian/patches/add_ofono_settings_support.patch,
    debian/patches/lp1461593-add-modem-reconnect-delay-to-policy.patch: More changes
    to NMModemOfono's modem_state handling.  Added get/set_reset_retries_timeout
    methods to NMSettingsConnection, and use the set method to lower the timeout for
    ofono connections to 30s.  Finally added a 5s delay to NM_POLICY's activation
    logic triggered when a modem device is disconnected.  This allows modem time to
    settle and NM to process the resulting DBus state changes. (LP: #1461593)
  * debian/patches/0001-wwan-add-support-for-using-oFono-as-a-modem-manager.patch,
    debian/patches/lp1445080-modify-device-modem-avail.patch,
    debian/patches/lp1445080-nm-modem-check-for-set-mm-enabled-func.patch,
    debian/patches/lp1461593-add-modem-reconnect-delay-to-policy.patch: These
    changes collectively fix flight-mode on arale ( and other devices ), due to
    some fundemental race conditions in the ofono logic. (LP: #1445080, #1440917)
  * debian/patches/0001-wwan-add-support-for-using-oFono-as-a-modem-manager.patch,
    debian/patches/add_ofono_settings_support.patch: Add support for the ofono
    gprs-context 'Preferred' property. (LP: #1361864)

  [ Mathieu Trudel-Lapierre ]
  * d/p/0002-wifi-cull-the-scan-list-before-signalling-ScanDone-b.patch:
    Re-add schedule_scan() call after we get the ScanDone signal from the
    supplicant. Otherwise we'd do one scan on startup and never scan again.
    (LP: #1445134)

 -- Mathieu Trudel-Lapierre <mathieu-tl@xxxxxxxxxx>  Wed, 05 Aug 2015
12:17:28 -0400

** Changed in: network-manager (Ubuntu)
       Status: In Progress => Fix Released

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

Title:
  Network manager never scanning for new access points

Status in Canonical System Image:
  Confirmed
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Vivid:
  Confirmed
Status in network-manager package in Ubuntu RTM:
  In Progress

Bug description:
  While trying to reproduce another bug related with the last seen value
  from the access points, I noticed that network manager is never really
  scanning for new access points on my desktop, not even when not
  connected.

  $ sudo nmcli g logging level debug domains wifi_scan

  Then powered an access point, but was never really able to see it.
  From syslog, noticed that there is never really a scan, which explains
  why the ap never goes away and why it is not able to find it in the
  first place.

  If I force a scan via cmdline it works as expected (and I noticed a
  scan also happens when changing connections).

  Was also able to reproduce this issue on mako, with the following image:
  phablet@ubuntu-phablet:~$ system-image-cli -i
  current build number: 173
  device name: mako
  channel: ubuntu-touch/devel-proposed
  alias: ubuntu-touch/vivid-proposed
  last update: 2015-04-16 14:58:58
  version version: 173
  version ubuntu: 20150416
  version device: 20150210
  version custom: 20150416

  In the mako case, I booted with a known connection in place, it
  connected successfully but it never really scans for other access
  points. Scan works fine after disconnecting though.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu14
  ProcVersionSignature: Ubuntu 3.19.0-14.14-generic 3.19.3
  Uname: Linux 3.19.0-14-generic x86_64
  ApportVersion: 2.17.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Apr 16 14:21:42 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-10-29 (534 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
  IpRoute:
   default via 192.168.1.1 dev wlan0  proto static  metric 1024
   10.0.3.0/24 dev lxcbr0  proto kernel  scope link  src 10.0.3.1
   169.254.0.0/16 dev lxcbr0  scope link  metric 1000
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.16
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to vivid on 2013-10-31 (532 days ago)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2013-11-04T02:19:36.923463
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'.

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