Bug 689115

Summary: [abrt] wpa_supplicant-1:0.7.3-4.fc15: _dbus_abort: Process /usr/sbin/wpa_supplicant was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Alex Williamson <alex.williamson>
Component: wpa_supplicantAssignee: Dan Williams <dcbw>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 15CC: dcbw, otaylor
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:d8988283516c5e5f0f8c31140750abe484224e6b
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-04-09 23:01:50 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description Alex Williamson 2011-03-19 16:08:51 UTC 
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 14109 bytes
cmdline: /usr/sbin/wpa_supplicant -c /etc/wpa_supplicant/wpa_supplicant.conf -B -u -f /var/log/wpa_supplicant.log -P /var/run/wpa_supplicant.pid
comment: Can't use wireless on f15, NetworkManager shows it disconnected, and wpa_supplicant errors are filling my disk.  This is from a fresh install of the alpha release
component: wpa_supplicant
Attached file: coredump, 995328 bytes
crash_function: _dbus_abort
executable: /usr/sbin/wpa_supplicant
kernel: 2.6.38-1.fc15.x86_64
package: wpa_supplicant-1:0.7.3-4.fc15
rating: 4
reason: Process /usr/sbin/wpa_supplicant was killed by signal 6 (SIGABRT)
release: Fedora release 15 (Lovelock)
time: 1300550924
uid: 0

How to reproduce
-----
1. Wireless show disconnected
2.
3.
Comment 1 Alex Williamson 2011-03-19 16:08:53 UTC 
Created attachment 486385 [details]
File: backtrace
Comment 2 Alex Williamson 2011-03-27 15:28:13 UTC 
Seems like wap_supplicant is broken on all x86_64 systems... seems important.
Comment 3 Owen Taylor 2011-04-09 23:01:50 UTC 

*** This bug has been marked as a duplicate of bug 678625 ***