Network-Manager won't connect to wifi with n-channels

[r_avital]

ubuntu@ubuntu:~$ lsb_release -rd
Description: Ubuntu 14.04 LTS
Release: 14.04

ubuntu@ubuntu:~$ apt-cache policy network-manager
network-manager:
  Installed: 0.9.8.8-0ubuntu7
  Candidate: 0.9.8.8-0ubuntu7
  Version table:
 *** 0.9.8.8-0ubuntu7 0
        500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
        100 /var/lib/dpkg/status

ubuntu@ubuntu:~$ uname -a
Linux ubuntu 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:11:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

Problem with wifi connection.

Behavior in 13.04, 13.10, using laptop's built'in wifi adapter (wlan0, see diagnostics below):
Connection is ok, in fact so fast that the laptop is connected by the time lightdm shows login screen.

Behavior in 14.04 LTS:
With laptop's built-in wifi adapter (wlan0) - prompt for password (for secure WEP-Personal network), attempt to connect, prompt for password again, attempt again, repeat. Never connects, process only interruptible by user intervension (hit "Cancel").

Same result in the case of a non-secured "open" network on same AP - connection fails (except no prompt for password obviously).

With USB wifi dongle plugged in (wlan1) - connection is quick and flawless.

Expected behavior: network-manager should connect with the laptop's built-in wan adapter (wan0) ***as it did in the previous versions mentioned above, same laptop, same hardware, sam AP, same network(s).***

Some diagnostics:

lspci: (Built-in wlan0: Intel Corporation Centrino Advanced-N 6200
usb wifi dongle wlan1:Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller

lspci output:
ubuntu@ubuntu:~$ lspci -nnk | grep -iA2 net
02:00.0 Network controller [0280]: Intel Corporation Centrino Advanced-N 6200 [8086:4239] (rev 35)
 Subsystem: Intel Corporation Centrino Advanced-N 6200 2x2 AGN [8086:1311]
 Kernel driver in use: iwlwifi
03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 03)
 Subsystem: Hewlett-Packard Company Device [103c:7001]
 Kernel driver in use: r8169
========================

ifconfig output:
eth0 Link encap:Ethernet HWaddr 60:eb:69:41:6c:38
          UP BROADCAST MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

lo Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING MTU:65536 Metric:1
          RX packets:729 errors:0 dropped:0 overruns:0 frame:0
          TX packets:729 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:75318 (75.3 KB) TX bytes:75318 (75.3 KB)

wlan0 Link encap:Ethernet HWaddr 00:27:10:97:75:9c
          UP BROADCAST MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

wlan1 Link encap:Ethernet HWaddr 00:21:2f:35:73:50
          inet addr:192.168.0.40 Bcast:192.168.0.255 Mask:255.255.255.0
          inet6 addr: fe80::221:2fff:fe35:7350/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:11823 errors:0 dropped:1 overruns:0 frame:0
          TX packets:5340 errors:0 dropped:1 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:8420626 (8.4 MB) TX bytes:810908 (810.9 KB)
========================

iwconfig:
wlan1 IEEE 802.11bg ESSID:"AVITAL_SECURE" Nickname:"rtl_wifi"
          Mode:Managed Frequency:2.462 GHz Access Point: 00:18:4D:44:A4:BD
          Bit Rate:54 Mb/s Sensitivity:0/0
          Retry:off RTS thr:off Fragment thr:off
          Power Management:off
          Link Quality=100/100 Signal level=100/100 Noise level=0/100
          Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
          Tx excessive retries:0 Invalid misc:0 Missed beacon:0

eth0 no wireless extensions.

lo no wireless extensions.

wlan0 IEEE 802.11abgn ESSID:off/any
          Mode:Managed Access Point: Not-Associated Tx-Power=15 dBm
          Retry long limit:7 RTS thr:off Fragment thr:off
          Power Management:off
========================

nm-tool:
NetworkManager Tool

State: connected (global)

- Device: wlan1 [Wi-Fi connection 1] ------------------------------------------
  Type: 802.11 WiFi
  Driver: r8712u
  State: connected
  Default: yes
  HW Address: 00:21:2F:35:73:50

  Capabilities:
    Speed: 54 Mb/s

  Wireless Properties
    WEP Encryption: yes
    WPA Encryption: yes
    WPA2 Encryption: yes

  Wireless Access Points (* = current AP)
    *MY_SSID: Infra, 00:18:4D:44:A4:BD, Freq 2462 MHz, Rate 54 Mb/s, Strength 100 WPA WPA2

  IPv4 Settings:
    Address: 192.168.0.40
    Prefix: 24 (255.255.255.0)
    Gateway: 192.168.0.1

    DNS: 192.168.0.1

- Device: eth0 -----------------------------------------------------------------
  Type: Wired
  Driver: r8169
  State: unavailable
  Default: no
  HW Address: 60:EB:69:41:6C:38

  Capabilities:
    Carrier Detect: yes

  Wired Properties
    Carrier: off

- Device: wlan0 ----------------------------------------------------------------
  Type: 802.11 WiFi
  Driver: iwlwifi
  State: disconnected
  Default: no
  HW Address: 00:27:10:97:75:9C

  Capabilities:

  Wireless Properties
    WEP Encryption: yes
    WPA Encryption: yes
    WPA2 Encryption: yes

  Wireless Access Points
    MY_SSID: Infra, 00:18:4D:44:A4:BD, Freq 2462 MHz, Rate 54 Mb/s, Strength 100 WPA WPA2
========================

rfkill list all:
0: hci0: Bluetooth
 Soft blocked: no
 Hard blocked: no
1: hp-wifi: Wireless LAN
 Soft blocked: no
 Hard blocked: no
2: hp-bluetooth: Bluetooth
 Soft blocked: no
 Hard blocked: no
3: phy0: Wireless LAN
 Soft blocked: no
 Hard blocked: no
========================
End of diagnostics.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.