Description of problem: NetworkManager functioning fine before updates to fc6test3 performed 2006.09.16. Fails to connect to wireless network by right-clicking applet, but opening 'Network' from administration menu and clicking 'Activate' on wireless device works. Wifi-radar and dhclient also work fine. Steps to Reproduce: 1. update fc6test3 to 2006.09.16 current 2. properly set up wireless device via network administration gui 3. attempt to connect using NetworkManager applet Actual results: fails to connect using applet Expected results: should connect, worked fine before Additional info: any useful info I could glean is attached
Created attachment 136450 [details] ifconfig output (while connected) 2006.09.16
Created attachment 136452 [details] iwconfig output (while connected) 2006.09.16
Created attachment 136453 [details] lspci output 2006.09.16
Created attachment 136454 [details] /var/log/messages 2006.09.16 Includes failed attempt to connect to wireless network via NetworkManager applet as well as successful attempt to connect to same network using wifi-radar.
Created attachment 136455 [details] /var/log/yum.log 2006.09.16 NetworkManager functioned perfectly before these updates + reboot
Fedora Core 5 and Fedora Core 6 are, as we're sure you've noticed, no longer test releases. We're cleaning up the bug database and making sure important bug reports filed against these test releases don't get lost. It would be helpful if you could test this issue with a released version of Fedora or with the latest development / test release. Thanks for your help and for your patience. [This is a bulk message for all open FC5/FC6 test release bugs. I'm adding myself to the CC list for each bug, so I'll see any comments you make after this and do my best to make sure every issue gets proper attention.]
I think this can be marked as closed. I had actually forgotten about this bug, sorry. NetworkManager has been working fine in my case for some time now, at least long enough for me to forget about this bug.
Okay closing. Apologies for the slow response to the bug. :(