[iwlagn] networkmanager applet cannot connect to WPA2 home network. Neither can WICD.

this is a critical bug in plasma network manager applet. it doesnt answer requests for secrets. meaning: it doesnt work for anything but open wifi networks.

ok, could be just that user submitted the syslog snippet when he cancelled attempt. i will debug that with him on IRC later. stay tuned.

Also, the laptop can't connect in ubuntu (gnome).

I added new syslog.ubuntu

Added new syslog

I used tha plasma applet

Complete kubuntu syslog added

indeed most likely a driver issue.

Bug reported upstream here: http://bugzilla.kernel.org/show_bug.cgi?id=12958

Keeping bug importance, and noting its been sent upstream can be marked as triaged.

I'm also having the same problem, after upgrading from Intrepid to Jaunty.
How can I help?

FYI, if it helps, I'm seeing the same issue on 2 laptops.

First laptop has an Intel PRO/Set 2200, that was a fresh install with Kubuntu jaunty from cd not more than a week ago, but fully updated as of today via wired connection.

Second laptop has an Intel PRO/Wireless 3945ABG, this was an upgrade from Intrepid to Jaunty. This one is also fully updated as of 10 mins ago, via wired connection.

This issue is not present in kernel 2.6.28-9-generic. It appears as if it was introduced in 2.6.28-10-generic. I also have an intel 3945 wireless card. Attatched is a snippet of my syslog, kernel daemon logs when trying to connect to my wireless lan at home w/ both WEP and WPA2 on Kernel 2.6.28-11-generic. Also I don't know if it will matter but I am running 64bit. It is a dell inspiron 1525n. If there is anything else needed please let me know.

I had a similar problem when I upgraded from hardy to intrepid on my fonero router.
I reported the problem here: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/263963
Now I'm using a different router.
It was never solved.

My router is a Thomson tg784 and it's not connect to fonero.

This is also affecting enterprise WPA2 networks. My university uses WPA2 with PEAP auth.

Hello ryan,

yes, but there is already another bug about WPA Enterprise networks: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/263963

We can focus here in the WPA personal networks.
If we are more specific is more easy to found the cause of the problem

I'm using the ath5k driver for Atheros AR242x card on 2.6.28-11-generic from Jaunty with the same issue. Its an ASUS F5 notebook.

This in syslog when trying to initiate a connection:

Mar 31 23:05:57 aether-laptop NetworkManager: <WARN> wait_for_connection_expired(): Connection (2) /org/freedesktop/NetworkManagerSettings/Connection/0 failed to activate (timeout): (0) Connection was not provided by any settings service

I'd have sworn I was using a different driver on Intrepid, maybe I blacklisted and used ndiswrapper... Anything I can do to help?

Ubuntu Intrepid Ibex (x86_64), network controller: Intel Corporation PRO/Wireless 4965 AG or AGN [Kedron] Network Connection (rev 61). Same problem with WPA Enterprise.

Javier,

Thank you. I understand the idea but would point out that WPA2
regardless of enterprise or personal is not working with what appears
a specific chipset. From what I understand, while obvious differences
between something that is enterprise grade and home/small office WPA2
its still WPA2 and the basics with its functionality is the same. And
I would advise that the two bugs be merged.

-Ryan

2009/3/31 Javier Jardón <email address hidden>:
> Hello ryan,
>
> yes, but there is already another bug about WPA Enterprise networks:
> https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/263963
>
> We can focus here in the WPA personal networks.
> If we are more specific is more easy to found the cause of the problem
>
> --
> [iwlagn] networkmanager applet cannot connect to WPA2 home network
> https://bugs.launchpad.net/bugs/348275
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Good news!

Today I can connect to my home WPA2 / AES network. Works in Ubuntu and Kubuntu.
I attach kubuntu syslog.

Added ubuntu syslog: syslog_ubuntu_works

Ok,

I can connect to my WPA2 network but after computer suspend I can't.

syslog_after_suspend_ubuntu attached

Seems to be fixed for Javier. ryan, can you confirm on latest Jaunty?

