I tracked down the issue where WiFi would fail after suspend in that it
doesn't associate anymore (tries to connect but fails), and it's a bug
in wpa-supplicant that was fixed in the current version (Ubuntu uses
2.1, newest is 2.3). Replacing Ubuntu's wpa-supplicant 2.1 with Debian's
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: wpasupplicant (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to wpasupplicant in Ubuntu.
Thank you Stefan, your suggestion from comment #4 helped me too on my
Thinkpad T60 with trusty and iwl3945 driver.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to wpasupplicant in Ubuntu.
https://bugs.launchpad.net/bugs/1305857
Title:
I made the change suggested in comment #4 and it works like a dream. I
would like to thank Stefan for helping me work around this annoying bug.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to wpasupplicant in Ubuntu.
A correction about comment #2 : wpa_cli terminate can make the connection
work after the system is woken up. It does however not work at the time sleep.d
is processed. So it seems wpa_cli can't connect to wpa_supplicant at that time.
I have because of that replaced $WPACLI resume with pkill
** Attachment added: syslog excerpt for auth timeout
https://bugs.launchpad.net/ubuntu/+source/wpasupplicant/+bug/1305857/+attachment/4079604/+files/syslog.log
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to wpasupplicant in Ubuntu.
A quick and dirty workaround is changing line 15 of /usr/lib/pm-
utils/sleep.d/60_wpa_supplicant to read
resume|thaw)
$WPACLI terminate
instead of
resume|thaw)
$WPACLI resume
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
One more thing I tried: After wake up, regardless of calling resume or not,
wpa_supplicant is reacting to wpa_cli ping and also does some stuff as can be
seen in the log. So it is probably not stuck but in a wrong internal state.
Additionally, it takes about 30 seconds after authentication until
8 matches
Mail list logo
