wpa_supplicant crashed with SIGSEGV

StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()

Status changed to 'Confirmed' because the bug affects multiple users.

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:

* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?

This will help us to find and resolve the problem.

Hi,

Not in my case. It has only happened once.

On 2013-10-21 14:52, Alberto Salvia Novella wrote:
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. Please answer these questions:
>
> * Is this reproducible?
> * If so, what specific steps should we take to recreate this bug?
>
> This will help us to find and resolve the problem.
>
> ** Changed in: wpa (Ubuntu)
> Status: Confirmed => Incomplete
>
> ** Attachment removed: "CoreDump.gz"
> https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1210785/+attachment/3767047/+files/CoreDump.gz
>
> ** Information type changed from Private to Public
>

If you know what specific steps will recreate this flaw, please write them into the bug description.

Thank you.

Thi s flaw has only occured for me when applications are left open and a restart is done, it occurs with many other errors as well.

Steps to reproduce: wake up laptop from sleep. This crash occurs every second time for each wakeup. Crash might be timing related and probably something to do with timing of the interface takedown sequence.

It happens for me as well when my laptop comes back from suspend. I've an Asus S56CA-WH31. Only started having this problem after my upgrade to 13.10 (I was on 13.04 before). I've sent at least one bug report via the ubuntu bug notifier app so you should have that info as well.

I had this crash also after a reboot of the same laptop as previously reported (laptop is Acer Aspire 5750). Here is the syslog of the part where it is going to suspend and crashes:

Oct 21 23:44:14 elrond NetworkManager[789]: <info> sleep requested (sleeping: no enabled: yes)
Oct 21 23:44:14 elrond NetworkManager[789]: <info> sleeping or disabling...
Oct 21 23:44:14 elrond NetworkManager[789]: <info> (eth0): device state change: unavailable -> unmanaged (reason 'sleeping') [20 10 37]
Oct 21 23:44:14 elrond NetworkManager[789]: <info> (eth0): cleaning up...
Oct 21 23:44:14 elrond NetworkManager[789]: <info> (eth0): taking down device.
Oct 21 23:44:14 elrond kernel: [129974.141273] tg3 0000:02:00.0: System wakeup enabled by ACPI
Oct 21 23:44:14 elrond NetworkManager[789]: <info> (wlan0): device state change: activated -> unmanaged (reason 'sleeping') [100 10 37]
Oct 21 23:44:14 elrond NetworkManager[789]: <info> (wlan0): deactivating device (reason 'sleeping') [37]
Oct 21 23:44:14 elrond whoopsie[993]: offline
Oct 21 23:44:14 elrond NetworkManager[789]: <info> (wlan0): canceled DHCP transaction, DHCP client pid 7414
Oct 21 23:44:14 elrond avahi-daemon[781]: Withdrawing address record for fe80::3a59:f9ff:feaf:73f2 on wlan0.
Oct 21 23:44:14 elrond avahi-daemon[781]: Leaving mDNS multicast group on interface wlan0.IPv6 with address fe80::3a59:f9ff:feaf:73f2.
Oct 21 23:44:14 elrond avahi-daemon[781]: Interface wlan0.IPv6 no longer relevant for mDNS.
Oct 21 23:44:14 elrond kernel: [129974.358733] wlan0: deauthenticating from 00:25:9c:41:a0:db by local choice (reason=3)
Oct 21 23:44:14 elrond wpa_supplicant[20620]: wlan0: CTRL-EVENT-DISCONNECTED bssid=00:00:00:00:00:00 reason=3
Oct 21 23:44:14 elrond kernel: [129974.366737] cfg80211: Calling CRDA to update world regulatory domain
Oct 21 23:44:14 elrond avahi-daemon[781]: Withdrawing address record for 192.168.200.142 on wlan0.
Oct 21 23:44:14 elrond avahi-daemon[781]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.200.142.
Oct 21 23:44:14 elrond avahi-daemon[781]: Interface wlan0.IPv4 no longer relevant for mDNS.
Oct 21 23:44:14 elrond NetworkManager[789]: <warn> DNS: plugin dnsmasq update failed
Oct 21 23:44:14 elrond NetworkManager[789]: <info> Removing DNS information from /sbin/resolvconf
Oct 21 23:44:14 elrond dnsmasq[1084]: setting upstream servers from DBus
Oct 21 23:44:14 elrond kernel: [129974.371681] cfg80211: World regulatory domain updated:
Oct 21 23:44:14 elrond kernel: [129974.371690] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Oct 21 23:44:14 elrond kernel: [129974.371696] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Oct 21 23:44:14 elrond kernel: [129974.371701] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Oct 21 23:44:14 elrond kernel: [129974.371706] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Oct 21 23:44:14 elrond kernel: [129974.371710] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Oct 21 23:44:14 elrond kernel: [129974.371714] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Oct 21 2...

