Bugzilla – Bug 758121
After initial WiFi setup, KNetwork manager does not connect, and cannot see router/WiFi
Last modified: 2012-09-09 21:55:33 UTC
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.
Is this still a problem? It works for me using 12.2 RC 1 storing the WPA key in KWallet.
(In reply to comment #1) > 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).
I made a clean 12.2 RC 1 installation with KDE4. I leave this bug open as a reminder for me to test. This is because I have exactly the same problem when logging out and in again! See Bug 765245. Did you store your WPA key in KWallet? Did you use an empty password? Then I know what to test.
WPA key was not stored in KWallet (I never use KWallet TBH). It was not an empty password - the router is configured with a typical PSK (letters, numbers , etc.). The scenario is simple: - clean install of openSUSE/KDE4 with new user (no reuse of old /home data) - connect to WiFi WPA using PSK and in my case I do not save the password in KWallet, it's saved in the KNetwork Manager (typical use case for my computers) - log out of KDE and back in and WiFi will fail to connect unless I delete, restart, and reconfigure.
Sorry, I really meant an empty KWallet password not an empty WPA2 key itself. I will test your scenario because that is the way I will really use it in production, too.
I have the same problem on openSUSE 12.2 after clean install I provided all info about WiFi network and everything worked fine until restart. After restart I cannot found my network on the networkmanager list. I found 4 workarounds: 1) (tested, working) mark a network as "System connection" (I use this one) 2) (tested, working) enter network name in connect to hidden network field and fill one time more all settings 3) (not tested) disable and enable WiFi by hardware switch or networkmanager switch 4) (not tested) Delete network settings and restart computer. I also fount that there is some similar bugs: https://bugzilla.novell.com/show_bug.cgi?id=771582 https://bugzilla.novell.com/show_bug.cgi?id=774934 https://bugzilla.novell.com/show_bug.cgi?id=768564
opensuse 12.2 detects my wireless connection after a fresh install. I enter the required security code and use firefox with no issues but after I shut down or restart the machine (dell latitude d510), the wireless connection does not work and my connection isn't even there within the list of the available connections. If I click on manage connections within the wlan interface, I could see my connection is listed there; but the icon next to the bottom clock indicates that I'm not connected, and even if I try firefox by then, nothing happened ...no internet. By the way, I got the same issue with opensuse 12.1. Any ideas will be hugely appreciated.
(In reply to comment #7) > 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
Thanks a lot guys. I found another workaround which seems to work for me. Uncheck connect automatically and delete your saved name in the network management. Click apply and OK. After that, every time you start your machine, click on the connection icon in the bottom right corner next to the clock; you will find your connection listed among the available connections; click on it and voilà, you're surfing again.
I think the problem resides in the "connect automatically" option; opensuse 12.2 seems unable to connect automatically to a network which is not listed in the WLAN Interface because what happened when we first connect to a certain network is that the system saved it inside the network management and deletes it from the wlan interface. So here the system faces a contrast: how can it connect automatically to a network which is not listed in the wlan interface? That's why when we uncheck the "connect automatically" option, the user's network is shown again in the wlan interface and thus by clicking on it, the connection is established again. So the connection has to be established manually, instead of automatically, every time the user starts his machine.
(In reply to comment #10) > 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.
Looks like the bug made it into 12.2 final. I did a fresh install. After connecting/disconnecting once to an AP, the networkmanager applet fails to list the AP until networkmanager is restarted. I also tried NetworkManager-gnome with the same result.
Let's focus on one bug report :-) *** This bug has been marked as a duplicate of bug 768564 ***