NetworkManager or wpa_supplicant timing out when connecting wireless

I'm agreeing with a few more people and think it's more probable to be a bug in wpa_supplicant. plasma_widget_manager doesn't work, nor does wicd when I eliminate NetworkManager altogether.

Full log attached...

This bug is not a duplicate of bug 572777 - I can see all the access points around my computer, I'm just unable to connect to them.

Err, sorry - this bug is not a duplicate of bug 575677 - I can see all the access points around my computer, I'm just unable to connect to them.

Duplicate status removed. Sorry.

Still researching and reading - if this is a duplicate bug, then it's possibly a duplicate of 496093. The threads mostly around RaLink drivers, but I've seen a few postings from people with Intel wireless and Broadcom wireless based cards having the same issue. Looking at my log, I see the same "Association request to the driver failed" that started that bug. Still reading the messages as there is lot's of posts. The worry here is that most of the posts are focused on the Ralink driver - not wpa_supplicant, and only a couple of brief messages of affects me to from a couple of people with other wireless - if that's bug is only specifically for the RaLink driver, then this bug report is not a duplicate of that issue.

The other bug, 572777, is a problem with the rt2860 driver in the 2.6.32 kernel that Ubuntu lucid came with. Unless the Broadcom chip is using the rt2860 driver (you can check with lshw -C network), I think this might be a separate issue with similar symptoms.

Hi all,
I have similar problem, with an Elitebook 8530w Network controller: Intel Corporation Wireless WiFi Link 5300.
The most strange is than at home it works fine, but at the office it stop working every 2 - 3 minutes even if knetworkmanager show it as connected.
At the office I have a college how uses Kubuntu 10.04 and for him everything works fine.

Can I do something to help you?

Okay, I'm comfortable this is not a duplicate of 496093 - I'm using the wl Broadcom Hybird STA driver. Last night I downloaded the driver directly from Broadcom, compiled it and replaced the one in my kernel - no change in establishing connection (I initally tried using the packaged version avalible, but I noticed that it compiles with errors). I also downgraded wpa_suppicant to the one in Karmac - again, no chage. So tonight I'll compile wpa_supplicant & networkmanager from source and see where I end up.

Zarama - is there any differances between the configuration of your home network and office (ie: is one using WEP security and the other WPA?).

I have a similar problem. I posted my comments here: http://ubuntuforums.org/showthread.php?t=1473260

I had been running Ubuntu 9.10 64-bit very successfully on my Dell 1420 laptop with a Broadcom 4328 wireless card and the proprietary drivers (v5.60.48.36). All was well - I could login to any wireless network that my system could detect at I could provide access info to.

I performed a clean install of Ubuntu 10.04 64-bit to this very same system. Everything works well except that I cannot log in to wireless systems that require a password. I can connect by hard-wire and I can connect to 'open' systems that do not require a password to get onto the wireless network.

I can 'see' all of the local wireless networks on my machine, but I can only successfully login to those without passwords required. And, yes, I am typing the passwords in correctly...

Any help here would be greatly appreciated - I'm quite mobile with my Ubuntu laptop for work purposes.

Hi nukedathlonman,
No both(home / office) use WAP2/Personal

Hmmm... Well, I see a couple of things to go on right now. I haven't tried unsecured or WEP based encrypted access points like Steve has - I'll dig out my old back up router and configure it up as a non-protected access point as well as a WEP encrypted one this weekend to check those ends as that would be a clear indicator of a problem with the wl driver.

I'll stick to my original game plan and self compile wpa_supplicant and networkmanager and see if I can get some debugging out put from them. My worry is it doesn't appear to be a Broadcom driver problem since there is someone with an Intel based wireless card reporting the same problem here. I know there is also a ton of posts in the ubuntu forms for serveral differant manufacturers of wireless cards doing this exact same thing. Can everyone dig through there logs and post them - be much easier for all of us to at least narrow down which package is failing for us all.

I'd like to also say that I have this problem. Using 10.04 and kernel 2.6.32-22 on 64-bit. I have a Broadcom 4312 card on my laptop, with a ZyXEL router using WPA-PSK enabled. Just now I logged on and failed to connect. Waited a few minutes to try again and was connected to the router. I usually have to try numerous times before I could connect, one time it took almost an hour and a half.

Just a note -- I have no trouble connecting an unsecured router at the local coffeshop.

Let me know if any output is required.

Hi Rick - are you using the closed wl driver or the open B43 driver (for further confirmation of other drivers the bug is effecting)?

nukedathlonman --

I am using the STA Drivers which includes the wl driver.

Rick

On Fri, 2010-05-07 at 13:50 +0000, nukedathlonman wrote:
> Hi Rick - are you using the closed wl driver or the open B43 driver (for
> further confirmation of other drivers the bug is effecting)?
>

nukedathlonman --

I am using the STA drivers which includes the wl driver.