It is possible that this problem is timing sensitive. I had about 5 suspend-wakeup cycles without a crash. After that it again started to crash. I think it may be caused by the fact that everything was cached to memory (this system has 8 GB ram and normally light usage). It is possible that this is harder to reproduce with systems which are capable of faster suspends. Just a guess: try the suspend with HDD, not SSD.

I used to have the same problem. Now it seems to have gone.

3.11.0-12-generic #19-Ubuntu SMP Wed Oct 9 16:12:00 UTC 2013 i686 i686 i686 GNU/Linux
Something must have been fixed.

By the way, I am using R835-P94.

It happens to me all of the time:

Linux me-Aspire-5745PG 3.11.0-12-generic #19-Ubuntu SMP Wed Oct 9 16:20:46 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

please refrain from "me too" type comments. I think what this bug needs is a reliable way to recreate the issue

Same here... after laptop wakes from sleep wifi doesnt work anymore.. wpa_supplicant crash Lenovo G570

It happens everytime on Lenovo U330P. What can I do to report more trace?

It happens on Asus P50IJ too, sometimes after only one "wake up" since the last restart, sometimes after 2 or 3 "wake ups". Is it possible posting more trace?

same crash, xubuntu 13.10 64 bit, fresh install.
it happens at boot time but then it seems to work.
never used sleep/suspend.
driver rtl8192cu and hidden ssid

Network controller: Qualcomm Atheros AR93xx Wireless Network Adapter (rev 01) - using ath9k wifi driver.

On my Chromebook (Samsung CR-48), this seems to happen in the running system (not from suspend). Ubuntu 13.10.

From my error log (does anybody know how I can get debugging symbols for wpa_supplicant?):

Disassembly:
 => 0x8102980: mov (%edi),%ebx
    0x8102982: je 0x810291b
    0x8102984: mov %esi,0x20(%esp)
    0x8102988: mov %eax,%esi
    0x810298a: mov %ebp,0x1c(%esp)
    0x810298e: mov %edi,%ebp
    0x8102990: mov 0x94(%esp),%edi
    0x8102997: jmp 0x81029b3
    0x8102999: lea 0x0(%esi,%eiz,1),%esi
    0x81029a0: add $0x1,%esi
    0x81029a3: mov (%ebx),%eax
    0x81029a5: cmp %ebx,0x1c(%esp)
    0x81029a9: je 0x810291b
    0x81029af: mov %ebx,%ebp
    0x81029b1: mov %eax,%ebx
    0x81029b3: cmp 0x7c(%ebp),%edi
InstallationDate: Installed on 2011-04-28 (921 days ago)
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
MarkForUpload: True
Package: wpasupplicant 1.0-3ubuntu2
PackageArchitecture: i386
Registers:
 eax 0x0 0
 ecx 0x0 0
 edx 0x7fa55c32 2141543474
 ebx 0x8835620 142824992
 esp 0x7fa55bd0 0x7fa55bd0
 ebp 0x8831e78 0x8831e78
 esi 0x8831e70 142810736
 edi 0xd089089 218665097
 eip 0x8102980 0x8102980
 eflags 0x210293 [ CF AF SF IF RF ID ]
 cs 0x73 115
InstallationDate: Installed on 2011-04-28 (921 days ago)
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
MarkForUpload: True
Package: wpasupplicant 1.0-3ubuntu2
PackageArchitecture: i386
Registers:
 eax 0x0 0
