Bug 366691

Description of problem:
I use my Laptop in a WPA-EAP/TTLS/TKIP/PAP environment. With NetworkManager 
0.6.x I was able to connect to the network, since the update to NetworkManager 
0.7.x this doesn't work anymore. Instead, /var/log/messages reports a segfault 
in wpa_supplicant.
If I deactivate NM and start wpa_supplicant manually with a manual generated 
configuration file everything works without a problem.

I tested with a normal WPA network from my home based router, that worked 
without problems.

Version-Release number of selected component (if applicable):
NetworkManager-0.7.0-0.5.svn3030.fc8
wpa_supplicant-0.5.7-15.fc8

How reproducible:
Set up an enterprise WPA network like above and try to connect with it. The 
segfault appears every time for me.

Actual results:
The NetworkManager first tries to connect directly without asking for the 
login data since these are already stored. In the attached log file it can be 
seen that NM uses the login information for the new configuration - and 
wpasupplicant then crashes (at 13:31:20).
Afterwards, the supplicant is restarted (13:31:26), another login attempt is 
done but doesn't work for some reason, and the interface asks the connection 
details again (a Mark is set at 13:31:46 to highlight that point). The data 
are typed into the GUI, NM adds them to the configuration - and wpa_supplicant 
crashes again at 13:32:09.

Expected results:
NM should automatically detect the known network and automatically connect to 
it.