NetworkManager plasma widget does not retrieve saved WiFi keys from kwallet

[Simon Farnsworth]

I'm using the Jaunty beta, and finding that the new Network Manager plasma thingy doesn't retrieve saved WEP keys.
$ lsb_release -rd
Description: Ubuntu jaunty (development branch)
Release: 9.04
$ apt-cache policy plasma-widget-network-manager
plasma-widget-network-manager:
  Installed: 0.0+svn930811-0ubuntu2
  Candidate: 0.0+svn930811-0ubuntu2
  Version table:
 *** 0.0+svn930811-0ubuntu2 0
        500 http://gb.archive.ubuntu.com jaunty/main Packages
        100 /var/lib/dpkg/status

I have a WiFi network which shows up in iwlist scan output as:
          Cell 02 - Address: 00:0C:42:2C:46:9D
                    ESSID:"FarnzPrivate5GHz"
                    Mode:Master
                    Channel:36
                    Frequency:5.18 GHz (Channel 36)
                    Quality=77/100 Signal level:-36 dBm Noise level=-67 dBm
                    Encryption key:on
                    IE: Unknown: 00104661726E7A507269766174653547487A
                    IE: Unknown: 01088C129824B048606C
                    IE: Unknown: 030124
                    IE: Unknown: 072A4742202401142501142601142701142801142901142A01142B01142C01142D01142E01142F0114300114
                    IE: Unknown: DD180050F2020101000003A4000027A4000042435E0062322F00
                    Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s
                              36 Mb/s; 48 Mb/s; 54 Mb/s
                    Extra:tsf=0000000000000000
                    Extra: Last beacon: 3308ms ago

I left-click the plasma icon for NetworkManager, and select "FarnzPrivate5GHz" from the list that pops up. This brings up a dialog, asking for my WEP key, which I fill in. I can right-click the icon, select "Manage Connections", and see the connection I just added in the Wireless tab; selecting it and clicking "Edit" on the right lets me confirm that the key has been saved correctly.

I then reboot, using the Leave tab of the Application Launcher, and selecting Restart (yellow icon). Again, checking the connection with "Manage Connections" confirms that the key is saved correctly. When I attempt to connect again, by selecting FarnzPrivate5GHz in the list that pops up when I click the plasma icon, I'm prompted for my key again. Entering it creates a new connection in the "Manage Connections" dialog.

I would expect that Kubuntu would attempt to use the key I saved before to reconnect, and to not prompt me unless that key failed to work.

[Xavier Charpentier (x-charpentier)]

I'im also using Jaunty beta and I can confirm this bug.
The first time I used the plasma connection manager it called kwallet to store the WPA key. At startup the plasma connection manager calls kwallet to get the key and connects properly.
However If kwallet is disabled the connection manager will keep asking for the key and never connect.
In the KDE Control Module -> Network settings -> Network management -> Wireless in can see the connection and the key seems to be saved but the plasma network manager will keep asking for it and never connect...
This is terribly annoying...

[naught101 (naught101)]

I get this too. Annoying.

[giacof (giacof)]

Confirmed on Jaunty beta.
I really cannot figure out why on the "Manage network connections" panel there is no "connect" button to quickly connect to any configured network.
Seriously considering to switch to wicd.

[Andreas Scherbaum (ads-launchpad)]

This - and other - bugs renders the plasma widget useless.
I cannot and will not remember all passwords for wireless networks and retype the password each time i connect.

Pity that the old knetwork manager seems not to work either.

[naught101 (naught101)]

nm-applet (gnome) works fine for me - it's a good workaround. It won't start if you have knetworkmanager or the plasma widget running.

[Andreas Scherbaum (ads-launchpad)]

Yeah, but i don't want workarounds, i want working software ;-)

[Simon Farnsworth (ubuntu-farnz)]

Something in recent updates appears to have fixed this for me. Don't know what, as the applet version hasn't changed.

[berk (berkulsoy)]

This still happens in official release. I expect that when I click a wireless network, network manager should try connecting if there is a saved setting for that ssid and ask details only if it is used first time or settings are not valid anymore.