PackageArchitecture: i386
Registers:
 eax 0x0 0
 ecx 0x0 0
 edx 0x7fa55c32 2141543474
 ebx 0x8835620 142824992
 esp 0x7fa55bd0 0x7fa55bd0
 ebp 0x8831e78 0x8831e78
 esi 0x8831e70 142810736
 edi 0xd089089 218665097
 eip 0x8102980 0x8102980
 eflags 0x210293 [ CF AF SF IF RF ID ]
 cs 0x73 115
 ss 0x7b 123
 ds 0x7b 123
 es 0x7b 123
 fs 0x0 0
 gs 0x33 51
SegvAnalysis:
 Segfault happened at: 0x8102980: mov (%edi),%ebx
 PC (0x08102980) ok
 source "(%edi)" (0x0d089089) not located in a known VMA region (needed readable region)!
 destination "%ebx" ok
SegvReason: reading unknown VMA
SourcePackage: wpa
Stacktrace:
 #0 0x08102980 in ?? ()
 No symbol table info available.
 #1 0x08059965 in ?? ()
 No symbol table info available.
 #2 0x0807bdc9 in ?? ()
 No symbol table info available.
 #3 0x08074039 in ?? ()
 No symbol table info available.
 #4 0x0812482a in ?? ()
 No symbol table info available.
 #5 0x08136847 in ?? ()
 No symbol table info available.
 #6 0x77727f3b in nl_recvmsgs_report () from /lib/i386-linux-gnu/libnl-3.so.200
 No symbol table info available.
 #7 0x777282c3 in nl_recvmsgs () from /lib/i386-linux-gnu/libnl-3.so.200
 No symbol table info available.
 #8 0x0812accd in ?? ()
 No symbol table info available.
 #9 0x0805a900 in ?? ()
 No symbol table info available.
 #10 0x0805af82 in ?? ()
 No symbol table info availabl...

See https://wiki.ubuntu.com/DebuggingProgramCrash#Debug_Symbol_Packages.

Same here with a Asus N53SN laptop(ASUSTeK Computer Inc. N53SN/N53SN, BIOS N53SN.209 01/10/2012)

same crash, xubuntu 13.10 64 bit, fresh install. It happens at every start, but I don't see any effect.

Since reinstalling wpasupplicant via synaptic package manager, the crash report has gone away. I'm no expoert, but although I used to get a crash error every time I booted, the wi-fi worked perfectly normal in every way, so it wasn't really a problem, just an annoyance. However, new users would get worried something was wrong and possible think Ubuntu was defective.

In its current state, there just isn't much we can do with this bug. I had been "fortunate" enough to get a stacktrace previously from one of the duplicates, but it's missing just as much data as what's currently included.

To get this bug in a "usable" state where I can fix the issue (and sorry, I just haven't had luck reproducing it yet), I'd need someone who is able to reproduce the bug easily to try the following:

1) Add my ppa (https://launchpad.net/~mathieu-tl/+archive/sru-staging?field.series_filter=saucy):
sudo add-apt-repository ppa:mathieu-tl/sru-staging

Note, it will take a few hours for the wpasupplicant packages to build. The only change is to add a package with debugging symbols so we can figure out what is going on.

2) install the debug packages and the wpasupplicant with extra debugging package from my PPA:

sudo apt-get install libc6-dbg
sudo apt-get install wpasupplicant-dbg wpasupplicant

3) Delete any files named wpasupplicant* from /var/crash (to make sure we get to see what happens)

4) Reboot (important! we need to make sure the new wpasupplicant gets used)

5) Reproduce the issue.

Once wpasupplicant crashes you should see it creates a file in /var/crash with its name: wpasupplicant.0.crash or something similar. Please send me this file via email at mathieu (at) canonical.com , make sure the subject is something meaningful.

I won't need five of them, just one is necessary, so please only do this if you feel confident I could answer you and ask for a bit more tinkering, like installing another debug package for libnl, if it comes to it.

Thanks!

I received the necessary data from Stéphane Delprat, I expect to have a patch to test soon.

This bug was fixed in the package wpa - 1.0-3ubuntu4

