Version-Release number of selected component: wpa_supplicant-2.0-3.fc19 Additional info: reporter: libreport-2.1.4 backtrace_rating: 4 cmdline: /usr/sbin/wpa_supplicant -u -f /var/log/wpa_supplicant.log -c /etc/wpa_supplicant/wpa_supplicant.conf -u -f /var/log/wpa_supplicant.log -P /var/run/wpa_supplicant.pid crash_function: eap_peer_sm_tls_event executable: /usr/sbin/wpa_supplicant kernel: 3.9.4-301.fc19.x86_64 runlevel: N 5 uid: 0 Truncated backtrace: Thread no. 1 (10 frames) #0 eap_peer_sm_tls_event at ../src/eap_peer/eap.c:1316 #1 openssl_tls_cert_event at ../src/crypto/tls_openssl.c:1179 #2 tls_verify_cb at ../src/crypto/tls_openssl.c:1275 #3 internal_verify at x509_vfy.c:1653 #4 X509_verify_cert at x509_vfy.c:369 #5 ssl_verify_cert_chain at ssl_cert.c:554 #6 ssl3_get_server_certificate at s3_clnt.c:1159 #7 ssl3_connect at s3_clnt.c:334 #8 openssl_handshake at ../src/crypto/tls_openssl.c:2377 #9 openssl_connection_handshake at ../src/crypto/tls_openssl.c:2468
Created attachment 759282 [details] File: backtrace
Created attachment 759283 [details] File: cgroup
Created attachment 759284 [details] File: core_backtrace
Created attachment 759285 [details] File: dso_list
Created attachment 759286 [details] File: environ
Created attachment 759287 [details] File: limits
Created attachment 759288 [details] File: maps
Created attachment 759289 [details] File: open_fds
Created attachment 759290 [details] File: proc_pid_status
Created attachment 759291 [details] File: var_log_messages
I connected to wired network (that uses 802.1X) and disconnected from wireless one (that uses same authentication). reporter: libreport-2.1.5 backtrace_rating: 4 cmdline: /usr/sbin/wpa_supplicant -u -f /var/log/wpa_supplicant.log -c /etc/wpa_supplicant/wpa_supplicant.conf -u -f /var/log/wpa_supplicant.log -P /var/run/wpa_supplicant.pid crash_function: eap_peer_sm_tls_event executable: /usr/sbin/wpa_supplicant kernel: 3.9.5-301.fc19.x86_64 package: wpa_supplicant-2.0-3.fc19 reason: Process /usr/sbin/wpa_supplicant was killed by signal 11 (SIGSEGV) runlevel: N 5 uid: 0
Using RTL8188CE wifi adapter to connect to WPA2 protected access point reporter: libreport-2.1.6 backtrace_rating: 4 cmdline: /usr/sbin/wpa_supplicant -u -f /var/log/wpa_supplicant.log -c /etc/wpa_supplicant/wpa_supplicant.conf -u -f /var/log/wpa_supplicant.log -P /var/run/wpa_supplicant.pid crash_function: eap_peer_sm_tls_event executable: /usr/sbin/wpa_supplicant kernel: 3.10.5-201.fc19.x86_64 package: wpa_supplicant-2.0-3.fc19 reason: Process /usr/sbin/wpa_supplicant was killed by signal 11 (SIGSEGV) runlevel: N 5 uid: 0
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.