Comment 28 for bug 141233

the wpasupplicant part of this bug is not really a problem for wpa_supplicant when used standalone. It is however a problem when used with some frontend like network manager. For network-manager, it has been worked around by alexander, thanks for that.

I'm closing the bugtask for wpasupplicant for now, because from this bugtrail, it is not clear to me how to reproduce this nor how to fix this in wpasupplicant. If you are suffering from this bug in one or the other way, please open a new bug for clarity. thanks.