---------------
wpa (1.0-3ubuntu4) trusty; urgency=low

  * debian/patches/git_deinit_p2p_context_on_mgmt_remove_ff1f9c8.patch:
    deinitialize the P2P context when the management interface gets removed for
    whatever reason, such as a suspend/resume cycle. (LP: #1210785)
 -- Mathieu Trudel-Lapierre <email address hidden> Mon, 18 Nov 2013 20:31:00 -0500

Gracias amigos, desapareció el error reportado. Trabaja de maravilla

Launchpad Bug Tracker <email address hidden> escribió:

>This bug was fixed in the package wpa - 1.0-3ubuntu4
>
>---------------
>wpa (1.0-3ubuntu4) trusty; urgency=low
>
> * debian/patches/git_deinit_p2p_context_on_mgmt_remove_ff1f9c8.patch:
> deinitialize the P2P context when the management interface gets removed for
> whatever reason, such as a suspend/resume cycle. (LP: #1210785)
> -- Mathieu Trudel-Lapierre <email address hidden> Mon, 18 Nov 2013 20:31:00 -0500
>
>** Changed in: wpa (Ubuntu)
> Status: In Progress => Fix Released
>
>--
>You received this bug notification because you are subscribed to a
>duplicate bug report (1237190).
>https://bugs.launchpad.net/bugs/1210785
>
>Title:
> wpa_supplicant crashed with SIGSEGV
>
>Status in “wpa” package in Ubuntu:
> Fix Released
>Status in “wpa” source package in Saucy:
> In Progress
>
>Bug description:
> [Impact]
> Any user of wpasupplicant, provided they have hardware that reports supporting P2P, possibly others as well. This is timing related in how wpasupplicant handles management interface changes (usually from request of another process, such as NetworkManager).
>
> [Regression potential]
> This fixes a known issue in the logic handling the p2p (wpa) context in wpasupplicant, specifically for P2P, so not expected to actually break things for a lot of people, given that P2P, although enabled, is not currently supported by NetworkManager or any other way except with manual configuration of wpasupplicant.
> If anything, what would be likely to break is tracking of the context for a p2p supplicant: in other words, it could be possible for the context (the way for the supplicant to get to the control interface, and as such possibly log information or errors) for the p2p supplicant (the supplicant process specifically for Wifi P2P support, which is somewhat separate from the standard wifi process) to be lost as the management interface changes due to command line requests, suspend/resume cycle, etc. causing a change in the available interfaces. I hope this is somewhat clear-ish ;)
>
> [Test Case]
> 1) remove wpa crash files from /var/crash:
> rm -f /var/crash/_sbin_wpa*
>
> 2) Suspend/resume repeatedly until the supplicant crashes.
>
> Without the patch, you should see an apport dialog pop up after a few cycles (possibly within 10 cycles?)
> With the patch, the supplicant should not crash.
>
> ----
>
> wpa_supplicant crashed with SIGSEGV
>
> ProblemType: Crash
> DistroRelease: Ubuntu 13.10
> Package: wpasupplicant 1.0-3ubuntu2
> ProcVersionSignature: Ubuntu 3.11.0-1.4-generic 3.11.0-rc4
> Uname: Linux 3.11.0-1-generic i686
> ApportVersion: 2.12-0ubuntu3
> Architecture: i386
> CrashCounter: 1
> Date: Sat Aug 10 16:58:28 2013
> ExecutablePath: /sbin/wpa_supplicant
> InstallationDate: Installed on 2013-08-06 (4 days ago)
> InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130730)
> MarkForUpload: True
> ProcCmdline: /sbin/wpa_supplicant -B -P /run/sendsigs.omit.d/wpasupplicant.pid -u -s -O /var/run/wpa_supplicant
> ProcEnviron:
>
> SegvAnalysis:
>  Segfa...

Gracias amigos, desapareció el error reportado. Trabaja de maravilla

Mathieu Trudel-Lapierre <email address hidden> escribió:

