[Hardy] Wireless broken with latests updates

Bug #198971 reported by Vytas
34
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Fix Released
High
Unassigned
wpasupplicant (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

After latest updates of March 5th, I cannot connect to any wireless network by using network manager.
I only managed to connect by configuring it manually by using network-admin.

According to the logs, there is some problem while communicating with WPA supplicant.

Package versions:
network-manager 0.6.6~rc2-0ubuntu1
wpasupplicant 0.6.0+0.5.8-0ubuntu1

Revision history for this message
Vytas (vytas) wrote :
Revision history for this message
Vytas (vytas) wrote :
Revision history for this message
Vytas (vytas) wrote :
Revision history for this message
vlowther (victor-lowther) wrote :

I see this error on my system as well. Relavent part of /var/log/daemon.log attached.

Changed in network-manager:
status: New → Confirmed
Revision history for this message
vlowther (victor-lowther) wrote :

nm failing to talk to supplicant. Network is open.

Changed in wpasupplicant:
status: New → Confirmed
Daniel T Chen (crimsun)
Changed in wpasupplicant:
status: Confirmed → Invalid
Changed in network-manager:
status: Confirmed → Fix Released
Revision history for this message
Caroline Ford (secretlondon) wrote :

undecided ->high

Changed in network-manager:
importance: Undecided → High
Revision history for this message
Francois Rigaut (francois.rigaut) wrote :

+1 here. Since March 6 updates (must have been the same than Vytas).
I see exactly the same symptoms (network is listed normally under the nm-applet, but selecting it fails to connect).
My network is open too.
Bugs is present both with 2.6.24-11 and 2.6.24-10.
I'm using an atheros card.

in /var/log/daemon.log:
Mar 8 23:57:30 poliahu NetworkManager: <WARN> nm_utils_supplicant_request_with_check(): nm_supplicant_interface_init: supplicant error for 'INTERFACE_ADD ath0^I^Iwext^I/var/run/wpa_supplicant0^I'. Response: 'FAIL'

Revision history for this message
Vytas (vytas) wrote :

Yes, but for me it was fixed again since I updated to 0.6.6-0ubuntu1.

What version are you using?

Revision history for this message
Nikolaus.x (nikolaus.x) wrote :

I also had this issue. Installed Hardy alpha 6, which OOTB worked fine with my wireless (D-Link 655), however after applying all updates I can no longer connect to it. I can see the signal strength of my AP, but Ubuntu can't connect to it. Just keeps trying and trying. Since it works after Hardy a6 install, and not after the updates, the updates broke something.

Revision history for this message
Francois Rigaut (francois.rigaut) wrote :

@Vytas: no luck. I am using 0.6.6-0ubuntu1 and my wireless still won't connect (I was already using this version when I wrote my previous message).

I also tried directly with the alpha6 liveCD and I get exactly the same problem: my open) network is listed by the nm-applet but the thing will not connect.

I can't come back to an earlier version and 0.6.6-0ubuntu1 is the only one left in the repos (if there's another way to get an earlier version I don't know it).

This seems to me a very serious bug, and I am surprised that other (thinkpad) users are not reporting it.

I am currently doing the latest upgrade (with 2.6.24-12), but I doubt this will solve my problem. I attach the relevant part of daemon.log and lspci in case it could be useful.
Note that I am now at work and this is a closed network, but the problem was also present at home with an open network.

Revision history for this message
Francois Rigaut (francois.rigaut) wrote :
Revision history for this message
Jordan (jordanu) wrote :

I was encountering ( what I think to be at least ) this bug and the most recent network-manager update today seems to have fixed it.

Revision history for this message
Francois Rigaut (francois.rigaut) wrote :

Yes, it did ! Thanks.

Revision history for this message
vladimir prieto (vladimirprieto) wrote :

yeap, i did connect with latest update.

i didn't update since 1 week, so don't know wich one does fix.

Revision history for this message
Robert (robrwo) wrote :

I have the same bug. I can only connect using Network Manager but not wpa_supplicant with ifup/ifdown. Actually, using ifup, I get an error that the interface "eth1=eth1" isn't configured.

Revision history for this message
Robert (robrwo) wrote :

I should add that this is still an issue for me as of 24 March.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.