Alex, https://bugzilla.redhat.com/show_bug.cgi?id=388471 says that this was fixed in upstream NetworkManager. Javier says it's fixed for him. Can you please change the tasks/close as appropriate? Thank you!

I still can't connect to both of my wireless routers (Thomson tg784 and La Fonera) using WPA.
If I reboot them, I'm able to connect to them, almost instantly. After that, I'm unable to connect again.

Martin

I can confirm that the bug is still present even after the latest
updates (which i did not see networkmanager listed for update).
Rolling back to kernel 2.6.28-9 is the only work around that i have
found to work for my situation right now. My home router is a linksys
WRT-54GL at University it is Cisco based w/ PEAP and MSCHAPv2 for
inner auth. method.

-Ryan

On Wed, Apr 1, 2009 at 04:32, jmachado <email address hidden> wrote:
> I still can't connect to both of my wireless routers (Thomson tg784 and La Fonera) using WPA.
> If I reboot them, I'm able to connect to them, almost instantly. After that, I'm unable to connect again.
>
> --
> [iwlagn] networkmanager applet cannot connect to WPA2 home network
> https://bugs.launchpad.net/bugs/348275
> You received this bug notification because you are a direct subscriber
> of the bug.
>

this bug was a driver bug which seems to be fixed now. Its been reported as fixed in bug 329798 too as it seems; NM certainly didnt change anything in the last rounds that could have fixed this.

When is the patched driver in the kernel going to be released? As of
this morning with the latest updates I am unable to connect to any
WPA2 Personal/Enterprise Network. The only solution has been to roll
back to 2.6.28-9 as both 2.6.28.-10 and 2.6.28-11 are broken.

On Wed, Apr 1, 2009 at 09:31, Alexander Sack <email address hidden> wrote:
> this bug was a driver bug which seems to be fixed now. Its been reported
> as fixed in bug 329798 too as it seems; NM certainly didnt change
> anything in the last rounds that could have fixed this.
>
> ** Changed in: plasma-widget-network-manager (Ubuntu Jaunty)
>       Status: Triaged => Invalid
>
> --
> [iwlagn] networkmanager applet cannot connect to WPA2 home network
> https://bugs.launchpad.net/bugs/348275
> You received this bug notification because you are a direct subscriber
> of the bug.
>

What is critical about this? It doesn't appear to be an issue any longer.