Rick

Okay. So far just tthe Intel 5300 and the closed Broadcom STA drivers seem to be effected (at least as reported in this bug so far).

I have the same problem on my Dell Vostro 1510 with "Broadcom Corporation BCM4328 802.11a/b/g/n (rev 03)" and Broadcom STA driver.

Sometimes it helps when I run "restart network-manager" (usually I have to run it twice with about 1 minute delay between each turn).

Backstory:

On my 32bit Lucid installation, this would only work after running the following commands in a terminal:

sudo rmmod wl
*wait a few seconds*
sudo modprobe wl

Once I run those commands, it usually connects on the next try. If it doesn't, I run them again and it works.

Now I just installed Lucid 64bit, and the trick no longer worked! I found myself stuck for hours trying to get wireless to connect. WEP connected just fine, "no security" wireless was fine, but when the router was in WPA ONLY, WPA2 ONLY or a mixed WPA mode, I was never able to connect...

This got me thinking about the circumstances which led to my first getting wireless to work on my 32bit Lucid install...it was right after going into suspend mode!

Solution:

Sure enough, on my 64bit install I went into suspend mode, came out, and immediately connected via wireless on WPA2! I tested this a few times, and if it did not connect, doing the

sudo rmmod wl
*wait a few seconds*
sudo modprobe wl

trick worked. Let me know if this works out for you!

