I use kde trunk... just in case...S | Name                        | Type    | Version                    | Arch   | Repository                                              
--+-----------------------------+---------+----------------------------+--------+---------------------------------------------------------
i | NetworkManager              | package | 0.9.4.0-151.5              | x86_64 | rwooninck's Home Project (openSUSE_Factory)             
i | NetworkManager-kde4-lang    | package | 0.9.60git.1336635528-372.1 | noarch | home:rwooninck:UNSTABLE_KDE4 (KDE_Qt48_openSUSE_Factory)
i | NetworkManager-kde4-libs    | package | 0.9.60git.1336635528-372.1 | x86_64 | home:rwooninck:UNSTABLE_KDE4 (KDE_Qt48_openSUSE_Factory)
i | NetworkManager-lang         | package | 0.9.4.0-151.5              | noarch | rwooninck's Home Project (openSUSE_Factory)             
i | NetworkManager-openvpn      | package | 0.9.4.0-1.3                | x86_64 | openSUSE-Factory-Oss                                    
i | NetworkManager-openvpn-kde4 | package | 0.9.60git.1336635528-372.1 | x86_64 | home:rwooninck:UNSTABLE_KDE4 (KDE_Qt48_openSUSE_Factory)
i | NetworkManager-openvpn-lang | package | 0.9.4.0-1.3                | noarch | openSUSE-Factory-Oss                                    
i | NetworkManager-pptp         | package | 0.9.4.0-1.3                | x86_64 | openSUSE-Factory-Oss                                    
i | NetworkManager-pptp-kde4    | package | 0.9.60git.1336635528-372.1 | x86_64 | home:rwooninck:UNSTABLE_KDE4 (KDE_Qt48_openSUSE_Factory)
i | NetworkManager-pptp-lang    | package | 0.9.4.0-1.3                | noarch | openSUSE-Factory-Oss                                    
i | glib-networking             | package | 2.32.1-1.2                 | x86_64 | openSUSE-Factory-Oss                                    
i | glib-networking-lang        | package | 2.32.1-1.2                 | noarch | openSUSE-Factory-Oss                                    
i | kdenetwork4-filesharing     | package | 4.8.42-7.2                 | x86_64 | home:rwooninck:UNSTABLE_KDE4 (KDE_Qt48_openSUSE_Factory)
i | libQtNetworkManager0        | package | 0.5.0git.1332199137-275.1  | x86_64 | home:rwooninck:UNSTABLE_KDE4 (KDE_Qt48_openSUSE_Factory)
i | libproxy1-networkmanager    | package | 0.4.7-12.3                 | x86_64 | openSUSE-Factory-Oss                                    
i | plasmoid-networkmanagement  | package | 0.9.60git.1336635528-372.1 | x86_64 | home:rwooninck:UNSTABLE_KDE4 (KDE_Qt48_openSUSE_Factory)
i | yast2-network               | package | 2.23.0-1.1                 | x86_64 | openSUSE-Factory-Oss

here is the video showing the bug
http://www.youtube.com/watch?v=SyIhc1qMJog

*** This bug has been marked as a duplicate of bug 299379 ***

Enable all debug messages using kdebugdialog, reproduce the bug and send me the file ~/.xsession-errors.

by the way, which Plasma NM version do you use? I mean, not the package version ( 0.9.60git.1336635528-372.1), which means nothing for me since OpenSuse does not use the official version for Plasma NM (historical reasons). Look at the version in "Settings..." -> "Other".

deleted my ~/.xsession-errors
recreated it... to be sure is empty
activated all the debugs...
and tried to connect... the .xsession-errors is totally empty.
Alin

I can connect to wpa-psk networks that keep their passwords in kwallet...

the version is 0.9.1_rc1 from 20120506

You should not have deleted the .xsession-errors, the file is written by kdm and some other processes. The Linux kernel doesl not release the file's data until all process that have it opened close their file handlers. You logout and and login after deleting ~/.xsession-errors. If you compiled Qt or kdelibs without debug messages there will be no usefull messages in ~/.xsession-errors too.

Created attachment 71048 [details]
.xsession-errors attached

here is the content of the .xsession-errors... before turning wifi on.. I added a ============
so I pasted only after.

I am starting to think that the real problem is in NetworkManager or wpa_supplicant. The repeated messages like the ones below

