[Bug 235060] New: KNetworkManager does not reconnect to WLAN after suspend2disk
https://bugzilla.novell.com/show_bug.cgi?id=235060 Summary: KNetworkManager does not reconnect to WLAN after suspend2disk Product: openSUSE 10.2 Version: Final Platform: i686 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: bernhard.bender@web.de QAContact: qa@suse.de After a suspend to disk, KNetworkManager is unable to reconnect to the WLAN it was connected to before suspending. When I manually select the WLAN, the connection failes after requesting the WPA key (which had been stored to the kwallet previously). When I terminate and restart KNetworkManager, I is able to connect using the key from the wallet. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=235060 ------- Comment #1 from bernhard.bender@web.de 2007-01-14 16:59 MST ------- Created an attachment (id=112924) --> (https://bugzilla.novell.com/attachment.cgi?id=112924&action=view) Excerpt from /var/log/NetworkManager This log from /var/log/NetworkManager shows the failed connection attempt. I can provide more info upon request. Thanks. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=235060 chrubis@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team- |thoenig@novell.com |screening@forge.provo.novell| |.com | -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=235060 hschaa@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hschaa@novell.com Status|NEW |NEEDINFO Info Provider| |bernhard.bender@web.de ------- Comment #2 from hschaa@novell.com 2007-01-16 03:26 MST ------- Is the network you are connecting to hidden? -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=235060 bernhard.bender@web.de changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|bernhard.bender@web.de | ------- Comment #3 from bernhard.bender@web.de 2007-01-16 04:22 MST ------- The network is not hidden, SSID bcast is enabled. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=235060 ------- Comment #4 from jpr@novell.com 2007-02-07 10:38 MST ------- Does it work if you remove the config Yast for the wireless card? -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=235060 ------- Comment #5 from bernhard.bender@web.de 2007-02-08 15:10 MST ------- After removing the yast config for the wlan device (setting it to "never" connect), KNetworkManager still does not connect automatically after resuming from suspend. It does however reconnect successfully when I manually select the AP. It is no longer necessary to restart KNW. Since it does connect automatically after system boot, I would like it to connect automatically after resume from suspend. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=235060 ------- Comment #6 from bernhard.bender@web.de 2007-02-14 15:34 MST ------- I just noticed that knetworkmanager now does automatically reconnect to WLAN after a suspend2disk. NetworkManager-kde-0.1r606753-17.1 NetworkManager-0.6.4-49 Kernel: 2.6.20 with the patches as described in https://bugzilla.novell.com/show_bug.cgi?id=239101#c20 The suspend itself fails and immediately resumes, but KNW recognizes a new network interface an automatically re-connects to my WLAN The setup here uses WPA, ndiswrapper.1.37 (with BCM4312 driver) wpa_supplicant-0.5.7 (both of which are not from the standard Suse10.2) -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=235060 ------- Comment #7 from bernhard.bender@web.de 2007-02-14 16:44 MST ------- After fiddling with GRUB the suspend/resume succeeded. Now, KWN does detect the card an network, but I need to manually select it in order to connect againn after resume. This is just like I described it in comment 5, but this time for my hp compaq nx6325 laptop. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=235060 ------- Comment #8 from bernhard.bender@web.de 2007-02-14 17:14 MST ------- Next test with identical setup worked just fine: KNW made the connection to WLAN automatically after resuming... -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=235060 hschaa@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=235060 hschaa@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |bernhard.bender@web.de ------- Comment #9 from hschaa@novell.com 2007-05-02 02:49 MST ------- Did the described symptoms appear anymore? Can I assume this one as "fixed"? -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=235060 bernhard.bender@web.de changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|bernhard.bender@web.de | ------- Comment #10 from bernhard.bender@web.de 2007-05-02 06:39 MST ------- I did not see this problem again after writing comment 8 I consider this issue closed. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=235060 hschaa@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |INVALID ------- Comment #11 from hschaa@novell.com 2007-05-02 06:47 MST ------- Closing as "invalid". Please reopen if the issue appears again. Thanks. -- 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, or are watching someone who is.
participants (1)
-
bugzilla_noreply＠novell.com