Ubuntu
network-manager package

WPA networks don't always work after suspend

Bug #135219 reported by Maya Shapira
4
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Fix Released
Low
Alexander Sack

Bug Description

After waking up from suspend-to-RAM, if the first available network is WPA encrypted (even though I normally connect to it and the key is in the keyring), NM doesn't successfully connect. Furthermore, the applet does not recognize any wireless networks, and the "Enable Wireless" box doesn't show up, nor do any wireless networks. I can only seem to fix this by rebooting. Attached is a relevant snippet from /var/log/daemon.log

Revision history for this message
Maya Shapira (maya-shapira) wrote :
Revision history for this message
Henrik Nilsen Omma (henrik) wrote :

Hi, was this with Feisty? Do you have a chance to retest with Gutsy? Thanks.

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

this appears to be related to wpasupplicant taking more than two seconds to bring up its ctrl socket. Thus you see:

  <WARNING>^I real_act_stage2_config (): Activation (eth1/wireless): couldn't connect to the supplicant.

... the next major gutsy package update increases this timeout to 12 seconds which appears to fit better. A bzr branch to test is available at https://code.launchpad.net/~asac/network-manager/ubuntu.0.6.x.dev.opennet.

Changed in network-manager:
assignee: nobody → asac
status: Incomplete → Fix Committed
Revision history for this message
Alexander Sack (asac) wrote :

this should be fixed in latest network-manager. If you still see it, please reopen this bug and leave a comment

Changed in network-manager:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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