HEAD 1.462 and 1.463, keyring errors

[Bill Moss <bmoss clemson edu>]

Dan applied the a patch at HEAD 1.459 has changed the way timestamps are 
written to gconf. Networks are written to gconf only
after a successful connection has been made, and timestamps are only 
updated if the network is in gconf and the user selects it from the 
menu. So gconf will not accumulate wireless networks that are scanned 
but not connected to. Please disregard the second solution for this 
issue that I posted as 'HEAD 1.451 gconf timestamp patch'.

HEAD 1.462 checks out OK on APs that broadcast ESSID and those that do 
not. It is necessary to clean up the keyring entries and the session 
startup programs because of the relocation of nm-applet. Also, somewhere 
along the way gtk2-2.8 became necessary.

HEAD 1.463 has some problems.

(a) If you boot in range of an AP that broadcasts its ESSID and has a 
key in keyring, you are asked for the keyring password and a connection 
is made. This is good.

(b) If you are booted with no AP in range and then move into range of an 
AP that is broadcasting its ESSID and has a key in keyring, NM fails to 
make a connection. The debug log says 'NO valid key exists' but you are 
not asked for a key. You can force the connection by clicking on the 
network in the menu and a connection is made but you are not asked for 
the keyring password.

(c) If you boot in range of a hidden AP which has a key in keyring, NM 
fails to make a connection. The debug log says 'NO valid key exists' but 
you are not asked for a key. You can force the connection by clicking on 
the network in the menu and a connection is made but you are not asked 
for the keyring password.

(d) If have a connection and you use the 'Connect to Other Network...' 
menu with a bogus key, you will eventually be given the passphrase 
dialog. If you cancel, the no-connection icon appears and then a few 
seconds later NM tries to remake the original connection but it fails in 
the DHCP stage. If you force the connection, by clicking on the menu 
item, a connection is made.

(e) If a non-beaconing AP is in range and you try to connect using 
'Connect to Other Wireless Network ...', no connection is made. NM hangs 
in stage1 of activation waiting for the wireless device to deactivate.
--
Bill Moss
Professor, Mathematical Sciences
Clemson University

--
Bill Moss
Professor, Mathematical Sciences
Clemson University