>** Also affects: wpa (Ubuntu Saucy)
> Importance: Undecided
> Status: New
>
>** Changed in: wpa (Ubuntu Saucy)
> Importance: Undecided => High
>
>** Changed in: wpa (Ubuntu Saucy)
> Status: New => In Progress
>
>** Changed in: wpa (Ubuntu Saucy)
> Assignee: (unassigned) => Mathieu Trudel-Lapierre (mathieu-tl)
>
>--
>You received this bug notification because you are subscribed to a
>duplicate bug report (1237190).
>https://bugs.launchpad.net/bugs/1210785
>
>Title:
> wpa_supplicant crashed with SIGSEGV
>
>Status in “wpa” package in Ubuntu:
> In Progress
>Status in “wpa” source package in Saucy:
> In Progress
>
>Bug description:
> wpa_supplicant crashed with SIGSEGV
>
> ProblemType: Crash
> DistroRelease: Ubuntu 13.10
> Package: wpasupplicant 1.0-3ubuntu2
> ProcVersionSignature: Ubuntu 3.11.0-1.4-generic 3.11.0-rc4
> Uname: Linux 3.11.0-1-generic i686
> ApportVersion: 2.12-0ubuntu3
> Architecture: i386
> CrashCounter: 1
> Date: Sat Aug 10 16:58:28 2013
> ExecutablePath: /sbin/wpa_supplicant
> InstallationDate: Installed on 2013-08-06 (4 days ago)
> InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130730)
> MarkForUpload: True
> ProcCmdline: /sbin/wpa_supplicant -B -P /run/sendsigs.omit.d/wpasupplicant.pid -u -s -O /var/run/wpa_supplicant
> ProcEnviron:
>
> SegvAnalysis:
> Segfault happened at: 0x81028d0: mov 0x4(%esi),%edx
> PC (0x081028d0) ok
> source "0x4(%esi)" (0x0000012d) not located in a known VMA region (needed readable region)!
> destination "%edx" ok
> SegvReason: reading NULL VMA
> Signal: 11
> SourcePackage: wpa
> StacktraceTop:
> ?? ()
> ?? ()
> ?? ()
> ?? ()
> ?? ()
> Title: wpa_supplicant crashed with SIGSEGV
> UpgradeStatus: No upgrade log present (probably fresh install)
> UserGroups:
>
>To manage notifications about this bug go to:
>https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1210785/+subscriptions

¿How can i download the fix?

The fix is currently in Trusty, which means it's not directly accessible to Saucy. Within a few days, the fix should be in the -proposed repository.

Also, shouldn't ~ubuntu-sru be subscribed?

Yes, they should be for the SRU process. I stopped temporarily because I had reports of a possible regression, which needs to be investigated.

In the meantime, you can try with the packages at https://launchpad.net/~mathieu-tl/+archive/sru-staging .

wpa 1.0-3ubuntu2.1~mtrudel1 contains the patch uploaded to Trusty along with some extra debugging packages for use if this doesn't fix the crashes, so I can get a stacktrace.

this tutorial can fix the problem, for those who can't waith for the fix in sausy-13.10 64 bit, i did it exactly, read completly:

download the package file attached to this comment, it contains the fix from trusty wpa 1.0-3ubuntu4, and network-manager-gnome becouse we need to unistall it to fix the problem.

with synaptic unistall wpa-supplicant completly
with synaptic unistall network-manager-gnome, just uninstall, if it was allready uninstalled it's fine.

you will get without internet.

reboot your system,

install the deb files in the package simply with ubuntu software center in this order:

wpasupplicant_1.0-3ubuntu4_amd64
hostapd_1.0-3ubuntu4_amd64
wpagui_1.0-3ubuntu4_amd64
network-manager_0.9.8.0-0ubuntu22_amd64
network-manager-gnome_0.9.8.0-1ubuntu5_amd64

reboot your system again,

and this is it, the fix is done, and the internet comes back without afecting the wifi passwords.

PD: when i tried to install the fix from trusty without uninstall network-manager-gnome, that didn't fix the problem.

You shouldn't have to uninstall the packages only to reinstall them later, nor do you have to download the deb files manually as Mathieu providing a PPA.

The steps should just be as follows (in Terminal):
sudo add-apt-repository ppa:mathieu-tl/sru-staging
sudo apt-get update
sudo apt-get dist-upgrade
Reboot your system.

Also, I installed the PPA packages, and there is still at least one crash happening on startup for me. Is this a different error?