Hi,
are the timeouts you are getting related to DHCP? I have tested three kernels so far (2.6.32-21, 2.6.32-22 and 2.6.33-02063303_amd64, which is recommended in comment #173 of bug 496093). None of them works for me, and the symptoms are always the same: I can see the SSID, according to syslog the connection to my wlan is established, and then there's the "DHCP transaction took too long, stopping it" and it's over.

I am having the following on-board card (lspci), which uses the ipw2200 driver:

03:05.0 Network controller: Intel Corporation PRO/Wireless 2915ABG [Calexico2] Network Connection (rev 05)

See also my comment #182 in 496093.

Does this help to narrow it down?

Thanks to all of you for working on this!

Thomas

When I try with WICD it says "BAD PASSWORD". I assume Network-Manager has the same error since it keeps asking for the password.

Is anyone using the hidden wpa wireless network? Does the suggestion from DodgeV83, reloading the driver helps anyone here?

It doesn't help me at all. Before anyoen asks, I haven't gotten around to compileing wpasupplicant or network manager - I'm in the middle of a reno that's dominating my time right now. Hope to get on it this weekend.

Now that I've had an extra day to mess with this on y 64bit Lucid install, subsequent reboots and multiple trials of going into suspend mode has had no effect on my ability to connect to a WPA connection.

Every-single-time I have tried connecting to a local non-secured wireless station, I have been able to switch back to my WPA router and connect successfully.

I'm using a Dell Studio XPS 13 (m1340) with the Broadcom STA drivers.

I have had the same issue since yesterday noon (MDT) on an Acer One. The wireless card is 03:00.0 Ethernet controller: Atheros Communications Inc. AR5001 Wireless Network Adapter (rev 01)

I can access my university's unsecured network, but was thrown out suddenly from our WEP network and now can't connect either to the WEP protected or the WPA/WPA2 protected one. We've checked that I still have access rights and nothing has changed at the sys admin's end. With either password protected network I am repeatedly asked for my key or uname and passwrd, but then nothing happens.

I've gone through my apt log, and I don't see any updates or anything from yesterday at all, so I don't know what could have changed.

I have the same problem on Dell Latitude 5500, Broadcom Corporation BCM4322, Broadcom STA driver, Lucid 64 bit.

I'm using the wl driver with Broadcom Corporation BCM4322. I've had the same problems, with failed association requests, "link timed out", and "WPA: Could not verify EAPOL-Key MIC - dropping packet" messages, etc. I'm happy to report that the problem is now solved for me, after I've upgraded wpasupplicant to 0.6.10. So whatever my problem was, it has been solved in 0.6.10. Since the EAPOL message got me started in the right direction I'm partial to this changelog entry, but I'm just speculating:

        * added a workaround for race condition between receive EAPOL frames
          and association events

For reference, here's more or less what I did to upgrade locally:

# First add source repository if you don't have it
$ sudo apt-get build-dep wpasupplicant
$ cd /tmp
$ sudo apt-get source --compile wpasupplicant
$ wget http://hostap.epitest.fi/releases/wpa_supplicant-0.6.10.tar.gz
$ tar xzvf wpa_supplicant-0.6.10.tar.gz
$ cd wpa_supplicant-0.6.10/wpa_supplicant/
$ cp ../../wpasupplicant-0.6.9/wpa_supplicant/.config .
$ make
$ sudo cp /sbin/wpa_supplicant /sbin/wpa_supplicant.bak
$ sudo cp wpa_supplicant /sbin/

Since there was a wpa_supplicant processes running I then took the coward's way out and rebooted to start with a clean slate. It's been working like a charm after that (I'm using wicd, but hopefully it should work fine with network-manager as well).

yessss, it works. you're a good man, Nils.

just a little issue: with NetworkManager (I don't know with wicd) edit (root perms)

/usr/share/dbus-1/system-services/fi.epitest.hostap.WPASupplicant.service

and remove the "-s" option from the Exec line. Who knows what's the "-s" option of wpa_supplicant? Google doesn't help ...

newly thanks Nils, bye

I'm one of the people with an Intel chip (5100) in a Lenovo x200s. I'm sorry to say that compiling and installing wpa_supplicant 6.10 did not fix the problem. (But thank you also Nils.) I am basically unable to connect to WPA networks. I can usually connect to WEP, but the connection is slow and almost unusable. Following Nils I installed wicd and killed network-manager and nm-applet. That didn't help either. The wicd connection attempts fail with a "bad password" error.

This strikes me as a pretty serious issue.

I installed kernel 2.6.33 (http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.33.3-lucid/ ) to see if it would help. (It helped on one of the ralink driver problems, I think.) There was no change in wifi behavior. I still can't connect in wpa/wpa2, and wep reports connection but is unusable.

Thanks Nils - I did what you said but that just really upset network manager for me. But that gave me an idea, and I ended up pulling in wpasuppicant form Debian Sid (along with libssl0.9.8 and libpcslite1) - that fixed it up for me.

I have been chasing this problem since January. have tried various network manager clients, tried changing drivers for bcm4322 (in a Dell Mini 10v) and nothing worked. The symptom was that it would be very erratic about connecting to the access point. It would take, oh five minutes or so before the connection would come up in knetworkmanager, and then once in a while it would lose it. Sometimes, it would simply never associate (for hours or days) then it would start working again for hours or days. All this with equipment that worked without issues under 9.10, and the access point works fine with other laptops.

Tried Nils' recipe to install 0.6.10 wpa_supplicant, and that broke nm completely until I removed the "-s"
from /usr/share/dbus-1/system-services/fi.epitest.hostap.WPASupplicant.service as suggested by spanna.

Now connects instantaneously afaict. As the problem is intermittent, will continue to test for a week or two, but this does look like it fixes what was wrong.

Thanks to Nils and spanna!

I think this bug should be rated high priority because:
   -- I think this is a very common configuration.
   -- this result is that wireless is "broken" (for anyone using WPA with certain hw.)
   -- while I managed to do this fix, it is pretty involved for most people. I think most people would just give up and switch OS. ( I was close to reverting to 9.10 )

will report back to confirm fixedness.

So far, no issues with me & my Debain Sid ported wpasupplicant & libriaries - worked out of the box, no other work beyond installing the debs was required.

I hope the guys with Intel WiFi chips suffering the same problem try both fixes out and that one of these fixes will help them. If neither of these fixes can help those guys out, then the bug is only partly solved. However I'm in 100% agreement that this should be marked a critical bug.

@nukedathlonman

Can you give some instructions on how you pulled the packages from Debian Sid? I tried to force a downgrade to the Karmic version of libssl0.9.8 (after adding the Karmic repos to my list) and it wanted to remove about half of my programs!

Go to to Debain Packages Organization and manually download (watch your arcitecture - i386 for 32-bit installs, AMD64 for 64-bit installs, etc, etc - do not use ia64 for standard 64bit installes - that specifically for the Intel Itanium CPU & will cause very large problems/headaches) wpasupplicant (here: http://packages.debian.org/sid/wpasupplicant ), libpcsclite1 (here: http://packages.debian.org/sid/libpcsclite1 ) & libssl0.9.8 (here: http://packages.debian.org/sid/libssl0.9.8). Once all three are downloaded, install the two library packages first with kpackagekit (for kubuntu - use gdebi for Ubuntu) then wpasupplicant. When done, reboot & you should have working wireless (post if not).

This worked immediately!

Thanks nukedathlonman!!

WPA is now working for me on both Intel chipsets. It turns out that I was having router problems as well as software problems. I did the wpa_supplicant upgrade along with associated libraries, but also got the router properly reconfigured at about the same time. So I cannot honestly say what did the trick. At any rate, wireless now seems to be working properly. Thanks everyone!

I had the same problem, and nukedathlonman's suggestion worked for me, too.

tried the suggestion in #35 but it still is not working for me..
I have a kohjinsha sx, just glad the wireless card is finally being recognized.

I can confirm this is happening with lucid lynx and a macbook 5.1 with the Broadcom proprietary drivers.
I've tried to follow the instructions in #35 with no luck.
I think this should gather attention, more than a "medium" valued bug.

I can't connect to wpa/wpa2 with my laptop and this is critical, i switched to lucid lynx hoping to fix this problem i was experiencing in Karmic but nothing changed.
Everything is working with open networks, instead

Hope to find a solution,
Thank you, by the way
Da.

Doesn't make any sense...
Well, i messed up things trying to fix this problem, i've been following different directions and one of them was to install a backport module for wireless.
Nothing worked so i decided to remove and then reinstall the broadcom driver, i did it but after that i was totally without wireless since the wl module wouldn't load due to an "unknown symbol" error.
It turned out it was that backport module i've installed to cause this so i removed it.
Then i had wireless back, but the same problem with the wpa stuff.
So i decided to downgrade the wpasupplicant i just upgraded following the #35 comment.
I came back to the wpasupplicant package in the ubuntu repositories.

I couldn't believe that, but when i tried to connect to my wpa protected network it worked immediately.
Now, i'm writing this without having rebooted yet, so...i can't say my problem is completely fixed.
I'll update this if it comes back.

Thanks,
Da.

The solution by nukedathlonman in comment #35 fixed the problem for me, too. Details follow.

Machine: Dell XPS M1330
OS: Ubuntu 10.04 64-bit
Wireless interface:
       product: BCM4312 802.11a/b/g
       vendor: Broadcom Corporation
       version: 01
       width: 32 bits
       clock: 33MHz
       capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
       configuration: broadcast=yes driver=wl0 driverversion=5.60.48.36 latency=0 multicast=yes wireless=IEEE 802.11abg

Sample syslog output:

Jun 6 09:18:06 $machine_name wpa_supplicant[967]: WPS-AP-AVAILABLE
Jun 6 09:18:06 $machine_name NetworkManager: <info> Activation (eth2) starting connection '$ssid'
Jun 6 09:18:06 $machine_name NetworkManager: <info> (eth2): device state change: 3 -> 4 (reason 0)
Jun 6 09:18:06 $machine_name NetworkManager: <info> Activation (eth2) Stage 1 of 5 (Device Prepare) scheduled...
Jun 6 09:18:06 $machine_name NetworkManager: <info> Activation (eth2) Stage 1 of 5 (Device Prepare) started...
Jun 6 09:18:06 $machine_name NetworkManager: <info> Activation (eth2) Stage 2 of 5 (Device Configure) scheduled...
Jun 6 09:18:06 $machine_name NetworkManager: <info> Activation (eth2) Stage 1 of 5 (Device Prepare) complete.
Jun 6 09:18:06 $machine_name NetworkManager: <info> Activation (eth2) Stage 2 of 5 (Device Configure) starting...
Jun 6 09:18:06 $machine_name NetworkManager: <info> (eth2): device state change: 4 -> 5 (reason 0)
Jun 6 09:18:06 $machine_name NetworkManager: <info> Activation (eth2/wireless): access point '$ssid' has security, but secrets are required.
Jun 6 09:18:06 $machine_name NetworkManager: <info> (eth2): device state change: 5 -> 6 (reason 0)
Jun 6 09:18:06 $machine_name NetworkManager: <info> Activation (eth2) Stage 2 of 5 (Device Configure) complete.
Jun 6 09:18:06 $machine_name NetworkManager: <info> Activation (eth2) Stage 1 of 5 (Device Prepare) scheduled...
Jun 6 09:18:06 $machine_name NetworkManager: <info> Activation (eth2) Stage 1 of 5 (Device Prepare) started...
Jun 6 09:18:06 $machine_name NetworkManager: <info> (eth2): device state change: 6 -> 4 (reason 0)
Jun 6 09:18:06 $machine_name NetworkManager: <info> Activation (eth2) Stage 2 of 5 (Device Configure) scheduled...
Jun 6 09:18:06 $machine_name NetworkManager: <info> Activation (eth2) Stage 1 of 5 (Device Prepare) complete.
Jun 6 09:18:06 $machine_name NetworkManager: <info> Activation (eth2) Stage 2 of 5 (Device Configure) starting...
Jun 6 09:18:06 $machine_name NetworkManager: <info> (eth2): device state change: 4 -> 5 (reason 0)
Jun 6 09:18:06 $machine_name NetworkManager: <info> Activation (eth2/wireless): connection '$ssid' has security, and secrets exist. No new secrets needed.
Jun 6 09:18:06 $machine_name NetworkManager: <info> Config: added 'ssid' value '$ssid'
Jun 6 09:18:06 $machine_name NetworkManager: <info> Config: added 'scan_ssid' value '1'
Jun 6 09:18:06 $machine_name NetworkManager: <info> Config: added 'key_mgmt' value 'WPA-PSK'
Jun 6 09:18:06 $machine_name NetworkManager: <info> Config: added 'psk' value '<omitted>'
Jun 6 09:18:06 $machine_name NetworkManager: nm_setting_802_1x_get_pkcs11...

sounds like lucid-backports / lucid-updates might need to consider adding wpasupplicant 0.6.10 and the accompanying packages mentioned in #35 ?

fwiw, I note that maverick is currently shipping wpasupplicant 0.6.9-3ubuntu3 which is identical to the lucid version

https://launchpad.net/ubuntu/maverick/i386/wpasupplicant

I'm getting a very similar-sounding bug with bcm4306 wireless, using the b43 driver. The above fix does not work for me. With wicd I get "Bad password", with nm-applet, I get the stuff attached. Unfortunately, I haven't had a chance to check other networks, this bug has only appeared in the last 24 hours for me.

Confirmed same problem here, #35 didn't fix it though.

The strange bit is that it works on some AP's and not on others. Both using WPA2. The difference being that the one that's not working is a sonicwall box with 802.11n and the working one is a thomson router with 802.11g.

Can someone PLEASE make this a high importance bug?

Details of my machine are below:

Linux him 2.6.32-22-generic #36-Ubuntu SMP Thu Jun 3 19:31:57 UTC 2010 x86_64 GNU/Linux

  *-network
       description: Wireless interface
       product: BCM4322 802.11a/b/g/n Wireless LAN Controller
       vendor: Broadcom Corporation
       physical id: 0
       bus info: pci@0000:09:00.0
       logical name: eth1
       version: 01
       serial: 00:21:00:AA:BB:CC
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
       configuration: broadcast=yes driver=wl0 driverversion=5.60.48.36 latency=0 multicast=yes wireless=IEEE 802.11abgn
       resources: irq:17 memory:d3100000-d3103fff

and /var/log/syslog shows this.
Jun 9 16:14:06 him NetworkManager: <info> Activation (eth1) starting connection 'Auto nothere'
Jun 9 16:14:06 him NetworkManager: <info> (eth1): device state change: 3 -> 4 (reason 0)
Jun 9 16:14:06 him NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled...
Jun 9 16:14:06 him NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) started...
Jun 9 16:14:06 him NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) scheduled...
Jun 9 16:14:06 him NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) complete.
Jun 9 16:14:06 him NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) starting...
Jun 9 16:14:06 him NetworkManager: <info> (eth1): device state change: 4 -> 5 (reason 0)
Jun 9 16:14:06 him NetworkManager: <info> Activation (eth1/wireless): access point 'Auto nothere' has security, but secrets are required.
Jun 9 16:14:06 him NetworkManager: <info> (eth1): device state change: 5 -> 6 (reason 0)
Jun 9 16:14:06 him NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) complete.
Jun 9 16:14:09 him NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled...
Jun 9 16:14:09 him NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) started...
Jun 9 16:14:09 him NetworkManager: <info> (eth1): device state change: 6 -> 4 (reason 0)
Jun 9 16:14:09 him NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) scheduled...
Jun 9 16:14:09 him NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) complete.
Jun 9 16:14:09 him NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) starting...
Jun 9 16:14:09 him NetworkManager: <info> (eth1): device state change: 4 -> 5 (reason 0)
Jun 9 16:14:09 him NetworkManager: <info> Activation (eth1/wireless): connection 'Auto nothere' has security, and secrets exist. No new secrets needed.
Jun 9 16:14:09 him NetworkManager: <info> Config: added 'ssid' value 'nothere'
Jun 9 16:14:09 him NetworkManager: <info> Config:...

