Lost WPA Support After Updates

[ms1234]

Just updated my main laptop, doesn't seem to matter if it is Broadcom or Intel chipset, it is still broken after the update

[normski9]

Just to add to the list of chipsets with the same problem, I' ve got the same issue with a Realtec 8192.

[MicronINC]

Alright guys, I've submitted the bug, now to wait it out. Still playing around, haven't fixed it yet.

https://bugzilla.redhat.com/show_bug.cgi?id=683603

[CoolOSS]

Same problem here.
I think it is just the kde-plasma-networkmanagement update (didn't have time to try anything to gdb update).
I can't roll back, because from now on there is no knetworkmanager-libs package.

Workaround: Uninstall kde-plasma-networkmanagement -> install NetworkManager-gnome (grrr) -> run nm-applet (not again!!!) -> wpa works fine...

Still waiting for an update for kde-plasma-networkmanagement...

[MicronINC]

Good to see its working for you. Seems that the issue is in fact with kde-plasma-networkmanagement then, not NetworkManager. I recieved updates for NetworkManager that did not fix the issue for me. I have not yet broken down to installing anything gnome. If the kde package is not updated soon I might just have to.

Always hated gnome..... </grumble>

[CoolOSS]

Sort of solved...

Just enabled KDE Wallet (even if I like to have it always disabled), and now everything works!

Hopefully on next update of kde-plasma-networkmanagement I will be able to re-disable KDE Wallet...

[MicronINC]

Wow! Thats too funny. Good find, I'll try that in the meantime. Some guys have replied to the bug post asking for more info, so I'll be supplying that to them as soon as I get back to my box. Its still broken

[ms1234]

Sort of solved...

Just enabled KDE Wallet (even if I like to have it always disabled), and now everything works!

Hopefully on next update of kde-plasma-networkmanagement I will be able to re-disable KDE Wallet...

Interesting, how did you do that? I have the wallet in use for some apps and I think it should also be for knetworkmanager...

[CoolOSS]

Interesting, how did you do that? I have the wallet in use for some apps and I think it should also be for knetworkmanager...

Well, I had the wallet completely disabled, so I enabled it, deleted the stored connection from Wireless Network connections, re-entered my credentials, was asked to store in the wallet, answred yes, and everything worked...

[MicronINC]

CoolOSS nailed it. I enabled KDE Wallet and was able to connect. Seems like the way NetworkManagement handles passwords is not working correctly. It trys to re-authenticate. I set NetworkManager's "Other" settings to "Do not store secrets". Enabled KDE Wallet and configured it to use the local wallet. Looking at /var/log/messages and wpa_supplicant It seems as if I'm actually able to authenticate and connect before it fails.

Trying to associate with 00:18:39:e5:6d:1b (SSID='Burris' freq=2437 MHz)
Associated with 00:18:39:e5:6d:1b
WPA: Key negotiation completed with 00:18:39:e5:6d:1b [PTK=TKIP GTK=TKIP]
CTRL-EVENT-CONNECTED - Connection to 00:18:39:e5:6d:1b completed (auth) [id=0 id_str=]
WPA: Group rekeying completed with 00:18:39:e5:6d:1b [GTK=TKIP]
WPA: Group rekeying completed with 00:18:39:e5:6d:1b [GTK=TKIP]
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Failed to initiate AP scan.

/var/log/messages:
localhost NetworkManager[1302]: <info> Activation (wlan0) starting connection 'Burris'
localhost NetworkManager[1302]: <info> (wlan0): device state change: 3 -> 4 (reason 0)
localhost NetworkManager[1302]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
localhost NetworkManager[1302]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
localhost NetworkManager[1302]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
localhost NetworkManager[1302]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
localhost NetworkManager[1302]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
localhost NetworkManager[1302]: <info> (wlan0): device state change: 4 -> 5 (reason 0)
localhost NetworkManager[1302]: <info> Activation (wlan0/wireless): access point 'Burris' has security, but secrets are required.
localhost NetworkManager[1302]: <info> (wlan0): device state change: 5 -> 6 (reason 0)
localhost NetworkManager[1302]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
localhost NetworkManager[1302]: <info> (wlan0): supplicant connection state:  scanning -> inactive
localhost NetworkManager[1302]: <warn> connection /org/freedesktop/NetworkManagerSettings/0 (scope 2) failed to activate (timeout)
localhost NetworkManager[1302]: <info> (wlan0): device state change: 6 -> 3 (reason 38)
localhost NetworkManager[1302]: <info> (wlan0): deactivating device (reason: 38).
localhost NetworkManager[1302]: <info> disable requested (sleeping: no  enabled: yes)
localhost NetworkManager[1302]: <info> sleeping or disabling...
localhost NetworkManager[1302]: <info> (wlan0): now unmanaged
localhost NetworkManager[1302]: <info> (wlan0): device state change: 3 -> 1 (reason 37)
localhost NetworkManager[1302]: <info> (wlan0): cleaning up...
localhost NetworkManager[1302]: <info> (wlan0): taking down device.

So it looks like the update from kde-plasma-networkmanagement 0.9-0.28x to 0.9-0.35x did it. Lets see if the next update fixes it. Thanks for your help guys.

[ms1234]

Well, I had the wallet completely disabled, so I enabled it, deleted the stored connection from Wireless Network connections, re-entered my credentials, was asked to store in the wallet, answred yes, and everything worked...

Thanks, got it working now. I had to remove the existing wallet entry and the wlan entry in networkmanager and then reconnect.

[worzie]

Sort of solved...

Just enabled KDE Wallet (even if I like to have it always disabled), and now everything works!

Hopefully on next update of kde-plasma-networkmanagement I will be able to re-disable KDE Wallet...

Thanks for the fix CoolOSS! I originally disabled it as it was a nuisance having to enter a wallet password. Small price to pay if it's still that way.

[Simian Man]

The update fixing this issue made its way into updates-testing. To fix it, just:

yum --enablerepo=updates-testing update kde-plasma-networkmanagement

This will probably be pushed into updates in a few days .

[MicronINC]

I've installed the new update packages with yum:

kde-plasma-networkmanagement-0.9-0.39.20110314.fc14.x86_64.rpm
kde-plasma-networkmanagement-libs-0.9-0.39.20110314.fc14.x86_64.rpm

They can be downloaded from:
http://koji.fedoraproject.org/koji/b...buildID=233740

Simian Man's method is cleaner, I wish I had checked here first instead of the bugzilla update!!!

According to Jirka Klimes on KDE forums:

When 'Connection Secrets' are configured to be stored as "In file (unencrypted)",
connecting to WiFi networks is not successful and stalls at "Waiting for authorization".

That is caused by not replying to GetSecrets() D-Bus call from NM. The problem is that
the WiFi connection contains Security8021xSetting even if it's not used (though it's
maked as not enabled). So we need to honour the enabled state of Security8021xSetting
in Connection::secretsAvailable().

Thanks for everybody's input on this thread