abrt 1.0.0 detected a crash. Attached file: backtrace cmdline: /usr/libexec/nm-openconnect-auth-dialog -u 40ae28c9-dec7-4831-a454-1826e3195de4 -n VPN connection 1 -s org.freedesktop.NetworkManager.openconnect component: openconnect executable: /usr/libexec/nm-openconnect-auth-dialog kernel: 2.6.31.9-174.fc12.x86_64 package: openconnect-2.12-1.fc12 rating: 4 reason: Process was terminated by signal 11
Created attachment 381145 [details] File: backtrace
Hm, deep within libxml's xmlFreeDoc() function. It looks like memory corruption of some kind within libxml's data structures, which may not be libxml's fault. I've looked over our use of libxml and used valgrind, and I can't see any problems except for some memory leaks because I didn't realise certain return values needed to be freed. I've fixed that in git (http://git.infradead.org/users/dwmw2/openconnect.git/commitdiff/08731af8) but it's not likely to fix your problem. I'm assuming this happened after you entered your username and password into the dialog and hit 'login'? Can you reproduce it? You don't need to disconnect and reconnect to the VPN -- you can just run the command line above (nm-openconnect-auth-dialog -u ...) and it will just do the authentication stage. If you run 'openconnect --cookieonly $VPNSERVER' that should also use the same authentication and XML parsing code. Can you reproduce it that way?
Your right it does crash on login. But not always, usually once in every 10 tries. I am trying to figure out the exact sequence that causes it, and I will try some of your suggestions. Dan
Does this only happen if the login form has been shown more than once -- if you've mistyped your password or changed the host?
I think the answer to my question above is 'yes', and I think it's fixed by http://git.infradead.org/users/dwmw2/openconnect.git/commitdiff/5b828b68 Are you able to build from the git tree and test that, or do I need to put together a package?
http://koji.fedoraproject.org/koji/taskinfo?taskID=1899841 If you confirm that this works, I'll make a new release and push it as an update.
RPM Package would be easiest, but ill give build it a shot.
Assuming I built it right, it does seem to fix the problem. I can't entirely be sure though, as I couldn't find a reliable way to reproduce the problem.
openconnect-2.20-1.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/openconnect-2.20-1.fc12
openconnect-2.20-1.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.