-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Paul Johnson wrote:
> 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!
Cool! So you got it working good now?
> 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?
I'm sure that you may hesitate to break things at this point, but if
you feel adventurous it might be a useful test to remove g-k-m and
then see if NM still can connect to your network. You could create a
new account to test under so you don't have to muck up anything in
your working one.
If it fails without g-k-m and works with it, then it seems like there
ought to be a dependency on that in NM.
- --
Todd OpenPGP -> KeyID: 0xD654075A | URL: www.pobox.com/~tmz/pgp
======================================================================
The American Republic will endure until the day Congress discovers
that it can bribe the public with the public's money.
-- Alexis De Tocqueville.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: When crypto is outlawed bayl bhgynjf jvyy unir cevinpl.
iG0EARECAC0FAkSITGwmGGh0dHA6Ly93d3cucG9ib3guY29tL350bXovcGdwL3Rt
ei5hc2MACgkQuv+09NZUB1otQwCfaYyWMLPVfh3g4EIQ39St8RK++F4AoJqeX5Q0
c0BTxPyoUCT/sgLqn2uf
=pU4A
-----END PGP SIGNATURE-----