#0 0x00000000004b1795 in wpa_supplicant_ctrl_iface_msg_cb (ctx=0x1386910,
    level=2, txt=0x138f0a0 "P2P: Update channel list", len=24)
    at ctrl_iface_unix.c:249
#1 0x00000000004148c9 in wpa_msg (ctx=0x1386910, level=2, fmt=<optimized out>)
    at ../src/utils/wpa_debug.c:455
#2 0x0000000000433f07 in p2p_update_channel_list (p2p=0x1386910,
    chan=0x7fff42f76300) at ../src/p2p/p2p.c:3800
#3 0x000000000042cac2 in wpas_p2p_update_channel_list (wpa_s=0x13adba0)
    at p2p_supplicant.c:4294
#4 0x00000000004d0891 in wpa_supplicant_event (ctx=0x13adba0,
    event=EVENT_CHANNEL_LIST_CHANGED, data=0x0) at events.c:2414
#5 0x00000000004e1409 in memcpy (__len=6, __src=<optimized out>,
    __dest=0x1381b5e) at /usr/include/x86_64-linux-gnu/bits/string3.h:51
#6 mlme_event_join_ibss (tb=0x7fff42f76770, drv=0x1381aa0)
    at ../src/drivers/driver_nl80211.c:1216
#7 process_event (msg=<optimized out>, arg=0x1381aa0)
    at ../src/drivers/driver_nl80211.c:1817
#8 0x00007fc5a6cc19fa in nl_recvmsgs_report ()
   from /lib/x86_64-linux-gnu/libnl-3.so.200
#9 0x00007fc5a6cc1d79 in nl_recvmsgs ()
   from /lib/x86_64-linux-gnu/libnl-3.so.200
#10 0x00000000004d665c in wpa_driver_nl80211_event_receive (
    sock=<optimized out>, eloop_ctx=0x1381aa0, handle=0x13a5a50)
---Type <return> to continue, or q <return> to quit---
    at ../src/drivers/driver_nl80211.c:1868
#11 0x0000000000415964 in eloop_sock_table_dispatch (
    table=table@entry=0x760508 <eloop+8>, fds=fds@entry=0x1386720)
    at ../src/utils/eloop.c:216
#12 0x000000000041603e in eloop_run () at ../src/utils/eloop.c:562
#13 0x00000000004cce99 in wpa_supplicant_run (global=0x1386910)
    at wpa_supplicant.c:2714
#14 0x0000000000000000 in ?? ()

why don't you try to uninstall network-manager-gnome before installing the ppa, then reinstall the ppa, finally install network-manager-gnome, the same as you happened to me first time, afterward, i did the large way i explain up there, maybe you can do it shorter/uncomplicated, i have two days without signs of this problem.

Saikrishna, that looks like the same error again. It probably happens on shutdown with the old wpasupplicant, so I'd remove the files from wpasupplicant from /var/crash and reboot a few more times to make sure ;)

Hello rolmops, or anyone else affected,

Accepted wpa into saucy-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/wpa/1.0-3ubuntu2.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

verification-done

lsb_release -rd
Description: Ubuntu 13.10
Release: 13.10

apt-cache policy wpasupplicant
wpasupplicant:
  Installed: 1.0-3ubuntu2.1
  Candidate: 1.0-3ubuntu2.1
  Version table:
 *** 1.0-3ubuntu2.1 0
        400 http://us.archive.ubuntu.com/ubuntu/ saucy-proposed/main amd64 Packages
        100 /var/lib/dpkg/status
     1.0-3ubuntu2 0
        500 http://us.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages

Thank you guys, it seems to be working fine. It has been running for the last 1-2 days already and I had no errors since install, finally! Thanks again! :)

This bug was fixed in the package wpa - 1.0-3ubuntu2.1

---------------
wpa (1.0-3ubuntu2.1) saucy-proposed; urgency=low

  * debian/patches/git_deinit_p2p_context_on_mgmt_remove_ff1f9c8.patch:
    deinitialize the P2P context when the management interface gets removed for
    whatever reason, such as a suspend/resume cycle. (LP: #1210785)
 -- Mathieu Trudel-Lapierre <email address hidden> Wed, 04 Dec 2013 11:20:38 -0500

The verification of the Stable Release Update for wpa has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions.