wpa_supplicant crashed with SIGSEGV

Bug #1212316 reported by Sharise Pringle
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

I'm really new to ubuntu so I'm not sure what this means. It just popped up when I took my computer out of sleep, and I figured I'd send an error report in hopes that I can get some direction on how to fix it myself.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: wpasupplicant 1.0-3ubuntu2
ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3
Uname: Linux 3.10.0-6-generic i686
ApportVersion: 2.12-0ubuntu3
Architecture: i386
CrashCounter: 1
Date: Wed Aug 14 01:20:35 2013
ExecutablePath: /sbin/wpa_supplicant
InstallationDate: Installed on 2013-08-13 (0 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130810)
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)" (0xac8b0000) 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: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
Sharise Pringle (starrbuck711) 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.