Javier, regarding comment 25, "I can connect to my WPA2 network but after computer suspend I can't." (https://bugs.edge.launchpad.net/ubuntu/+bug/348275/comments/25), could you open a new bug report for that issue?

Also, per a request from the release team, we will reopen this bug as it is fixed from some but not everyone. Thanks.

This is still a problem for some users:
HW:
    description: Notebook
    product: HP Pavilion dv7 Notebook PC
    vendor: Hewlett-Packard
    version: 1
    serial: xxxxxxxxxx
    width: 64 bits
    capabilities: smbios-2.4 dmi-2.4 vsyscall64 vsyscall32

 ~$ uname -a
   2.6.28-11-generic #39-Ubuntu SMP Thu Apr 2 04:39:54 UTC 2009 x86_64 GNU/Linux

 ~$ dmesg | grep ath5k
[ 15.231457] ath5k_pci 0000:09:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
[ 15.231470] ath5k_pci 0000:09:00.0: setting latency timer to 64
[ 15.231558] ath5k_pci 0000:09:00.0: registered as 'phy0'
[ 15.372371] ath5k phy0: Atheros AR2425 chip found (MAC: 0xe2, PHY: 0x70)
[ 30.535823] ath5k phy0: gain calibration timeout (2412MHz)
[ 30.535827] ath5k phy0: can't reset hardware (-11)
[ 30.907197] ath5k phy0: gain calibration timeout (2412MHz)
[ 30.907202] ath5k phy0: can't reset hardware (-11)

 ~$ sudo lshw
*-network DISABLED
    description: Wireless interface
    product: AR242x 802.11abg Wireless PCI Express Adapter
    vendor: Atheros Communications Inc.
    physical id: 0
    bus info: pci@0000:09:00.0
    logical name: wmaster0
    version: 01
    serial: xx:xx:xx:xx:xx:xx
    width: 64 bits
    clock: 33MHz
    capabilities: pm msi pciexpress msix bus_master cap_list logical ethernet physical wireless ...

Just made a discovery that seems strange but could be unrelated:
From the dmesg output:
[ 15.231457] ath5k_pci 0000:09:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
 And when checking with:
sudo lspci -vvnn:
09:00.0 Ethernet controller [0200]: Atheros Communications Inc. AR242x 802.11abg Wireless PCI Express Adapter [168c:001c] (rev 01)
        Subsystem: Hewlett-Packard Company Device [103c:137b]
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0, Cache Line Size: 128 bytes
        Interrupt: pin A routed to IRQ 18
!!! Last line could be important when comparing with video:
01:00.0 VGA compatible controller [0300]: ATI Technologies Inc Mobility Radeon HD 3400 Series [1002:95c4]
        Subsystem: Hewlett-Packard Company Device [103c:30fc]
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0
        Interrupt: pin A routed to IRQ 18

Looks like an IRQ conflict but it is maybe not important.......

I have the same problem with Atheros AR242x and ubuntu jauntly UNR with the last updates. If you want I can give you all info you need

this is happening to me as well, was working with 2.6.28-11.39... but in 11.40 it is unable to connect.

I dist-upgraded from intrepid to jaunty, and check daily for new updates... WPA broke on me yesterday, so now it is back to the good old Adamm's kernel :(

I am still able to use the network with other computers, and also can get onto unsecure networks.
Using an RaLink RT2860

I suggest this might actually be an issue with wpasupplicant. I cannot do a connection with that either.

This is my output when trying to connect with wpa_supplicant - my key was generated with wpa_passphrase.

aether@aether-laptop:/etc$ sudo wpa_supplicant -iwlan0 -c/etc/wpa_supplicant.conf
ioctl[SIOCGIWSCAN]: Resource temporarily unavailable
CTRL-EVENT-SCAN-RESULTS
Trying to associate with 00:14:6c:69:1d:ce (SSID='WirelessAP' freq=2462 MHz)
Associated with 00:00:00:00:00:00
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
ioctl[SIOCSIWENCODEEXT]: No such file or directory
CTRL-EVENT-SCAN-RESULTS
Trying to associate with 00:14:6c:69:1d:ce (SSID='FancyPantsJane' freq=2462 MHz)
Associated with 00:00:00:00:00:00
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
ioctl[SIOCSIWENCODEEXT]: No such file or directory

FYI, I have two PCs using different cards with the issue, one with an Atheros AR5001X+ and the other with an Atheros AR242x, I have Jaunty_Proposed in my repository and all up to date. Both can connect to open or WEP protected networks.

I did a search for bugs in wpasupplicant on launchpad but couldn't find a relevant one. I can start attaching random log files if it will help? Does network manager just use wpasupplicant? If so, I suggest this would be a critical bug there.

I would like to confirm that I've been experiencing this same bug on my laptop with an Intel PRO/Wireless 5100 AGN controller.

After resuming from suspend, I would not be able to connect to a WPA2 network (WPA2-PSK).

When I unloaded and reloaded the wifi module, iwlagn, I was then able to connect to the wpa2 network.

This was the messages found in dmesg when failing to connect:

wlan0: authenticate with AP XX:XX:XX:XX:XX:XX
wlan0: authenticated
wlan0: associate with AP XX:XX:XX:XX:XX:XX
wlan0: RX AssocResp from XX:XX:XX:XX:XX:XX (capab=0x1 status=10 aid=0)
wlan0: AP denied association (code=10)

Nope. Just updated Jaunty on my laptop fully and removed WICD and installed plasma-widget-network-manager. Rebooted and added the widget to the desktop.

Intel PRO/Wireless 3945ABG.

Doesn't offer WPA2 as an option. WICD works fine. Now I need to go find my wire and reinstall WICD.

Fonera 2100 and Fonera 2200 specs:

http://www.dd-wrt.com/wiki/index.php/La_Fonera_Hardware_Specifications

I was having similar problems in Ubuntu 9.04 Jaunty Jackalope on aToshiba satellite a75-s209 , ATI Radeon, gnome desktop . These have disappeared after I uninstalled compiz .

The issue seems to be with KDE Network Manager. Here is what I found out by running Ubunutu 9.04 and Kubuntu 9.04 live CDs:

- connection to non-secured wireless AP works in both
- connection to WPA secured AP works out of the box only from Ubuntu, but not from Kubuntu
- connection to WPA secured AP is possible to setup from Kubuntu through 'interfaces' and 'wpa_supplicant.conf' files as outlines in https://help.ubuntu.com/community/WifiDocs/WPAHowTo
- all of the above was done on the same wireless client (Lenovo R51 notebook) and AP (WRT54G with Tomtato firmware)

Some details:
--------------------
Ubuntu 9.04 Live off the CD
- Connects to WPA2 secured network out of the box
-- asks for WPA2 keyphrase
-- then asks for KeyRing (or smth like that) password, the step that is missing in KDE4 NetManager

Kubuntu 9.04 Live off the CD
- Does NOT connects to WPA2 secured network out of the box
- the workaround through wpa_supplicant.conf file does work

Some conclusions: since the 'low level' wireless setup (through wpa_supplicant) does work even in Kubuntu, it really seems to be the issue with the KDE Network Manager rather than chipset drivers....

Just my 2c..

It sounds very much like there are two bugs here. The first is the KDE network manager bug that volenin describes above that is fixed by installing linux-backports-modules-jaunty. The second seems to be hardware specific as described in Javier's last couple of messages.

I would like to add that I've the same problem with different hardware. I've a desktop pc (no brand) with an usb wireless network card (WN121T), working with the ndiswrapper module, on an Ubuntu 9.04 fresh installation. I can make a connection to a wpa access point, but after an random amount of time it disconnects and can't reconnect. This also happens with a WEP accespoint. If there is no encryption, the connection is stable.

On two installs of Jaunty Jacaklope Ubuntu:
One on a desktop PC, upgraded from a clean install of Ubuntu 8.10, a WPA2 secured network cannot be connected to, using a Netgear WPN111 USB wireless adaptor
One on a laptop using an Atheros AR5005G wireless adaptor, upgraded from a clean install of Xubuntu 8.10 to Jaunty, same problem.
Both try to connect, but never ask for any login credentials, and after a lengthy time, fail to connect at all.

i am not able to connect to a wpa2 peap mschapv2 network.

i am running jaunty 2.6.28-11 with an ar5212 pcmcia card. with wicd. i have tried wpa_supplicant with ndiswrapper, madwifi and ath5k drivers.

I am able to get and 'inet6' adress in ifconfig but when i run dhclient i can never get an IP adress : 'inet addr" in ifconfig.

I am also having a similar issue with Jaunty (2.6.28-11-generic) & Gnome (2.26.1) running on a Dell Mini 9 with a Broadcom wireless card. This was an initial Release Candidate install, but I have been performing regular updates.

I was able to connect to WPA2 Personal networks without any issues up until a week ago. Then it stopped working. I can successfully connect to unsecured networks. I have tried WPA Personal, WPA2 Personal and WPA/WPA2 Mixed. All are unsuccessful.

I have reinstalled WPASupplicant and Network Manager. I have uninstalled Network Manager and installed WICD. All of these attempts have been unsuccessful.

I am running a Linksys WRT54G with dd_WRT, hidden SSID, WPA/WPA2 Mixed.

Recently, I have noticed the Keyring popup message when I make changes to the wireless network settings. I don't remember these messages a couple weeks ago.

Could this have something to do with the WPA Passphrase getting stored in the keyring.

- Tim

I had the same problem but on the new Studio 15 ( 1550) using the 5100 wifi card.
Updating through the ubuntu packages from linuxwireless.org did not help. (Did not try loading the latest patches by compiling from source).
The problem was related to the n-mode, switching it off works as a work-around until the firmware gets updated:

create (or modify) iwlagn.conf:

sudo gedit /etc/modprobe.d/iwlagn.conf

and add:

options iwlagn 11n_disable=1
options iwlagn 11n_disable50=1

$ lspci | grep -i wireless
0c:00.0 Network controller: Intel Corporation PRO/Wireless 4965 AG or AGN [Kedron] Network Connection (rev 61)

I've had this problem too. Installing linux-backports-modules-jaunty-generic and adding the "11n_disable*" options in iwlagn didn't fix it for me.

This is now fixed for me. I believe the remedy was installing the latest stable compat-wireless drivers: http://wireless.kernel.org/en/users/Download/stable/

I was able to attach to my WPA2 wireless router by broadcasting the SSID. If the SSID is hidden, it will not connect.

This was working when I was running the Jaunty RC (before the release). Then I ran the updater on the same machine to get the 9.04 release files and the wireless stopped auto connecting to my WPA2, hidden SSID router (WRT54G/dd-WRT). I have seen threads that point this issue to "wpa-supplicant".

Thanks,

Tim

I am still successfully connecting via WPA2 after enabling my SSID to be broadcast on my wireless router.

Can someone else verify their SSID broadcast options and test with SSID broadcast enabled. Then test with SSID broadcast disabled.

- Tim

thornbe:
With fully upgraded Jaunty, Network Manager cannot find the network with broadcast disabled, and still cannot connect successfully with it enabled for me. It asks for the network password a few times, then fails.

Fred,

Are you using "WPA & WPA2 Personal" as your "Security:" setting?

What is the brand of your wireless router?

How do you have the Security set on the wireless router?

Thanks,

Tim

Yes, it's WPA & WPA2 Personal
The router is a Netgear DG834PN, I'm not allowed to login to change any settings on it, but I know it's using the last patch from the Netgear website, and is also set to WPA2. It's not likely I could get him to change the security on it, so I'm stuck using it.

THORNBE Information:

Hardware: Dell Mini 9
Network Controller: Broadcom Corporation BCM4312 802.11b/g (rev 01)
Network Driver: Broadcom STA Wireless Driver
Ubuntu: 9.04 (updated from 9.04 RC)
Kernel: 2.6.28-11-generic
Network Manager: 0.7.1~rc4.1.cf199a964-0ubuntu2
NM Security Setting: WPA & WPA2 Personal
WPASupplicant Version: 0.6.6-2ubuntu1
Wireless Router: Linksys WRT54G
Router OS: dd-WRT
Wireless Security Settings: WPA & WPA2 Personal, TKIP/AES

Can others post their settings to see if we can find a correlation?

Thanks,

Tim

My info:

Hardware: Sony VAIO FZ430E laptop
Network controller: Intel Corporation PRO/Wireless 4965 AG or AGN [Kedron] Network Connection (rev 61)
Network driver: Intel Wireless WiFi Link AGN driver for Linux (iwlagn 1.3.27ks)
OS: Kubuntu 9.04 x86_64 (fresh install)
Kernel: 2.6.28-13-generic
Network manager: 0.7.1~rc4.1.cf199a964-0ubuntu2
NM security setting: WPA2-PSK
WPASupplicant version: 0.6.6-2ubuntu1
Wireless router: 2WIRE 3800HGV-B
Wireless security settings: WPA2-PSK, SSID broadcast enabled

Per my comment several weeks ago, I had trouble connecting at first, but things started working after I installed linux-backports-generic.

I also use this laptop on the wireless network at work, but that's an unsecured guest network and I've had no trouble with it.

Craig,

I see you have SSID Broadcast enabled. Can you disable the SSID broadcast and see if your VAIO can connect?

Thanks,

Tim

Linux Kernel Bug Tracker #12958 parted ways with this bug months ago.

I disabled my SSID broadcast last night and tested each of the WPA security settings on the wireless router. The WPA Personal, WPA2, WPA2 Mixed options with the SSID broadcast disabled did not allow my Dell Mini to connect at all. Once I enabled SSID broadcast, it would connect without issue. I did not change any settings on my netbook.

I have a co-worker that has a Dell Mini and runs 9.04, he just confirmed with the same issues. He has his wireless router set to broadcast the SSID.

Thanks,

Tim

Tim, per your request I tried disabling SSID broadcast at my main AP. My VAIO would then connect only to a wireless repeater further away (which does not seem to have an option to disable SSID broadcast), not to the main AP as it normally does.

Based on an above comment by "ryan" on 2009-04-01, it appears Kernel 2.6.28-9 was working and now kernels 2.6.28.10 and above are broken.

How would we proceed with identifying the kernel changes from version 2.6.28-9 to version 2.6.28-10 that would affect wireless networking, WPA security or interaction with Network Manager/WPA-Supplicant?

If the change is identified, how do we get it to be fixed?

Thanks,

Tim

The 2.6.28-14-generic kernel was released yesterday. I loaded the new kernel, disabled the SSID broadcast on my wireless router and I was able to auto connect through my wireless interface on my Dell Mini 9.

It appears this issue might have been fixed with this latest kernel. Can others that were having the same issue give the new kernel a try and report back their status?

Thanks,

Tim

thornbe: I'm not able to confirm that. a Dell Latitude c400 here with a clean Jaunty install updated to that kernel still cannot connect to any hidden wireless network, nor any secured network.
It seems to be regardless of the security used, at present, but as I have no way of changing my router's security, I can't verify that.

I can't connect too with NM using iwlagn with simple WPA authentication

My info:

Hardware: Keynux laptop
Network controller: Intel Corporation Wireless WiFi Link 5100
Network driver: iwlagn: Intel(R) Wireless WiFi Link AGN driver for Linux, 1.3.27ks
OS: Ubuntu 9.04 x86_64 (fresh install)
Kernel: 2.6.28-14-generic
Network manager: 0.7.1~rc4.1.cf199a964-0ubuntu2
NM security setting: WPA-PSK
WPASupplicant version: 0.6.6-2ubuntu1
Wireless router: Acer
Wireless security settings: WPA-PSK, SSID broadcast enabled

linux-backport-modules-jaunty not installed but wireless-compat used instead in version 2.6

I joined syslog.txt

Thanks for your help

Should I upgrade NM ?

Same problem with WICD

Sorry iwlagn works for me now with WEP and simple WPA. I turned out bluetooth and it started working !?!
The problem seems to be else where. If someone has an idea, just let me know directly. I stop spoiling the list right now.
Best regards.

I found out one of the AP's was still configured to broadcast it's SSID. After disabling the SSID broadcast, I was not able to connect. The 2.6.28-14-generic kernel does not appear to fix the issue.

Sorry for the confusion.

Thanks,

Tim

Connecting manually with wpa_supplicant does not work when NetworkManager is running. Stopping NetworkManager enables wpa_supplicant to connect,

With NetworkManager running wpa_supplicant actually connects but is kicked of again. Any good hint on what to try on my systen to hunt this down?

With NetworkManager running but without having knetworkmanager running wpa_supplicant gives me this :

CTRL-EVENT-SCAN-RESULTS
WPS-AP-AVAILABLE
Trying to associate with 00:09:5b:d0:37:ab (SSID='SGH' freq=2462 MHz)
Association request to the driver failed
Associated with 00:00:00:00:00:00
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
ioctl[SIOCSIWSCAN]: Device or resource busy
Failed to initiate AP scan.
CTRL-EVENT-SCAN-RESULTS
WPS-AP-AVAILABLE
Trying to associate with 00:09:5b:d0:37:ab (SSID='SGH' freq=2462 MHz)
Association request to the driver failed
Associated with 00:09:5b:d0:37:ab
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
ioctl[SIOCSIWSCAN]: Device or resource busy
Failed to initiate AP scan.
CTRL-EVENT-SCAN-RESULTS
Trying to associate with 00:09:5b:d0:37:ab (SSID='SGH' freq=2462 MHz)
Association request to the driver failed
Associated with 00:00:00:00:00:00
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
ioctl[SIOCSIWSCAN]: Device or resource busy
Failed to initiate AP scan.
CTRL-EVENT-SCAN-RESULTS

After killing NetworkManager i get :

ioctl[SIOCSIWSCAN]: Device or resource busy
Failed to initiate AP scan.
CTRL-EVENT-SCAN-RESULTS
Trying to associate with 00:09:5b:d0:37:ab (SSID='SGH' freq=2462 MHz)
Association request to the driver failed
Associated with 00:09:5b:d0:37:ab
WPA: Key negotiation completed with 00:09:5b:d0:37:ab [PTK=TKIP GTK=TKIP]
CTRL-EVENT-CONNECTED - Connection to 00:09:5b:d0:37:ab completed (auth) [id=0 id_str=]

Problem is gone in

Linux phoenix 2.6.31-6-generic #25-Ubuntu SMP Fri Aug 14 16:28:28 UTC 2009 x86_64 GNU/Linux

We have two new notebooks and network manager keeps losing connection. When we check "edit connections"; the password has been changed to some garbled lengthy code. Something we didn't put in.

This happens all the time and its getting frustrating, especially with all the postings in launchpad and very few confirmed status listings.

The forums and web are plastered with this problem. There are over a hundred right here on this thread. I can't believe the foot dragging on this issue. Internet connections are a serious component of any computer. C'mon guys.

What the hell is up with network manager and why doesn't Canonical get with it?

I'd like to respond to Ronnie's recent comments...

Canonical has responded to this bug from the start. One of the problems is that multiple bugs have been intermingled in a single bug report and thus it makes it very hard to manage.

Javier, the *original* bug reporter stated that he couldn't connect to a WPA2/AES access point.

He also changed the original description to state that by installing linux-backports-generic, and the Jaunty version of network-manager from the PPA, that his problem resolved. Similarly, he's stated that it works in the current development release ( Karmic ) as well.

As for the garbled key / passphrase displayed when using "Edit Connections", unfortunately this is the way the network-manager applet used to store keys & passphrases. The keys/passphrases input by the user were transformed into the native format, which as you've pointed out makes it very hard to edit. This has been fixed in NM 0.8 which will be included in Ubuntu 9.10. For more details about hashed keys, you can read Dan William's blog which describes in detail how NM 0.7 handled keys ( search for "hashed keys" in the page ).

http://blogs.gnome.org/dcbw/category/networkmanager/

Also Ronnie, losing connections again is a *different* problem than what Javier originally described. If you're still experiencing this problem, please enter a *new* bug report. Please see the following Wiki page for more information on how to properly do so:

https://help.ubuntu.com/community/ReportingBugs

Finally, it's my opinion that the linux (ubuntu) portion of this bug should be marked WontFix, as installing backports modules seems to fix the original problem, and as pointed out above, it's fixed in Karmic.

The original issue was deemed to not be an issue with the plasma widget.

The linux package is fixed in Karmic.

I just reinstalled 9.04 on my Dell Mini 9. I installed all Updates. Tested wireless connectivity with the WPA Personal security and SSID Broadcast = Disabled. It would not connect. I installed the "generic-linux-backports" and anything related to wireless disappeared through Network Manager.

I tried to install Karmic and the installer "Ubiquity" kept crashing. So no Karmic Alpha 4, yet.

Does anyone have the exact steps to install the "backports" and the 0.8 version of Network Manager?

Thanks,

Tim

I was able to get the "generic-linux-backports" installed and working correctly with Network Manager. I disabled SSID Broadcasts on both of my wireless routers and my Dell Mini still can not connect automatically.

Any ideas?

Thanks,

Tim

I swapped out my Broadcom Corporation BCM4312 802.11b/g (rev 01) wireless adapter with an Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02) wireless adapter and I am able to connect to my wireless router with the SSID Broadcast "Disabled".

I am no longer using the "Broadcom STA Wireless Driver" and everything else has stayed the same. I am guessing the proprietary hardware drive was contributing to the problem.

Good luck to everyone,

Tim

Setting the linux Jaunty task to won't fix as it appears to be resolved via linux-backports-modules for Jaunty. Thanks.