Hm, working for me here. As root, please run /usr/libexec/nm-openconnect-service in a terminal, and paste its output when you try to connect to the VPN.

David,

I used the command and it did not show any output.  I have tried this on two of my 64bit installs and it is working fine with no problems.  I am thinking I might have a bad LiveCD and some libs got corrupted.  I will reinstall and test again.  Thanks Nathan

David,

Tried it on another i686 install and it does the same thing as the previous one does.  

Dec  8 12:32:55 nc5516laptop NetworkManager: <info>  Starting VPN service 'org.freedesktop.NetworkManager.openconnect'...
Dec  8 12:32:55 nc5516laptop NetworkManager: <info>  VPN service 'org.freedesktop.NetworkManager.openconnect' started (org.freedesktop.NetworkManager.openconnect), PID 3340
Dec  8 12:32:55 nc5516laptop kernel: tun: Universal TUN/TAP device driver, 1.6
Dec  8 12:32:55 nc5516laptop kernel: tun: (C) 1999-2004 Max Krasnyansky <maxk>
Dec  8 12:32:55 nc5516laptop kernel: vpn0: Disabled Privacy Extensions
Dec  8 12:32:55 nc5516laptop NetworkManager: <info>  VPN service 'org.freedesktop.NetworkManager.openconnect' just appeared, activating connections
Dec  8 12:32:55 nc5516laptop NetworkManager: <info>  VPN plugin state changed: 1

NetworkManager just sits and shows like it is trying to connect.  It does not pop up the login window like on the 64bit installs.

Thanks

Run 'strace nm-openconnect-service' instead. Does it do _anything_ when you try to connect?

Can you kill nm-applet and run that from a terminal too. Is there any relevant output?

Also try running the authentication dialog manually. You need to find the UUID for your connection, by running 'gconftool-2 --dump /system/networking/connections | less'. Find the openconnect VPN connection, and note the UUID for it; it's a long hex string with a few dashes in it. Then run

/usr/libexec/nm-openconnect-auth-dialog -u $UUID -n vpn-i-ha02 -s org.freedesktop.NetworkManager.openconnect

(replacing $UUID with the correct value, of course).

Btw, if nm-openconnect-auth-dialog spits out a cookie when you run it successfully, don't put it in here without obscuring it. That cookie is enough for anyone to log in to your server (for as long as the session lasts).

When running nm-applet from the command line, I get this when trying to connect with openconnect.

[ncrubel@nc4530laptop ~]$ nm-applet

** (nm-applet:2529): WARNING **: handle_property_changed: property 'vpn-state' changed but wasn't defined by object type NMVPNConnection.
*** glibc detected *** /usr/libexec/nm-openconnect-auth-dialog: malloc(): memory corruption: 0x09967760 ***

yum --enablerepo=rawhide update openconnect

Does the problem persist?

Transaction Check Error:
  file /etc/vpnc/vpnc-script from install of vpnc-script-0.5.3-7.fc13.noarch conflicts with file from package vpnc-0.5.3-4.fc12.i686


Getting error when trying to update.

update vpnc too then

That worked, I am able to connect.  

Thanks

Thanks for testing. When CVS comes back, I'll update the F-12 package.

David,

I found a big problem, when I restarted the machine I updated to, the Linux kernel hangs and does not start.  There are no messages.  This has happened to two machines after I installed the Fedora 12 openconnect and vpnc.  I had to reinstall Linux on those two machines for work, but tonight I will do it in a VM and see if it does it again.  The PC's started and worked fine until I did the update.

Thanks

nathan

openconnect-2.12-1.fc12 has been submitted as an update for Fedora 12.
http://admin.fedoraproject.org/updates/openconnect-2.12-1.fc12

Precisely what packages got updated when you installed the rawhide openconnect package?

It should only have installed openconnect, vpnc and vpnc-script.

Please also show _exactly_ what happens when the kernel 'hangs'. What is the last output you see?

I suspect you've updated the kernel too, and the rawhide kernel is crashing. You ought to be able to select the F12 kernel from the boot menu.

David,

The kernel does nothing, and it does not put out any output.  It was using the latest Fedora 12 kernel.  I will get the packages tonight when I install it in a VM and see what else I can get for you. 

I tried to use the 3 older kernels and they did the same thing.  

After grub, it goes to a blinking - and does nothing.  No output, for about 30 secs, you can hit enter and type but after 30 seconds, it does not take any keyboard commands.  

Thanks

Nathan

Created attachment 378661 [details]
Screen shot of starting VM with openconnect upgrade in rawhide

Updating:
 openconnect         i686           2.12-1.fc13           rawhide          65 k
 vpnc                i686           0.5.3-7.fc13          rawhide          76 k
Installing for dependencies:
 vpnc-script         noarch         0.5.3-7.fc13          rawhide          11 k
Updating for dependencies:
 upstart             i686           0.6.3-3.fc13          rawhide         222 k

Here is what it isntalled.  I attached a screen shot also.

I got a little more info, but the VM hangs.  The VM was working fine before I upgraded the openconenct and vpnc from rawhide.  

Thanks

Nathan

(In reply to comment #15)
> After grub, it goes to a blinking - and does nothing.  No output, for about 30
> secs, you can hit enter and type but after 30 seconds, it does not take any
> keyboard commands.  

Um, that wasn't entirely true, now was it? The picture shows that there _is_ kernel output, and that there's a problem with init starting up... which is hardly surprising, since for some reason the latest vpnc depends on rawhide's shiny new exciting and broken version of upstart. Sorry about that; I didn't realise it would happen.

You should be able to fix the offending system(s) by booting from the install CD in rescue mode and removing the vpnc package (you only wanted vpnc-script anyway), and downgrading upstart to the Fedora 12 version.

I've built an update package for F-12 now:
http://koji.fedoraproject.org/koji/buildinfo?buildID=146993

David,

Thanks for you help.  I was suprised the VM gave output also, my netbook did not do anything or did my nettop.  They would do the blinking thing and no text, but I think it would be doing the samething as the VM.

Nathan

> 
> I've built an update package for F-12 now:
> http://koji.fedoraproject.org/koji/buildinfo?buildID=146993  

That version works with no problems.  Thanks

openconnect-2.12-1.fc12 has been pushed to the Fedora 12 stable repository.  If problems still persist, please make note of it in this bug report.