** Summary changed:

- wireless connection error and general issues connecting
+ Wi-Fi doesn't connect; disconnecting causes "Connection Activation Failed 
(32)" dialog; reboot usually fixes it

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

Title:
  Wi-Fi doesn't connect; disconnecting causes "Connection Activation
  Failed (32)" dialog; reboot usually fixes it

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

Bug description:
  In 12.10 I have noticed that when I boot up often times network-
  manager sits in a loop trying to connect to my wifi and when I then
  click the dialog and click disconnect to end the looping attempt and
  try to restart the connecting process I get an error

  "Connection Activation Failed (32)"

  When this bug occurs the only way for me to connect wirelessly is to:

  1.) Connect to my Guest Wireless SSID?
  2.) Reboot and try again (usually resolves and allows me to connect)

  
  I know that its not the wireless hardware (AP) or even signal levels since 
this has occurred on two different routers both of which were high-end 
dual-band routers.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: network-manager 0.9.6.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-8.8-generic 3.5.0
  Uname: Linux 3.5.0-8-generic x86_64
  ApportVersion: 2.4-0ubuntu6
  Architecture: amd64
  Date: Thu Aug  9 09:57:52 2012
  EcryptfsInUse: Yes
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  IpRoute:
   default via 192.168.33.1 dev wlan0  proto static 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.33.0/24 dev wlan0  proto kernel  scope link  src 192.168.33.122  
metric 9
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to quantal on 2012-08-08 (0 days ago)
  nmcli-con:
   NAME                      UUID                                   TYPE        
      TIMESTAMP    TIMESTAMP-REAL                     AUTOCONNECT   READONLY   
DBUS-PATH                                 
   Circle of Friends         d7a2eadd-e5c1-4816-9223-8c773cba460f   
802-11-wireless   0            never                              yes           
no         /org/freedesktop/NetworkManager/Settings/2
   Wired connection 1        283a782b-a730-4c24-b28e-80f4c0f0e0db   
802-3-ethernet    1344531260   Thu 09 Aug 2012 09:54:20 AM PDT    yes           
no         /org/freedesktop/NetworkManager/Settings/1
   VPN connection 1          a39c3e45-8bfb-4a87-b424-32123b2422fc   vpn         
      0            never                              yes           no         
/org/freedesktop/NetworkManager/Settings/0
   Circle of Friends-guest   22726422-07db-4bbc-907c-4fcd6240a0e3   
802-11-wireless   1344531327   Thu 09 Aug 2012 09:55:27 AM PDT    yes           
no         /org/freedesktop/NetworkManager/Settings/3
  nmcli-dev:
   DEVICE     TYPE              STATE         DBUS-PATH                         
         
   eth0       802-3-ethernet    unavailable   
/org/freedesktop/NetworkManager/Devices/1  
   wlan0      802-11-wireless   connected     
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING         VERSION    STATE           NET-ENABLED   WIFI-HARDWARE   
WIFI       WWAN-HARDWARE   WWAN      
   running         0.9.6.0    connected       enabled       enabled         
enabled    enabled         disabled

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

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

Reply via email to