Red Hat Bugzilla – Bug 961019
[abrt] wpa_supplicant-1.1-1.fc18: ibss_rsn_init: Process /usr/sbin/wpa_supplicant was killed by signal 11 (SIGSEGV)
Last modified: 2014-02-05 16:17:01 EST
Description of problem:
1) Execute Virtualbox VM ,including Windows XP
2) A few mount ago , the network is shutdown and re-connect
3) But the network can not connect all the time, i don't know why. i think this is a bug about fedora18,this problem didn't happend to fedora17 .Maybe a bug of Virtualbox VM.I don't know
4) then wpa_supplicant crashed is happend
A few months ago , this problem is to my Acer laptop. I took a month to fixed it through Google,but i failed. I'm dejected very much .And now , i'm learning JAVA,i can not work without Fedora.But this proplem is stil exist. Why Google did't include thus page about this problem? I need a great help, thank you
Version-Release number of selected component:
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
core_backtrace: 7848ab1beef568266f8fdf22a160a61d60b3ce17 0x1f356 ibss_rsn_init /usr/sbin/wpa_supplicant dbc459f4733a704de8582fb6d33923e6ae2fe5fd
Thread no. 1 (1 frames)
Created attachment 745261 [details]
Created attachment 745262 [details]
Created attachment 745263 [details]
Created attachment 745264 [details]
Created attachment 745265 [details]
Created attachment 745266 [details]
Created attachment 745267 [details]
Created attachment 745268 [details]
Created attachment 745269 [details]
It happened to me on wpa_supplicant 1.0->1.1 update. Had to restart the box.
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '18'.
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 prior to Fedora 18's end of life.
Thank you for reporting this issue and we are sorry that we may not be
able to fix it before Fedora 18 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 to Fedora 18's end of life.
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 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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
Thank you for reporting this bug and we are sorry it could not be fixed.