wpa_supplicant crashed with SIGSEGV

Bug #1224830 reported by soren nygaard
This bug report is a duplicate of:  Bug #1210785: wpa_supplicant crashed with SIGSEGV. Edit Remove
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
wpa (Ubuntu)
New
Undecided
Unassigned

Bug Description

automatic redirection for bug after upgrade to Xubuntu 13.10 on Asus EEEpc 1015PX

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: wpasupplicant 1.0-3ubuntu2
ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0
Uname: Linux 3.11.0-7-generic i686
NonfreeKernelModules: wl
ApportVersion: 2.12.1-0ubuntu4
Architecture: i386
CrashCounter: 1
Date: Fri Sep 13 09:09:04 2013
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-guandu-20110429-8
ExecutablePath: /sbin/wpa_supplicant
InstallationDate: Installed on 2011-11-02 (680 days ago)
InstallationMedia: Ubuntu 10.10 "Maverick" - Build i386 LIVE Binary 20110429-13:50
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: 0x8102980: mov (%edi),%ebx
 PC (0x08102980) ok
 source "(%edi)" (0x06083088) not located in a known VMA region (needed readable region)!
 destination "%ebx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: wpa
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: wpa_supplicant crashed with SIGSEGV
UpgradeStatus: Upgraded to saucy on 2013-09-04 (8 days ago)
UserGroups:

Revision history for this message
soren nygaard (fam-nygaard) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1210492, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

information type: Private → Public
tags: removed: need-i386-retrace
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.