Edit OpenVPN Connectionin Kubuntu Jaunty - multiple UI issues, is useless

Binary package hint: network-manager-openvpn

Can't even get off the starting blocks with this one!

Computer- Kubuntu 64-bit, originally Hardy then upgraded a week ago through Intrepid to Jaunty. OpenVPN connection through the little applet worked in Hardy.

dpkg -s shows:
  network-manager: 0.7.1~rc4.1.cf199a964-0ubuntu2
  network-manager-kde 1:0.7svn864988-0ubuntu8
  network-manager-openvpn: 0.7.1~rc4.1.20090323+bzr27-0ubuntu2
  networkstatus: 4:3.5.10-0ubuntu1~hardy3.1 (relevance of this?)
  plasma-widget-network-manager: 0.0+svn930811-0ubuntu2

lsb_release -rd shows: Ubuntu 9.04 / release 9.04
uname -srmv shows: Linux 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:58:03 UTC 2009 x86_64

(This is I hope reasonably vanilla Jaunty with all available updates as at 2009-04-28)

To reproduce:
 1. Right click NM applet on Plasma panel, Select "Manage connections"
 2. Go to VPN tab, select "Add" -> OpenVPN

Observed:
  Connection name: "New VPN Connection" (remember this fact)
  Gateway: (blacnk, ok)
  Connection Type: X.509 Certificates
  CA File: __________________ + open file
  Username: ______
  Password: _______

BAD #1: Connection type is X.509 certs but it is asking for username and password? If you select a different connection type (eg preshared key) then back to X.509 certs, then appears as expected:

  CA File: ___________________ [file button]
  Certificate: __________________ [file button]
  Key: _______________________ [file button]

So anyway
3. Toggle the connection type to get the right boxes, Set Connection name to say "Test One"
, gateway, and pick the CA Cert, user cert & key Save and OK out of the
4. Single-click on on network status icon
Observed:
  Under "VPN Connections" heading is "Test One" - so far ok.

5. Right click on network status icon and select "Manage Connections", VPN tab, select Test One, and click EDIT

Observed:
  Connection Name: Test One (OK) , Gateway: as before (OK), Connection type: X.509 Certs.

But ... have CA File, Username and Password boxes again (BAD #1 again)
<sigh>

6. Change connection type to Pre-shared-key and back to X.509 certificates

Observed: CA file and (user) Certificate have come back to stored values, but Key field is empty. (BAD #2)

7. Pick the key file again. Also change the connection name to "Test Two", Click OK / OK out.

8. Single click on Network status icon

Observed :
  Under the VPN connections, it is still listed as "Test One" (BAD #3)

<sigh again>

9. Right click / Manage connections /VPN/ Test Two (as it is) / Edit
10. Go through all the rigmarole of ensureing the Certificate / key files are set
11. Click on "Optional Information" tab
Observed: Port ___ [X] "Use default" is checked, nothing else is checked, all other fields disabled (OK so far but...

12a. Uncheck Use default port - > Port # textbox does not enable
12b. Check "User cipher" -> combo box does not enable
12c. Check "Use TLS Auth" -> nothing changes
12d Check "Only use VPN for these addresses" -> edit box does not enable
 BAD #4

Summary
BAD #1 = Initial state of fields for Certificate files/credentials are wrong (should match whatever initial connection type). On New and edit.

BAD #2 = Value of "Key file" apparently not remembered (may be symptom of #1, but it remembers the others)

BAD #3 = popup from Network Status icon shows old name even if connection renamed (not sure when it resets, restart of widget?)

BAD #4 = Nothing seems to work on the "Optional Information" tab

The combination of these pretty much eliminates any attempt by me to use this to attach to my OpenVPN server. I can't even be bothered with it, sorry. (I did write up this bug report though so hopefully the last hour is not completely wasted).