Bugzilla – Bug 771582
Networkmanager-kde4 doesn't handle well some networks
Last modified: 2012-09-09 22:06:35 UTC
Hello, I've got openSUSE 12.2 on my laptop using KDE. If I'm using the "Novell" wireless network all works well not problems there, but if I'm using my home wireless network which is WPA2 Personal, at every start-up or reboot or logout I have to delete the network from the list, re-add the network and then everything works. If I have it already setup, then I logout and then login again, I have to delete the network, disable my wireless device, enable it and then add again the wireless network. Problem is that after logout and login, the network is still in the list, Networkmanager doesn't connect to it and doesn't see anymore my network until I run the above steps. NOTE: The same thing doesn't happen with the Novell network which we have in SUSE. Doesn't matter if I logout/login, reboot, shutdown and so on.
Because I've ran: osc maintainer openSUSE:12.2 NetworkManager-kde4 and I got: maintainer of openSUSE:12.2 : coolo, lnussel, namtrac
Hi Robert, Could you do the following steps to get the NetworkManager log? 1) Change the logging level to "DEBUG" $ sudo dbus-send --system --print-reply --dest=org.freedesktop.NetworkManager /org/freedesktop/NetworkManager org.freedesktop.NetworkManager.SetLogging string:"debug" string:"" 2) Change the log domain: $sudo dbus-send --system --print-reply --dest=org.freedesktop.NetworkManager /org/freedesktop/NetworkManager org.freedesktop.NetworkManager.SetLogging string:"info" string:"wifi_scan,wifi,supplicant,core,dhcp4,ip4" 3) Reproduce the bug and attach the diff of /var/log/NetworkManager
Created attachment 499617 [details] NetworkManager log file with debugging enabled I've attached the NetworkManager log file, its just 5kb. It's totally fresh.
The log showed the system connected to the AP in the end. Did the issue happen when you collect the log? BTW, the dbus-send commands in comment#3 can be combined as $ sudo dbus-send --system --print-reply --dest=org.freedesktop.NetworkManager /org/freedesktop/NetworkManager org.freedesktop.NetworkManager.SetLogging string:"debug" string:"wifi_scan,wifi,supplicant,core,dhcp4,ip4" Please use the above command when you need to collect the log. Sorry for the confusion.
Created attachment 500735 [details] NetworkManager.log.gz OK, I've realised today that restarting the network also fixes the issue: doing sudo /etc/init.d/network restart also is a fix. I've also attached the logs with both of the methods of fixing the issue, one remove the wifi network, disabled the wifi device, re-enable, re-add the network and then second method with restarting NetworkManager.
I found the key message: <warn> No agents were available for this request. <info> (wlan0): device state change: need-auth -> failed (reason 'no-secrets') [60 120 7] NM tried to get the PSK password but failed. The settings were stored this file: /etc/NetworkManager/system-connections/Kongoni If there is a "permissions" entry in the [connection] section, it's a private connection, and the password is kept in the user's password agent, e.g. gnome-keyring for gnome or kwallet for kde, so this may be an issue of the kde NM client. If there is no such entry, it's a system connection, and you will find your psk password in the [802-11-wireless-security] section. In this case, I will need to find a way to make NM print more code trace. Could you check the file to clarify the issue?
rmilasan@coolcat:~> sudo cat /etc/NetworkManager/system-connections/Kongoni |grep permissions permissions=user:rmilasan:; rmilasan@coolcat:~> sudo cat /etc/NetworkManager/system-connections/Novell |grep permissi permissions=user:rmilasan:; As you can see its for both Novell and Kongoni, but the Novell setup always works, only the Kongoni one doesn't. Its highly possible a KDE NM client issue.
Reassign to kde-maintainers for further investigation.
When it fails to connect, does the Kongoni network appear in the list of available connections in the NM-kde4 popup? Or does it only show a substring of "Kongoni"? Does "nm-tool" show Kongoni?
No, it doesn't appear anymore in the NM-kde4 popup. I haven't tried nm-tool, but I can do this home.
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=774934 https://bugzilla.novell.com/show_bug.cgi?id=758121 https://bugzilla.novell.com/show_bug.cgi?id=768564
*** Bug 774934 has been marked as a duplicate of this bug. ***
Looks like the bug made it into 12.2 final :-/ I did an upgrade from 12.1 (12.1 was a fresh install) on my: Thinkpad x220 (Type 4291-36G) CPU: Intel i7-2620M OS: openSUSE 12.2 x86_64 Wireless: Intel Centrino Advanced-N 6205 (driver iwlwifi) My wireless network (the one I'll be talking about): WPA2 (CCMP), 62 ASCII digits password Wireless Router: FRITZ!Box Fon WLAN 7360 Router vendor: AVM ( https://en.wikipedia.org/wiki/AVM_GmbH ) Router firmware: FRITZ!OS 05.09-21867 Workarounds 1, 3 and 4 from comment#c12 worked but this isn't a solution for my mum's and fathers notebooks. Also the system-connection thing isn't because I don't like to tell them stuff like "set the system-connection flag when adding a wireless". Usually people forget things like this and start to call me :-/ The other bug-reports comment#12 mentioned look quite similar. There are also some log-outputs in the other bug-reports that might help. Some new findings: I used the openSUSE 12.2 GNOME x86-64 LiveCD to boot my notebook (same notebook as before, but LiveCD > NO installation) and I got the same results in GNOME as in KDE! 1. Setting up my wireless network and the notebook logged into the network. 2. Logged out the GNOME session and logged in again. No automatic connection to my network and my wireless doesn't shows up in the list. 3. Switched off wireless in the network-manager gui (like workaround 3 from comment#12 ) and switched it on again. After a few seconds my wireless network became active. Did one more test with the openSUSE 12.2 KDE x86-64 LiveCD. Same results as in GNOME! And one more test with my installed (not LiveCD) openSUSE 12.2 and KDE 12.2: I deleted my wireless network from the network manager configuration and changed the encryption on my wireless router from WPA2 to "none". After that I connected my notebook to the wireless again (made new settings in network manager). The result was similar to the WPA2 network with one exception: After a reboot the wireless was connected! But after stopping the connection (clicking the red cross in KDE networkmanager) my wireless didn't reappeared in the network list. I had to disable wireless connections in the KDE networkmanager and to enable it again to see my wireless network in the list. I also checked if the unencrypted wireless was connected directly after reboot, before I log into KDE (like a system connection). But it wasn't! So this seems to be a NetworkManager bug. Not (just but maybe also) a KDE bug. Wireless is a major feature for the desktop experience. So please get a fix! If I can help with any information, please tell! Thanks kolAflash
This bug is assigned but I have already set some bugs as duplicate of #768564. I hope you don't mind. *** This bug has been marked as a duplicate of bug 768564 ***