May 12 10:35:17 abbaton NetworkManager[714]: <info> (wlan0): supplicant interface state: disconnected -> scanning
May 12 10:35:19 abbaton NetworkManager[714]: <info> (wlan0): supplicant interface state: scanning -> authenticating
May 12 10:35:19 abbaton NetworkManager[714]: <info> (wlan0): supplicant interface state: authenticating -> associating
May 12 10:35:19 abbaton NetworkManager[714]: <info> (wlan0): supplicant interface state: associating -> associated
May 12 10:35:19 abbaton NetworkManager[714]: <info> (wlan0): supplicant interface state: associated -> disconnected

indicates wpa_supplicant is not able to associate to the access point. The fact that Plasma NM is asking for password is because NetworkManager always ask for *new* password when the connection fails, even if the password is correct and something else is causing the problem. The fact that the password dialog is empty is because the current Plasma NM implementation does not know what secrets it should ask for WPA2EAP connections. I can fix the last problem but if the real problem is in NM or wpa_supplicant then it will not solve the problem with connecting to eduroam.

*** Bug 299379 has been marked as a duplicate of this bug. ***

Created attachment 71053 [details]
Patch to fix wpa2eap ask password dialog

Can you try the attached and check if it fixes the empty password dialog? There should be from one to three widgets in the dialog with this patch.

Hi,

First I will try to see if the issue is the disconnection... I will change to the wl driver instead of the opensouce b43 one.

I will  generate a package, probably tomorrow.

Alin

If you fix the problem with eduroam probably the ask password dialog will not show up anymore.

the good news which is bad forme is that I get the same issues with the wl driver too.

I still did not have time to test the patch on the secrets issue... maybe sometime today. I will keep you posted.

Alin

Git commit 6b8aaf68dddc1214c49d8201dafbbef44748b035 by Lamarque V. Souza.
Committed on 22/06/2012 at 02:16.
Pushed by lvsouza into branch 'master'.

Try to fix ask password dialog for WPA2 connections.

M  +14   -0    libs/service/secretstorage.cpp

http://commits.kde.org/networkmanagement/6b8aaf68dddc1214c49d8201dafbbef44748b035

Git commit 244649c4760794a340bfa4bfe2234b7a08e03f90 by Lamarque V. Souza.
Committed on 22/06/2012 at 02:16.
Pushed by lvsouza into branch 'nm09'.

Try to fix ask password dialog for WPA2 connections.
(cherry picked from commit 6b8aaf68dddc1214c49d8201dafbbef44748b035)

M  +14   -0    libs/service/secretstorage.cpp

http://commits.kde.org/networkmanagement/244649c4760794a340bfa4bfe2234b7a08e03f90

I compiled and installed Plasma NM 0.9.0.4 since you mentioned eduroam in this post http://lamarque-lvs.blogspot.de/2012/07/plasma-nm-0904.html on my T400 with Ubuntu 12.04 and KDE 4.8.4.
Unfortunately my personal situation has not improved. Since i'm not a kde developer (but i guess quite an advanced kde user) i would like to "help". By testing or sending logs or whatever.
Every time i use an eduroam connection it will break in an random amount of time. Only way to get it working again is to "Disable wireless" (button to the left button). Sometimes a connection stays for an hour, sometime just a minute or two. Please tell me how to help you the help me ; )

@marcnesium, the problem reported here is about the missing password field when trying to activate a wpa2 enterprise connection. Once the connection is made then it is up to NetworkManager and the wifi driver to sustain the connection until you choose to disconnect.

By what you wrote there seems to be an instabiligy in your wifi driver or access point. You should check if there are too many packet loss using the command below:

ping -s 1000 - c 60 <ip of your access point>

the '-s 1000" uses 1000 bytes packets for testing, that's overkill, but if it works ok with that packet size then it should be ok with smaller packets too. If there are more 5% of packet loss then your problem is probably related to instability in your network and there is nothing I can do about it.

