I seem to be having similar issues. Everything was fine when I was using my
laptop last night and when booted this morning and choosing my wifi network,
I was prompted for the WPA passphase and not my default keyring passphrase.
Below are the updates installed last night, taken from /var/log/yum.log
Oct 29 21:16:30 Updated: compiz-fusion - 0.6.0-5.fc8.x86_64
Oct 29 21:16:32 Updated: libsoup - 2.2.103-1.fc8.x86_64
Oct 29 21:16:34 Updated: gnokii - 0.6.18-3.fc8.x86_64
Oct 29 21:16:44 Updated: anaconda - 11.3.0.48-1.x86_64
Oct 29 21:16:45 Updated: bluez-utils-alsa - 3.20-4.fc8.x86_64
Oct 29 21:16:45 Updated: bluez-utils-cups - 3.20-4.fc8.x86_64
Oct 29 21:16:48 Updated: bluez-utils - 3.20-4.fc8.x86_64
Oct 29 21:16:48 Updated: isomd5sum - 11.3.0.48-1.x86_64
Oct 29 21:18:33 Updated: compiz-fusion-gnome - 0.6.0-5.fc8.x86_64
Oct 29 21:18:39 Updated: iso-codes - 1.5-1.fc8.noarch
Oct 29 21:18:40 Updated: libsoup - 2.2.103-1.fc8.i386
Here is the relevant part from /var/log/messages
Oct 30 07:35:24 dougalb-lnx NetworkManager: <info> User request for
activation of wlan0.
Oct 30 07:35:24 dougalb-lnx NetworkManager: <info> Deactivating device
eth0.
Oct 30 07:35:24 dougalb-lnx NetworkManager: <info> eth0: canceled DHCP
transaction, dhclient pid 3011
Oct 30 07:35:24 dougalb-lnx avahi-daemon[2187]: Withdrawing address record
for 192.168.100.14 on eth0.
Oct 30 07:35:24 dougalb-lnx avahi-daemon[2187]: Leaving mDNS multicast group
on interface eth0.IPv4 with address 192.168.100.14.
Oct 30 07:35:24 dougalb-lnx avahi-daemon[2187]: Interface eth0.IPv4 no
longer relevant for mDNS.
Oct 30 07:35:24 dougalb-lnx NetworkManager: <info> Activating device wlan0
Oct 30 07:35:24 dougalb-lnx avahi-daemon[2187]: Withdrawing address record
for fe80::21a:4bff:fe5b:b4b3 on eth0.
Oct 30 07:35:24 dougalb-lnx NetworkManager: <info> Activation (wlan0) Stage
1 of 5 (Device Prepare) scheduled...
Oct 30 07:35:24 dougalb-lnx NetworkManager: <info> Activation (wlan0) Stage
1 of 5 (Device Prepare) started...
Oct 30 07:35:24 dougalb-lnx NetworkManager: <info> Activation (wlan0) Stage
2 of 5 (Device Configure) scheduled...
Oct 30 07:35:24 dougalb-lnx NetworkManager: <info> Activation (wlan0) Stage
1 of 5 (Device Prepare) complete.
Oct 30 07:35:24 dougalb-lnx NetworkManager: <info> Activation (wlan0) Stage
2 of 5 (Device Configure) starting...
Oct 30 07:35:24 dougalb-lnx NetworkManager: <info> Activation
(wlan0/wireless): access point 'Auto hippotje' has security, but secrets are
required.
Oct 30 07:35:24 dougalb-lnx NetworkManager: <info> Activation (wlan0) Stage
2 of 5 (Device Configure) complete.
Oct 30 07:35:24 dougalb-lnx NetworkManager: Missing required value
'key-mgmt'.
Oct 30 07:35:24 dougalb-lnx NetworkManager: Missing or invalid key
management
Oct 30 07:35:24 dougalb-lnx NetworkManager: <info> Activation (wlan0) Stage
1 of 5 (Device Prepare) scheduled...
Oct 30 07:35:24 dougalb-lnx NetworkManager: <info> Activation (wlan0) Stage
1 of 5 (Device Prepare) started...
Oct 30 07:35:24 dougalb-lnx NetworkManager: <info> Activation (wlan0) Stage
2 of 5 (Device Configure) scheduled...
Oct 30 07:35:24 dougalb-lnx NetworkManager: <info> Activation (wlan0) Stage
1 of 5 (Device Prepare) complete.
Oct 30 07:35:24 dougalb-lnx NetworkManager: <info> Activation (wlan0) Stage
2 of 5 (Device Configure) starting...
Oct 30 07:35:24 dougalb-lnx NetworkManager: <info> Activation
(wlan0/wireless): connection 'Auto hippotje' has security, and secrets
exist. No new secrets needed.
Oct 30 07:35:24 dougalb-lnx NetworkManager: <info> Config: added 'ssid'
value 'hippotje'
Oct 30 07:35:24 dougalb-lnx NetworkManager: <info> Config: added
'key_mgmt'
value 'WPA-PSK'
Oct 30 07:35:24 dougalb-lnx NetworkManager: <info> Config: added 'psk'
value '<omitted>'
Oct 30 07:35:24 dougalb-lnx NetworkManager: <info> Config: added 'proto'
value 'WPA RSN'
Oct 30 07:35:24 dougalb-lnx NetworkManager: <info> Config: added
'pairwise'
value 'TKIP CCMP'
Oct 30 07:35:24 dougalb-lnx NetworkManager: <info> Config: added 'group'
value 'WEP40 WEP104 TKIP CCMP'
Oct 30 07:35:24 dougalb-lnx NetworkManager: <info> Activation (wlan0) Stage
2 of 5 (Device Configure) complete.
Oct 30 07:35:24 dougalb-lnx NetworkManager: <info> (wlan0) Supplicant
interface state change: 0 -> 2
Oct 30 07:35:39 dougalb-lnx ntpd[2042]: sendto(83.137.16.7) (fd=23): Invalid
argument
Oct 30 07:35:49 dougalb-lnx NetworkManager: <info> Activation
(wlan0/wireless): association took too long, asking for new key.
Oct 30 07:35:49 dougalb-lnx NetworkManager: <info> (wlan0) Supplicant
interface state change: 2 -> 0
Oct 30 07:36:05 dougalb-lnx NetworkManager: <WARN> get_secrets_cb():
Couldn't get connection secrets:
applet.c.2997(get_secrets_dialog_response_cb): canceled.
Oct 30 07:36:05 dougalb-lnx NetworkManager: <info> Activation (wlan0)
failed for access point (hippotje)
Oct 30 07:36:05 dougalb-lnx NetworkManager: <info> Marking connection 'Auto
hippotje' invalid.
Oct 30 07:36:05 dougalb-lnx NetworkManager: <info> Activation (wlan0)
failed.
Oct 30 07:36:05 dougalb-lnx NetworkManager: <info> Deactivating device
wlan0.
Oct 30 07:36:05 dougalb-lnx NetworkManager: <info> SWITCH: no current
connection, found better connection 'Auto Ethernet (eth0)'.
I am guessing the problem lies with the following two lines:
Oct 30 07:35:24 dougalb-lnx NetworkManager: Missing required value
'key-mgmt'.
Oct 30 07:35:24 dougalb-lnx NetworkManager: Missing or invalid key
management
Anybody got any thoughts as to what got changed?
Kind regards,
Dougal
On 10/30/07, Rodd Clarkson <rodd(a)clarkson.id.au> wrote:
On Mon, 2007-10-29 at 19:29 +0000, Adam Huffman wrote:
> On Mon, 29 Oct 2007, Adam Huffman wrote:
>
> > This morning NM (svn3030) was behaving strangely. I repeatedly
entered
> > my gnome keyring password but the dialog box kept asking for it. In
the
> > end, I cancelled it and the WPA connection seemed to take place
anyway.
> >
>
> This happened again. It wouldn't accept the keyring password and when I
> clicked on "Deny", it connected to the network anyway, which doesn't
> seem terribly secure...
>
> I've added a comment to
>
>
https://bugzilla.redhat.com/show_bug.cgi?id=351411
>
Alright, I don't think this is NM, I think this is gnome-keyring.
I'm assuming you've set up a new WPA connection and after entering the
passphrase, you've been prompted for the gnome-keyring password to store
the passphrase.
Since you can't enter the password for the keyring, you'll be prompted
for the WPA passphrase again next time you connect.
I'm having the same problem in evolution. I've set up a IMAP account
for my gmail account and I have to retype the password each time I
restart evolution, because I can't store the imap password in the
keyring since gnome-keyring won't accept my keyring password. I can
unlock items in the keyring using the keyring password (like my NM WPA
information) but not store anything.
R.
--
"It's a fine line between denial and faith.
It's much better on my side"
--
fedora-test-list mailing list
fedora-test-list(a)redhat.com
To unsubscribe:
https://www.redhat.com/mailman/listinfo/fedora-test-list