5 Nov
2008
5 Nov
'08
13:46
https://bugzilla.novell.com/show_bug.cgi?id=406635 User jbenc@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=406635#c15 --- Comment #15 from Jiri Benc <jbenc@novell.com> 2008-11-05 06:46:17 MST --- Yes. And it is really the same issue as bug 416508. By the way, it is not connected to iwl* drivers - I can reproduce it also on my laptop with ath5k driver. It seems to happen more often with iwl* but it may be just a coincidence. >From what I know so far, it is caused by knetworkmanager not getting all networks from NetworkManager. This has two consequences: 1. knetworkmanager doesn't show all wireless networks available, while nm-tool does. 2. When connecting, NetworkManager asks knetworkmanager for keys, which are not provided as knetworkmanager doesn't see the network. This results in unsuccessful attempt to associate. This also means that the reconnection fails after suspend - NetworkManager tries to reassociate and asks knetworkmanager for keys, which fails. Also, it seems it happens only after KDE is started or after a suspend. After restarting knetworkmanager, everything works. In all cases nm-tool reports all of the networks. (Please note we have probably another bug with iwl* driver when the current network is not returned even by the driver - see bug 394333. But that is not the same as this bug as the symptoms described here can be observed with other drivers as well.) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.