Wireless failes to reconnect automaticaly after suspend or takes too long to reconnect

Bug #261014 reported by mike hancock
0
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Triaged
High
Unassigned

Bug Description

I am running a dell xps 1330 (pre-installed ubuntu) with Hardy. After a suspend to ram, some times all of the following 3 casses happen

1) network manager does not reconnect to my wifi network at all. network manager says "networking disabled". This case is very uncommon; but it happens some times(like today :( ).

2) network manager connects automatically, but it takes _too_ long to connect; any where from 30 sec to 1.5 min. while waiting it also says "networking disabled" but it eventually it connects.

3) it works as it should and automatically connects

in all of the above cases it works to run
iwconfig essid "networkname"; dhclient eth1

to reconnect, but doing so network manager still shows "networking disabled"(even though it is working!).

Revision history for this message
mike hancock (javaiscoolmike) wrote :

since i have upgraded to intrepid beta, I have not had this problem. well at least not as severely as it was in hardy. now only occasionally it takes more then a few seconds to reconnect. i still sometimes see the "networking disabled" thing but it ends up reconnecting much faster them before.

Changed in dell:
status: New → Invalid
Revision history for this message
Alexander Sack (asac) wrote :

is that iwl drivers? or atheros? we have bug 292054 and bug 263963 ... but the former should fit well i guess.

Changed in network-manager:
importance: Undecided → High
status: New → Triaged
Revision history for this message
Alexander Sack (asac) wrote :

i mark this of a dupe of the workaround bug on network-manager ... but i empasize that this is a driver issue like in the latter bug i mentioned. or with some luck just "wpasupplicant" issue, which i doubt though.

Changed in somerville:
status: New → Invalid
no longer affects: dell
Revision history for this message
Timothy R. Chavez (timrchavez) wrote :

The bug task for the somerville project has been removed by an automated script. This bug has been cloned on that project and is available here: https://bugs.launchpad.net/bugs/1305581

no longer affects: somerville
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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