Just wanted to add that I was able to connect to any network (wpa/wep/unsecure) on all three b/g/n while on Karmic. Lucid ruined this pleasure :(

Since this looks like a regression (it was working in a previous release) doesn't that qualify as a valid reason to raise the importance of the bug?

Thanks

Well, I'm not a developer here so I can't bump the severity. When I attempted to compile wpasupplicant and replace the packed one, I couldn't connect to any network - after fighting for an hour, I just got lazy and did the port from sid (and that did work for me & at least a few others)... I'm looking at the logs, and it's for sure wpasupplicant and the wl driver competeing with eachother causing the wpa connection failures. But why, I don't know... I'm still trying to figure that out.

For configurations, who's using what encryption protocalls? My router is set to use AES only encryption, and the other routers I connect to are WEP (don't ask, I don't configure peoples networks, I just use when needed). Might present problems if your router/access point can use both tkip and AES, and might cause more bugs with the router/access point can also do both WPA & WPA2 at the same time.

Mine is working on a different AP, so perhaps it isn't related to this. Happy to run any solid debugging process to test though...

nukedathlonman's fix #35 to install the debian packages works for me. FYI I have Broadcom 4312 rev 2. I also recently updated from 9.10 to 10.04. WPA became unbearable. Now works every time.

I'll confirm that fix #35 works. I used the fix a couple of weeks ago and worked flawlessly. The latest kernel update broke it this morning, and by reinstalling the fix#35 again worked like a charm. I have an e-machine E525 with BCM4312 rev01 wireless card.

I have this problem also.
Gonna try the newer packages from Debian Sid & report back.

Hey dev's! Up the priority please! This has been broken over two major releases now!

Ok the Sid packages install with out pain.
Working fine now.

Hi,

I tried to follow #35 but the libssl won't install. I've selected the AMD version for my 10.04 on a macbook pro 4,1:

gdebi started from the command line gives this:

Reading package lists... Done
Building dependency tree
Reading state information... Done
Building data structures... Done
  Traceback (most recent call last):
  File "/usr/bin/gdebi", line 83, in <module>
    if not debi.open(args[0]):
  File "/usr/lib/python2.6/dist-packages/GDebi/GDebiCli.py", line 86, in open
    if not self._deb.checkDeb():
  File "/usr/lib/python2.6/dist-packages/GDebi/DebPackage.py", line 368, in checkDeb
    if not self.checkBreaksExistingPackages():
  File "/usr/lib/python2.6/dist-packages/GDebi/DebPackage.py", line 283, in checkBreaksExistingPackages
    'depversion' : dep.version}
