N-M doesn't work without gnome keyring?

[Paul Johnson <pauljohn ku edu>]

I had trouble with N-M, it never accepted my WEP key. I have tried over 
the past few months, without success.  I asked about it in the fedora 
list, and after some discussion I found the solution. Install 
gnome-keyring-manager.  After I found the fix, then N-M does work for 
me, both on WEP encrypted networks and on nonencrypted networks.  

After I posted about my success in the fedora list, two people wrote to 
me and said I should forward this experience to your list, hoping to 
either 1) find out if I'm completely wrong, or 2) let you know that 
gnome-keyring-manager really makes a big difference.

To fedora-list 2006/06/08:

I've been testing some more.  I was unable to log in, and started
re-tracing my steps. I turned off the "network" service, still no N-M
joy.  But I grew tired of typing in the key over and over, and I
installed the rpm gnome-keyring-manager.i386 2.14.0-1, and it would
not run because it could not connect to the keyring daemon.

Then I tried the MS Windows solution: reboot.

After using modprobe to load the ipw3945 module and loading the
userspace driver, then N-M did work.  After I typed in the WEP key,
then the gnome keyring manager popped up and asked for a password.
That's when I really knew I was in business!

Hypothesis 1:

what if N-M failed to connect with my WEP key because
gnome-keyring-manager was not installed?  N-M appeared to be doing
nothing, but maybe it was looking for the keyring manager?

Hypothesis 2:

Perhaps the NetworkManager RPM should have a pre-requisite of
gnome-keyring-manager.

--
Paul E. Johnson                       email: pauljohn ku edu
Professor, Political Science          http://pj.freefaculty.org
1541 Lilac Lane, Rm 504                              
University of Kansas                  Office: (785) 864-9086
Lawrence, Kansas 66044-3177           FAX: (785) 864-5700