@Lamarque: Thanks for answering that quickly!
Just did that test. Result: 60 packets transmitted, 60 received, 0% packet loss, time 59080ms
Perhaps i can provide some more infos: My guess is: that problem is not access point related, because that happens in two different cities at different universities (i guess different hardware, but i don't know).
I have also a problem with password entering: my password is stored by networkmanager. And when i connect for the first time every thing works fine - i don't have to enter my password and there is not dialogue popping up. But when the connection goes down after a random amount of time, a tiny little window popps up. it wants me to enter my pw, but there is no text field for that (nothing else in there, but a show the pw button). Whatever i do with this dialogue, the connection does not come up again. Like i said, disabling wireless is the only way.
What this eduroam connection uses:
WPA2 Enterprise, EAP (PEAP), PEAP version: auto, MSCHAPv2.
Wifi driver is iwlwifi.
I try to debug this connection since days... it is really frustrating. I don't know where to start.
http://pastebin.com/b5vz761Y Here is a piece of my syslog.
Any further ideas? Thanks in advance!

Ok, so your connection is rock solid in terms of packet loss. If the problem happens in more than one city then it is not a problem with access points indeed.

That "tiny little window popup" is the password dialog, the missing text field is the problem I tried to solve and that I mentioned in Plasma NM 0.9.0.4's release announcement. So the problem is not fixed, that's bad.

Even if I fix this bug with the password field you will still have to type the password everytime the connection drops or NetworkManager will never try to reconnect.

Please enable all debug messages using kdebugdialog program, reproduce the problem and send me the file ~/.xsession-errors. If you can "git pull" the repo and recompile it would be better since I added a couple of debug messages that could help me debug the problem.

Git commit 96246a4aa370873dee982846cde543091be086b6 by Lamarque V. Souza.
Committed on 30/07/2012 at 21:43.
Pushed by lvsouza into branch 'master'.

Add kDebug() calls to debug problem with missing password field with
WPA2 enterprise connections.

M  +2    -0    libs/service/secretstorage.cpp
M  +1    -1    plasma_nm_version.h

http://commits.kde.org/networkmanagement/96246a4aa370873dee982846cde543091be086b6

Git commit 4655cac5d7e06594d56b69c08256a69e38a43dda by Lamarque V. Souza.
Committed on 30/07/2012 at 21:44.
Pushed by lvsouza into branch 'nm09'.

Add kDebug() calls to debug problem with missing password field with
WPA2 enterprise connections.

M  +2    -0    libs/service/secretstorage.cpp
M  +1    -1    plasma_nm_version.h

http://commits.kde.org/networkmanagement/4655cac5d7e06594d56b69c08256a69e38a43dda

I get hit by this bug in KDE 4.9.5 on Gentoo, with NetworkManager 0.9.6.4.
My eduroam settings, see http://helpdesk.ugent.be/eduroam/eduroam_ubuntu.php
I've input my username and password, but nevertheless get a dialog to provide 'secrets' with only a selection box, but no input fields. However, I sometimes do get connected...

Yes, this bug is still present. I tried to fix it but I cannot find where is the problem. I will try to fix this problem at school where we also have eduroam.

I have fix for this problem and I hope that it works. Check https://git.reviewboard.kde.org/r/108941/

I am now up to KDE 4.10 (Using stock Chakra Benz). I have never been able to connect to my employer's wifi network working with KDE. I have no problems connecting using windows (of course) and even my android phone can connect every single time with no problems. This is definitely a bug that is still present in KDE. If anyone has a workaround please let me know. 

Thanks

Created attachment 77385 [details]
Fix missing field in password dialog

Can someone test if the attached patch fixes this problem?

Git commit 732dc9b929e3f7f5fa8691e711b2ee29195f94fe by Lamarque V. Souza.
Committed on 17/02/2013 at 19:28.
Pushed by lvsouza into branch 'nm09'.

Fix missing password field in wpa2 password dialog.
(cherry picked from commit e8726711de16f792ed4e96f5896361da0eef7d66)

M  +1    -1    libs/internals/setting.cpp
M  +1    -1    libs/internals/setting.h
M  +7    -7    libs/internals/settings/802-11-wireless-security.cpp
M  +1    -1    libs/internals/settings/802-11-wireless-security.h
M  +4    -4    libs/internals/settings/802-1x.cpp
M  +1    -1    libs/internals/settings/802-1x.h
M  +2    -2    libs/internals/settings/cdma.cpp
M  +1    -1    libs/internals/settings/cdma.h
M  +3    -3    libs/internals/settings/gsm.cpp
M  +1    -1    libs/internals/settings/gsm.h
M  +2    -2    libs/internals/settings/pppoe.cpp
M  +1    -1    libs/internals/settings/pppoe.h
M  +1    -1    libs/internals/settings/vpn.cpp
M  +1    -1    libs/internals/settings/vpn.h
M  +1    -1    plasma_nm_version.h

http://commits.kde.org/networkmanagement/732dc9b929e3f7f5fa8691e711b2ee29195f94fe

Shouldn't this bug be set as resolved?

(In reply to comment #29)
> Shouldn't this bug be set as resolved?

I was just waiting for someone to confirm the fix since I cannot reproduce it here. jgrulich has just confirmed to me that it is fixed.