TypeError: not enough arguments for format string

Does anybody have a solution or suggestion?

uh.. dude.. newer mac's use Intel chips... that would be i386
older mac's use PowerPC chips...

Newer macs (and this one) have an intel core2 duo, which is 64 bits and should use the AMD packages.

Good luck with that...

Further on #56: I've managed to install with dpkg instead of gdebi. Don't understand why, but it works.

But: I still have an instable situation with the wpa_supplicant: it looses connection and reconnects, very irregularly! And now and then it pops up the window again with all the settings where you have to click on the 'connect' to make it try once more.

This is really not workable!

I have now have the 2.6.32-23 kernel, libssl0.9.8o-1 and the wpa_supplicant 0.6.10-2.

what a shame.
same problem with UNE 10.04 and desktop 10.10 with the latest kernel
atheros card.

wen i try RT28xx and RT73usb i can see the AP but not conect.

I have this same problem with UNE 10.04 HP mini 5102 with Broadcom STA driver.

I did has instructed in #35 and tested with 10 reboot and it worked fine after each test
(well, Networkmanager is much slower with establishing connection than Windows or OS X, but that's another issue).

Afaik, HP mini 5102 is quite popular notepad, so this should be fixed asap.

Hi,

I have a same problem with NetworkManager i.e. when I try connecting to wireless network, it accepts password but after a while it repeats the question(endlessly). I tried MSI Wind U100 with Ubuntu 9.10 and 10.04. Wireless router is Linksys Wrt54gl(original firmware) and network I am trying to connect to is hidden.
One time on Ubuntu 9.10 I removed NetworkManager completely and configured wireless interface via /etc/network/interfaces with wpa-* and it worked with any problems for a long time.
Today I tried NetworkManager on Ubuntu 9.10(fresh install) with no luck. However I reconfigured wireless router to broadcast SSID of my network(make it visible) and then NM connected me with no problems at all !
Now I am wondering what happens if I make my network hidden again and alter /etc/network/interfaces file i.e. add wpa-ap-scan & wpa-scan-ssid. Will it stop NM from working properly ? Or should editing /etc/wpa_supplicant/wpa_supplicant.conf be a better idea ?

Same symptoms for me Asus eee901 with rt2860sta module, trying to connect to a WPA2 Personal network. It had worked fine in Ubuntu 9.10 and is unusable in 10.4, it occasionally connects but never for more than a few minutes, then just keeps endlessly re-prompting for the password.

I tried replacing wpasupplicant as suggested in comment #35, this didn't work for me.

I also added a new kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.33.3-lucid/ based on a tip from http://ubuntuforums.org/showthread.php?t=1476007, this has so far been working for me. I've kept the updated wpasupplicant packages also (http://packages.debian.org/sid/wpasupplicant, http://packages.debian.org/sid/libpcsclite1, http://packages.debian.org/sid/libssl0.9.8), not sure if those are strictly necessary.

I have this problem now having upgraded from Lucid to Maverick latest updates stream, when connecting to the same network that worked in Lucid

Hi, I've got a Thinkpad X200 with Intel WiFi 5300 and got the same problem, though I not only can not connect to WPA/WPA2 networks but also not to WEP networks. I've tried the above updates of wpasupplicant, but they didn't fix anything.

Dell Latitude E6510
Ubuntu10.04 64bit
Broadcom Restricted Drivers

Followed method in post #27, seems to be working :)

Question: Should Synaptic show the new version of wpa_supplicant? Mine still reads what shipped (.9.3- I believe).

Will have to reboot/switch networks, etc. to be sure it's working...

ANOTHER HINT: I kept getting "text file busy" on last step...after you've backed up your current wpa_supplicant, I had to remove the file to copy the new one in...don't know if anyone else had that problem.

Thanks!

further on #58:

I now have a NEW macbook pro i5 (15") (MBP6,2). Installed 10.04 on it (uptodate).
Wireless still bails out every now and then, but less often than before (now several times per hour).
(I never physically move my laptop during these operations).

1) On a DELL laptop with Xubuntu 10.04 installed the wireless network roaming was no problem (same WPA2 wireless network).
2) On my (this) new MBP6,2 wireless works on Mac OSX, but I keep having these problems under Ubuntu 10.04.
3) At home I use this mbp6,2 with a wpa (not 2) secured network and there are no problems there.

