[Touch-packages] [Bug 1330471] Re: nm connects to far away access points since #83 mako flo

2014-12-27 Thread Alberto Salvia Novella
** Changed in: network-manager (Ubuntu)
   Importance: Undecided = High

-- 
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/1330471

Title:
  nm connects to far away access points since #83 mako  flo

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  For a few images now, on mako and flo my devices seem to cling onto
  access points which are far away rather than nearby ones.

  At home I have two access points named such that I know which is which
  (popey_2.4_bed  popey_2.4_den).

  When I boot up an Ubuntu device (phone/tablet) they always seem to
  attach to the far away access point and stay on it until I forcibly
  choose the other access point.

  I notice this a lot because I find using the phone slow because it's
  using the 'bed' AP which is at the other end of the house and through
  a few walls, whereas the 'den' one is right next to me in the office.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: network-manager 0.9.8.8-0ubuntu18
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.3-0ubuntu1
  Architecture: armhf
  CRDA: Error: [Errno 2] No such file or directory: 'iw'
  Date: Mon Jun 16 13:41:12 2014
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   # Include files from /etc/network/interfaces.d:
   source-directory /etc/network/interfaces.d
  InstallationDate: Installed on 2014-06-16 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140616)
  IpRoute:
   default via 192.168.1.1 dev wlan0  proto static 
   10.144.147.0/24 dev rmnet_usb0  proto kernel  scope link  src 10.144.147.88  
metric 13 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.105  
metric 9
  PciNetwork:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.dbus.1.system.d.org.freedesktop.NetworkManager.conf: 
2014-06-11T20:47:57
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   /ril_0 gsm   connected 
/org/freedesktop/NetworkManager/Devices/1  
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8connected   enabled   enabled 
enabledenabled enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1330471/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1330471] Re: nm connects to far away access points since #83 mako flo

2014-08-18 Thread Alan Pope ㋛
This still happens on latest image. Every time I boot I have to switch
to a different access point to get a signal.

-- 
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/1330471

Title:
  nm connects to far away access points since #83 mako  flo

Status in “network-manager” package in Ubuntu:
  New

Bug description:
  For a few images now, on mako and flo my devices seem to cling onto
  access points which are far away rather than nearby ones.

  At home I have two access points named such that I know which is which
  (popey_2.4_bed  popey_2.4_den).

  When I boot up an Ubuntu device (phone/tablet) they always seem to
  attach to the far away access point and stay on it until I forcibly
  choose the other access point.

  I notice this a lot because I find using the phone slow because it's
  using the 'bed' AP which is at the other end of the house and through
  a few walls, whereas the 'den' one is right next to me in the office.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: network-manager 0.9.8.8-0ubuntu18
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.3-0ubuntu1
  Architecture: armhf
  CRDA: Error: [Errno 2] No such file or directory: 'iw'
  Date: Mon Jun 16 13:41:12 2014
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   # Include files from /etc/network/interfaces.d:
   source-directory /etc/network/interfaces.d
  InstallationDate: Installed on 2014-06-16 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140616)
  IpRoute:
   default via 192.168.1.1 dev wlan0  proto static 
   10.144.147.0/24 dev rmnet_usb0  proto kernel  scope link  src 10.144.147.88  
metric 13 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.105  
metric 9
  PciNetwork:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.dbus.1.system.d.org.freedesktop.NetworkManager.conf: 
2014-06-11T20:47:57
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   /ril_0 gsm   connected 
/org/freedesktop/NetworkManager/Devices/1  
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8connected   enabled   enabled 
enabledenabled enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1330471/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1330471] Re: nm connects to far away access points since #83 mako flo

2014-08-18 Thread Andrew Hayzen
Thank you for taking the time to report this bug and helping to make Ubuntu 
better.
I can confirm that when using the package network manager on ubuntu touch 
utopic #193 using the steps provided by Alan that I can reproduce the bug. 
Therefore I have set this bug to confirmed.


** Changed in: network-manager (Ubuntu)
   Status: New = Confirmed

-- 
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/1330471

Title:
  nm connects to far away access points since #83 mako  flo

Status in “network-manager” package in Ubuntu:
  Confirmed

Bug description:
  For a few images now, on mako and flo my devices seem to cling onto
  access points which are far away rather than nearby ones.

  At home I have two access points named such that I know which is which
  (popey_2.4_bed  popey_2.4_den).

  When I boot up an Ubuntu device (phone/tablet) they always seem to
  attach to the far away access point and stay on it until I forcibly
  choose the other access point.

  I notice this a lot because I find using the phone slow because it's
  using the 'bed' AP which is at the other end of the house and through
  a few walls, whereas the 'den' one is right next to me in the office.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: network-manager 0.9.8.8-0ubuntu18
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.3-0ubuntu1
  Architecture: armhf
  CRDA: Error: [Errno 2] No such file or directory: 'iw'
  Date: Mon Jun 16 13:41:12 2014
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   # Include files from /etc/network/interfaces.d:
   source-directory /etc/network/interfaces.d
  InstallationDate: Installed on 2014-06-16 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140616)
  IpRoute:
   default via 192.168.1.1 dev wlan0  proto static 
   10.144.147.0/24 dev rmnet_usb0  proto kernel  scope link  src 10.144.147.88  
metric 13 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.105  
metric 9
  PciNetwork:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.dbus.1.system.d.org.freedesktop.NetworkManager.conf: 
2014-06-11T20:47:57
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   /ril_0 gsm   connected 
/org/freedesktop/NetworkManager/Devices/1  
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8connected   enabled   enabled 
enabledenabled enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1330471/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1330471] Re: nm connects to far away access points since #83 mako flo

2014-07-16 Thread Alan Pope ㋛
** Summary changed:

- nm hangs onto far away access points #83 mako  flo
+ nm connects to far away access points since #83 mako  flo

-- 
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/1330471

Title:
  nm connects to far away access points since #83 mako  flo

Status in “network-manager” package in Ubuntu:
  New

Bug description:
  For a few images now, on mako and flo my devices seem to cling onto
  access points which are far away rather than nearby ones.

  At home I have two access points named such that I know which is which
  (popey_2.4_bed  popey_2.4_den).

  When I boot up an Ubuntu device (phone/tablet) they always seem to
  attach to the far away access point and stay on it until I forcibly
  choose the other access point.

  I notice this a lot because I find using the phone slow because it's
  using the 'bed' AP which is at the other end of the house and through
  a few walls, whereas the 'den' one is right next to me in the office.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: network-manager 0.9.8.8-0ubuntu18
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.3-0ubuntu1
  Architecture: armhf
  CRDA: Error: [Errno 2] No such file or directory: 'iw'
  Date: Mon Jun 16 13:41:12 2014
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   # Include files from /etc/network/interfaces.d:
   source-directory /etc/network/interfaces.d
  InstallationDate: Installed on 2014-06-16 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140616)
  IpRoute:
   default via 192.168.1.1 dev wlan0  proto static 
   10.144.147.0/24 dev rmnet_usb0  proto kernel  scope link  src 10.144.147.88  
metric 13 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.105  
metric 9
  PciNetwork:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.dbus.1.system.d.org.freedesktop.NetworkManager.conf: 
2014-06-11T20:47:57
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   /ril_0 gsm   connected 
/org/freedesktop/NetworkManager/Devices/1  
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8connected   enabled   enabled 
enabledenabled enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1330471/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp