[Bug 758121] New: After initial WiFi setup, KNetwork manager does not connect, and cannot see router/WiFi
https://bugzilla.novell.com/show_bug.cgi?id=758121 https://bugzilla.novell.com/show_bug.cgi?id=758121#c0 Summary: After initial WiFi setup, KNetwork manager does not connect, and cannot see router/WiFi Classification: openSUSE Product: openSUSE 12.2 Version: Milestone 3 Platform: i686 OS/Version: openSUSE 12.2 Status: NEW Severity: Major Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers@suse.de ReportedBy: smaug42@gmail.com QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/536.6 (KHTML, like Gecko) Chrome/20.0.1094.0 Safari/536.6 SUSE/20.0.1094.0 This is similar to a problem discussed with the early Milestone releases of openSUSE 12.1. After a clean install (not an upgrade) of openSUSE12.2 Milestone3 with KDE4, WiFi fails on restart. Wired works correctly. Reproducible: Always Steps to Reproduce: Assuming a clean install of openSUSE 12.2/M3. WiFi was not set up during installation. Booted to the KDE4 desktop, and no configuration changes made, everything is default post-install. 1. Click KNetworkManager icon in system tray. 2. Select WiFi network from the list. 3. Configure (enter WPA2 password). 4. Save and wait for connection. 5. Test connection is working correctly. 6. Reboot computer. Actual Results: On restart (step 6), WiFi does not connect. KNetworkManager shows a "no connection" icon. This no connection status persists over multiple reboots and/or logout/login. 1. Click KNetworkManager icon. 2. Scroll through available WiFi networks and the previously configured WiFi network is not displayed. 3. Click Manage Connections. 4. Select the previously configured WiFi network connection and click Delete. 5. Restart computer. 6. Click KNetworkManager icon in the system tray 7. Select and configure the WiFi network (after the delete and reboot the WiFi node is shown again) 8. Test and verify that WiFi is working. WiFi will continue to be available/working right up until a restart, and then again, the WiFi is no longer visible nor can it be connected to. Tested hardware: CPU=Intel Atom 1.6GHz GPU=Intel 945GME WiFi=AR9285 Tested in Gnome3 as well. If the WiFi issue failed in KDE4 and WiFi was not available after a reboot, logging out of KDE4 and logging in to Gnome 3 did not change anything. To get WiFi working in Gnome3, I had to log back in to KDE4, delete the KDE4 WiFi configuration, reboot, log in to Gnome3 and configure WiFi there. Once configured in Gnome3, the connection persists over reboots. Interestingly, after deleting ALL WiFi configuration in KDE4, rebooting, configuring WiFi in Gnome3, and then logging in to KDE4... WiFi works perfectly and persists in KDE4 over reboots. It only seems to fail when you try to configure in KDE4 first. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=758121
https://bugzilla.novell.com/show_bug.cgi?id=758121#c1
Jan Ritzerfeld
https://bugzilla.novell.com/show_bug.cgi?id=758121
https://bugzilla.novell.com/show_bug.cgi?id=758121#c2
--- Comment #2 from Clayton smaug42
Is this still a problem? It works for me using 12.2 RC 1 storing the WPA key in KWallet.
Unfortunately I have no access to my test machines until at least November, and I cannot get openSUSE 12.2 (or 12.1) to even launch the YaST installer on the only computer I've got access to right now... so there no way for me to re-test this particular bug. The key was a clean install NOT an upgrade. If you're not seeing it on a clean install with KDE4, then close the bug (considering there is no way for me to provide info). -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=758121
https://bugzilla.novell.com/show_bug.cgi?id=758121#c3
--- Comment #3 from Jan Ritzerfeld
https://bugzilla.novell.com/show_bug.cgi?id=758121
https://bugzilla.novell.com/show_bug.cgi?id=758121#c4
--- Comment #4 from Clayton smaug42
https://bugzilla.novell.com/show_bug.cgi?id=758121
https://bugzilla.novell.com/show_bug.cgi?id=758121#c5
--- Comment #5 from Jan Ritzerfeld
https://bugzilla.novell.com/show_bug.cgi?id=758121
https://bugzilla.novell.com/show_bug.cgi?id=758121#c6
Szymon Kowalczyk
https://bugzilla.novell.com/show_bug.cgi?id=758121
https://bugzilla.novell.com/show_bug.cgi?id=758121#c7
abdel rebel
https://bugzilla.novell.com/show_bug.cgi?id=758121
https://bugzilla.novell.com/show_bug.cgi?id=758121#c8
--- Comment #8 from Szymon Kowalczyk
opensuse 12.2 (....) Any ideas will be hugely appreciated.
The best workaround in my opinion is to mar network as a system connection: http://www.physik.rwth-aachen.de/typo3temp/pics/f2855a44e6.png (below connect automatically) other workarounds are in comment #6 -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=758121
https://bugzilla.novell.com/show_bug.cgi?id=758121#c9
--- Comment #9 from abdel rebel
https://bugzilla.novell.com/show_bug.cgi?id=758121
https://bugzilla.novell.com/show_bug.cgi?id=758121#c10
abdel rebel
https://bugzilla.novell.com/show_bug.cgi?id=758121
https://bugzilla.novell.com/show_bug.cgi?id=758121#c11
--- Comment #11 from Szymon Kowalczyk
how can it connect automatically to a network which is not listed in the wlan interface?
I checked it but looking into networkmanager.log network exist while "auto connect" is executed. In my opinion problem is that connection password system is not ready to provide secrets on auto connect: after system start we have: ... <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0] <info> Activation (wlan0/wireless): access point 'removed' has security, but secrets are required. <info> (wlan0): device state change: config -> need-auth (reason 'none') [50 60 0] <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete. PROBLEM: <warn> No agents were available for this request. <info> (wlan0): device state change: need-auth -> failed (reason 'no-secrets') [60 120 7] <warn> Activation (wlan0) failed for access point (neostrada_7869) <info> Marking connection 'removed' invalid. <warn> Activation (wlan0) failed. ... but after switching WiFi off and on ... <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0] <info> Activation (wlan0/wireless): access point 'removed' has security, but secrets are required. <info> (wlan0): device state change: config -> need-auth (reason 'none') [50 60 0] <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete. NO PROBLEM: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started... <info> (wlan0): device state change: need-auth -> prepare (reason 'none') [60 40 0] <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting... <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0] <info> Activation (wlan0/wireless): connection 'removed' has security, and secrets exist. No new secrets needed. Which mechanizm/program/process is responsible to provide secrets: <info> (wlan0): device state change: config -> need-auth (reason 'none') [50 60 0] This is started to late or is not working correctly. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=758121
https://bugzilla.novell.com/show_bug.cgi?id=758121#c12
Ferenc Nagy
https://bugzilla.novell.com/show_bug.cgi?id=758121
https://bugzilla.novell.com/show_bug.cgi?id=758121#c13
Javier Llorente
participants (1)
-
bugzilla_noreply@novell.com