Conclusion: it is SPECIFICALLY this Broadcom 'restricted' driver with THIS macbook hardware on a wireless WPA2 network.

The messages I reported above (#58 and lower) on my mbp4,1 are the same on the mbp6,2.

hi, i've a lenovo n500. with an intel wlan when i installed ubuntu 10.04 everything went ewell, except the wlan. i had the same problem with 9.10 but i solved it installing some restricted drivers. b43-fwcutter and another one, Now, i have problems with, bcmwl-kernel-source, i reintalled it for every way but i just dont wanna work and an error window says that happened a problem number 6. does anybody have the same problem? any ideas??? thanks, bye

Adding Debian sid packages for wpa-supplicant, etc from comment #35 worked me on a Dell M1330 Lucid 64-bit. Strangely the Network Manager notifier shows no connection but browsing works fine.

How can this possibly be of only Medium importance? It is a regression which means that some people cannot connect to Wireless networks!

I have to agree with Warwick. This is a show stopper as it means you can't run Ubuntu on the particular hardware. In my situation I have an Intel 855GME. Wireless works fine on OpenSuse 11.3 (my work around). Forgive my limited understanding but I thought the different vendors shared the same kernel and drivers? Considering that the problem appears to be limited to specific wireless hardware, the hardware in question is Intel (who I believe are great open source contributors?) and other Linux vendors (OpenSuse) don't exhibit the same problem with the same hardware, it's difficult for me as a niave user to understand why the problem persists. AND this is a LTS release. Surely this problem warrants a high severity?

Running Macbook 5,1, had the same issues as planctus, performed #41 (marked wpasupplicant for reinstallation) and WPA works again.

For the full bit:
I reinstalled Ubuntu 10.04.1 to go 64 bit from my previous 32 bit installation which worked fine as far as WPA is concerned. After doing what I did on the 32 bit side, I still couldn't connect to my Airport Extreme router which has WPA enabled. I followed the guide in #35 with no luck, then reinstalled wpasupplicant, with luck.

I also find it very frustrating that this hasn't been fixed yet.

I installed Ubuntu 10.04 to Acer Travelmate 4670 and it has exactly the same problem with wireless network.
After I installed #35 wpasupplicant, libpcsclite1and libssl0.9.8 wireless connection works without problems.

It is hard to recommend Ubuntu for laptop usage, if there is this kind of problems which seem to be relatively easy to fix but are not.

It seems to be fixed in Maveric - I hope that means this will hit the backports for Lucid users.

Hmm, looking back at some of the earlier posts, maybe it's not. :-(

Same problem when connect a wifi with wpa: start to connect, but finish and require the passphrase again...
I tried to configure manually the wpa_supplicant... no success.
I tried to use Wicd... but it uses the wpa_supplicant... no success too.

Using Ubuntu Lucid, I don't have any problems with network-manager...

I tried to use the updates from "ppa:network-manager" for maverick... no success again.

my notebook:
Itautec w7655

lshw -short

WARNING: you should run this program as super-user.
H/W path Device Class Description
==============================================
                       system Computer
/0 bus Motherboard
/0/0 memory 3897MiB System memory
/0/1 processor Intel(R) Core(TM)2 Duo CPU T6600 @ 2.20GHz
/0/100 bridge Mobile 4 Series Chipset Memory Controller Hub
/0/100/2 display Mobile 4 Series Chipset Integrated Graphics Controller
/0/100/2.1 display Mobile 4 Series Chipset Integrated Graphics Controller
/0/100/1a bus 82801I (ICH9 Family) USB UHCI Controller #4
/0/100/1a.1 bus 82801I (ICH9 Family) USB UHCI Controller #5
/0/100/1a.2 bus 82801I (ICH9 Family) USB UHCI Controller #6
/0/100/1a.7 bus 82801I (ICH9 Family) USB2 EHCI Controller #2
/0/100/1b multimedia 82801I (ICH9 Family) HD Audio Controller
/0/100/1c bridge 82801I (ICH9 Family) PCI Express Port 1
/0/100/1c.5 bridge 82801I (ICH9 Family) PCI Express Port 6
/0/100/1c.5/0 eth0 network RTL8111/8168B PCI Express Gigabit Ethernet controller
/0/100/1d bus 82801I (ICH9 Family) USB UHCI Controller #1
/0/100/1d.1 bus 82801I (ICH9 Family) USB UHCI Controller #2
/0/100/1d.2 bus 82801I (ICH9 Family) USB UHCI Controller #3
/0/100/1d.7 bus 82801I (ICH9 Family) USB2 EHCI Controller #1
/0/100/1e bridge 82801 Mobile PCI Bridge
/0/100/1f bridge ICH9M LPC Interface Controller
/0/100/1f.2 storage ICH9M/M-E SATA AHCI Controller
/0/100/1f.3 bus 82801I (ICH9 Family) SMBus Controller
/1 scsi6 storage
/2 wlan0 network Wireless interface

uname -a

Linux rossini-laptop 2.6.35-22-generic #34-Ubuntu SMP Sun Oct 10 09:26:05 UTC 2010 x86_64 GNU/Linux

lsb_release -a

No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 10.10
Release: 10.10
Codename: maverick

Solved for me using kernel 2.6.36... ppa:kernel-ppa.

A Broadband bcm4318 seems to associate more quickly by adding -Dwext to the service file exec line.

/usr/share/dbus-1/system-services/fi.epitest.hostap.WPASupplicant.service

Exec=/sbin/wpa_supplicant -Dwext -u -f /var/log/wpa_supplicant.log

This is suggested at http://wireless.kernel.org/en/users/Drivers/b43, last line but is somewhat misleading.

#35 fix issue in lucid with intel wireless card

macbookpro 5,1.
I try to follow #35 but get this when I try to install libssl0.9.8_0.9.8o-3_i386.deb:
Error: Breaks existing package 'libssl-dev' dependency libssl0.9.8 (= 0.9.8o-1ubuntu4.2)
more info:

dpkg -l |grep libssl
ii libssl-dev 0.9.8o-1ubuntu4.2
ii libssl0.9.8 0.9.8o-1ubuntu4.2

dpkg -l |grep wpas
ii wpasupplicant 0.6.10-2

dpkg -l |grep libpcs
ii libpcsclite1 1.5.5-3

any advice?

This is crazy, and unacceptable. I have just the same, authentication keeps failing. I was working on this for many hours mostly trying simple things and trying to reconnect (at that time not knowing about this bug) and in 3 hours basically of retrying, it accepted authentication but it did not last more than 30 seconds. In addition to the 3 hours, I previously checked in detail the function and settings of the modem router, and the wireless access point. I am not fluent in all this, it is a friends system I help with, and it took a very long time for me to re-learn how to do the checks and test with a third machine.

Detail:
Two identical Lenovo N500 laptops of a friend have suddenly stopped connecting to the wireless access point after working apparently faultlessly for over 6 months.
Ubuntu 10.04, broadcom chip (not sure which just now) B43 (not sta) driver, cutter, DLink wireless access point. WPA2 security, long pass string.

The machines were previously running ok. And ubuntu 9.10 was ok also. When I installed 10.04 on them, I did not make use of a keyring for the password.

The problem started, coincided with a power outage of the modem router for a couple of days, so I guess that the laptops were attempting to connect without success for a while, I do not know if that is relevant, but I thought the connection management responds to what it sees, maybe reconfigures in some way (?) After the power outage was fixed (bad power socket), then no connection with wireless!

My ubuntuforums post before I found this bug entry
http://ubuntuforums.org/showthread.php?t=1739853

These are not my own machines, I am helping a friend, I am not experienced technically with the type of suggestions given in this thread (grateful though) so I cannot do much experimenting without careful preparation (and time), these machines are 'in the wild'.

This is the sharp end of Ubuntu being used instead of Windows by ordinary people, and is what we aspire to. Ubuntu in the wild, 'on a street near you', and suddenly NOT working with wireless! It is making these mobile laptops into wire bound desk machines.

It warrants a *high* priority

typo sorry

"and in 3 hours basically of retrying, it accepted authentication but it did not last more than 30 seconds"

should read

"and in 3 hours basically of retrying, it accepted authentication only ONCE but it did not last more than 30 seconds"

Important news from my situation:
Although the symptoms were as described, I have found the main reason for my problem. Wireless interference from nearby (neighbours) systems! I did a series of experiments including taking all of the (wireless hardware and laptop to my house where I was surprised shocked to find it all worked perfectly straight away. It took me several other time consuming experiments to fail to find a reason for things not working. I am not experienced with basic wifi and the significance of the target location being in the middle of a block of apartments did not emerge for me until much later. A smartphone (Android) app for wireless scan immediately showed a dozen competing signals with useful channels occupied, and several signals were very strong indeed. So strong that even with our wireless access point (WAP) in the same room as the laptop and smartphone, the two competing signals were showing the -same- strength (!) the solution was to set the WAP to partly avoid the competition by using a fixed channel (3) just in between the competition (1) and (6). Not ideal but it works (so far).

The WAP is D-Link DAP 1353 which I think is good kit (?)
The history of wifi working then stopping working I put down to a neighbour or two deciding to increase their own power maybe.