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
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to wpa in Ubuntu.
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:
Fix Committed
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:
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
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
