Version: 0.2 (using KDE KDE 3.5.7) Installed from: Debian testing/unstable Packages OS: Linux Hi, knetworkmanager does not automatically reassociate to a WEP encrypted wireless network after hibernate. The network is listed in the right-click menu and choosing it manually from the list works. The desired network is listed in "trusted networks" (so forgetting that it is trusted isn't the problem). Note that knetworkmanager does associate just fine after a reboot and initial logon. Just doesn't associate after hibernate. In case it helps you: nm-tool info right after hibernate: #nm-tool NetworkManager Tool State: disconnected - Device: eth0 ---------------------------------------------------------------- NM Path: /org/freedesktop/NetworkManager/Devices/eth0 Type: 802.11 Wireless Driver: ipw2200 Active: no HW Address: 00:16:F6:8A:6D:78 Capabilities: Supported: yes Wireless Settings Scanning: yes WEP Encryption: yes WPA Encryption: yes WPA2 Encryption: yes Wireless Networks (* = Current Network) 5848_primrose: Infrastructure Mode, Freq 2.412 MHz, Rate 62 Mb/s, Strength 31%, Encrypted (WEP) linksys: Infrastructure Mode, Freq 2.437 MHz, Rate 54 Mb/s, Strength 39% belkin54g: Infrastructure Mode, Freq 2.462 MHz, Rate 62 Mb/s, Strength 31% nm-tool after manually selecting the desired network via knetworkmanager menu: #nm-tool NetworkManager Tool State: connected - Device: eth0 ---------------------------------------------------------------- NM Path: /org/freedesktop/NetworkManager/Devices/eth0 Type: 802.11 Wireless Driver: ipw2200 Active: yes HW Address: 00:16:F6:8A:6D:78 Capabilities: Supported: yes Speed: 54 Mb/s Wireless Settings Scanning: yes WEP Encryption: yes WPA Encryption: yes WPA2 Encryption: yes Wireless Networks (* = Current Network) *5848_primrose: Infrastructure Mode, Freq 2.412 MHz, Rate 62 Mb/s, Strength 31%, Encrypted (WEP) linksys: Infrastructure Mode, Freq 2.437 MHz, Rate 54 Mb/s, Strength 39% belkin54g: Infrastructure Mode, Freq 2.462 MHz, Rate 62 Mb/s, Strength 31% IP Settings: IP Address: 192.168.1.3 Subnet Mask: 255.255.255.0 Broadcast: 192.168.1.255 Gateway: 192.168.1.100 Primary DNS: 192.168.1.100 Secondary DNS: 0.0.0.0 Thanks for the nice program, C.
I'm also seeing this problem. Model: Dell Latitude D800 OS: OpenSuse 10.3 (Linux 2.6.22.9-0.4-default i686) KDE version: 3.5.7 release 72 KNetworkManager version: 0.2 Wireless: Intel PRO/Wireless 2200BG Wireless Driver: ipw2200 (revision 5?)
Confirming this in Ubuntu Gutsy (KNetworkManager 0.2, KDE 3.5.8). In my case, there is an additionnal problem: when I reassociate (manually) after resume, the tool tip will very quickly progress to 100% (so quick I sometimes cannot see it). After that, I am still associated with no AP. When I try a second time, it will work normally (maybe 10 to 20 seconds to connect a WPA/AES network, quicker for a WEP network, and the AP is actually associated in the end). It is quite surprising that: 1 - the system does not automatically associates an AP at resume 2 - the association process systematically fails at the first manual attempt 3 - the user has no feedback, no error window, sees nothing Maybe for the 2 and 3, another bug report should be filed, but all those issues happen only when I resume from hibernation, so I don't think they are completely unrelated.
*** Bug 149473 has been marked as a duplicate of this bug. ***
*** Bug 151265 has been marked as a duplicate of this bug. ***
*** Bug 154459 has been marked as a duplicate of this bug. ***
*** Bug 162911 has been marked as a duplicate of this bug. ***
A login to the desktop should connect to the wireless connection, if present, that was there previously. With Fedora's knetworkmanager-0.7-0.7.20080926svn.fc10.i386 this seems to be a regression, although it may just be taking over from NetworkManager, and NM was better at doing the right thing, what the user expects. It's not brain surgery. Fix it, release it, everyone lives.
Never mind. I see that Fedora eol'd knetworkmanager, and standardised on NetworkManager-gnome. Sorry for the spam.
More spam, just to clarify, kde-plasma-NetworkManager is the future Fedora package. My bad, sorry.
Yes, and there are now fixes in the intel drivers to make sure that they reload their firmware after a suspend.