Bug 320941
Summary: | crashes when adding new openvpn connection | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Andy Grover <andy.grover> | ||||||||||||
Component: | NetworkManager-openvpn | Assignee: | Tim Niemueller <tim> | ||||||||||||
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||
Severity: | high | Docs Contact: | |||||||||||||
Priority: | low | ||||||||||||||
Version: | rawhide | CC: | adv, anuar, bugs, carlos.labarca, cbuckley, charkins, daniel.challen, daves, edoutreleau, ernstp, ezradibiase, jsmith.fedora, mike, mk, mohd.izhar.firdaus, narf, peter, renato.ramonda, roger, stanislav.polasek, steve, wheeee | ||||||||||||
Target Milestone: | --- | ||||||||||||||
Target Release: | --- | ||||||||||||||
Hardware: | All | ||||||||||||||
OS: | Linux | ||||||||||||||
Whiteboard: | |||||||||||||||
Fixed In Version: | 0.7.0-6.svn3169.fc8 | Doc Type: | Bug Fix | ||||||||||||
Doc Text: | Story Points: | --- | |||||||||||||
Clone Of: | Environment: | ||||||||||||||
Last Closed: | 2008-01-22 15:37:16 UTC | Type: | --- | ||||||||||||
Regression: | --- | Mount Type: | --- | ||||||||||||
Documentation: | --- | CRM: | |||||||||||||
Verified Versions: | Category: | --- | |||||||||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||
Embargoed: | |||||||||||||||
Attachments: |
|
Description
Andy Grover
2007-10-05 22:20:07 UTC
Does create mean create a new connection entry or establishing a connection? And is dropdown deleting a connection entry or tearing down a connection? Sorry, "creating" and "dropdown" suggest that you mixed operations and I just want to make sure... creating a new connecion entry. 1) Click NetworkManager applet, VPN connections, Configure VPN 2) Click Add 3) Click forward 4) Select "openvpn client" and click forward 5) Bug buddy pops up I have the same thing, with the following versions: openvpn-2.1-0.19.rc4.fc7 NetworkManager-0.7.0-0.3.svn2970.fc8 NetworkManager-openvpn-0.3.2-7.fc6 I'm following the same steps as Andy is in comment number 2 above. Created attachment 248341 [details]
Bug Buddy bug report for nm-vpn-properties
Now that the package has been rebuilt for F8, I've tried again: openvpn-2.1-0.19.rc4.fc7 NetworkManager-0.7.0-0.5.svn3030.fc8 NetworkManager-openvpn-0.7.0-2.svn3047.fc8 This time, I do the following: 1) Click NetworkManager applet, VPN connections, Configure VPN 2) Click Add 3) Click forward 4) Select "openvpn client" and click forward 5) Under "Connection Name", I type "test" 6) The second I start typing in the "Gateway Address" box, it crashes. I've attached the results of Bug Buddy, if they're of any use. I've also tried this on Fedora 8 PPC, and it has the exact same problem. Also, I noticed that if you *first* add the gateway address, the program crashes when you start typing in the "Connection Name" box. These two text boxes are somehow linked to the crash. Nothing else in the dialog seems to matter. Confirmed. I'm looking at it. *** Bug 376491 has been marked as a duplicate of this bug. *** *** Bug 384331 has been marked as a duplicate of this bug. *** *** Bug 384331 has been marked as a duplicate of this bug. *** *** Bug 384091 has been marked as a duplicate of this bug. *** Hi Tim, The error is inside impl_is_valid() in nm-openvpn.c Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1208173712 (LWP 23915)] 0x00200c8e in impl_is_valid (self=0x9839650) at nm-openvpn.c:557 557 if ( (strlen (connectionname) == 0) || Appears to be a null pointer for the 'port' item, presumably because the entry field is no longer in that dialog (there's also a null pointer for routes_entry lurking).. *** Bug 372721 has been marked as a duplicate of this bug. *** I have added a patch which fixes that problem. During investigation it became obvious once more that NM is currently in flux. So please test this version and report if it is not working (due to other reasons, can't test right now by myself). You can find the packages at http://koji.fedoraproject.org/koji/buildinfo?buildID=25302. Please try and let me know if it works for you. Created attachment 267591 [details]
bug buddy crash log
crash when saving conf.
The crash of the first dialog appears to be fixed. Now it crashes when confirming the configuration (saving). (see the above attached file) (In reply to comment #16) > The crash of the first dialog appears to be fixed. Now it crashes when > confirming the configuration (saving). > > (see the above attached file) I too can confirm this. See my attached. Created attachment 267601 [details]
crash on save
Ok, will check this tonight. *** Bug 398001 has been marked as a duplicate of this bug. *** *** Bug 395931 has been marked as a duplicate of this bug. *** One of the problems is that the advanced settings dialog is not getting loaded from the glade XML file (the patched rpms linked to above work around these crashes, but don't actually solve the problem). However, fixing that still causes crashes in a couple other places. Hopefully I'll get it figured out and can get a patch up here soon. I'd really appreciate that as my current time constraints do not permit to work on this as much as I want... I don't know if this is the same bug I see: This is on a x86_64 system. If I add a new VPN entry, fill in Connection Name, Gateway, and group name, press Forward, press Apply, then nothing happens. The new entry doesn't show up in the list. I've done this many times before on F7 i386. The patched version mentioned in comment #14 makes no difference. I have exactly the same problem as in previous comment. No only it does not save the connection settings, but if I define the vpn and then go back from the "Finished Create VPN Connection" window, the entered settings disappear and the "Create VPN connection 2 of 2" window is empty again. x86_64 arch, too. Hold tight guys. There are a number of issues in the openvpn plugin, but I'm very close to getting them all resolved. I've successfully connected to the vpn with my changes, but the remote address was hard coded and the vpn routes are not getting set up. I'll submit the changes upstream when I've got these last few quirks figured out and I suspect they'll push an update after that. This should be fixed in trunk now with revisions 3140 and 3162. There were a number of other openvpn issues that have been dealt with as well. Great, going to package this tonight. I have built new packages incorporating Casey's patches and the patch for the NULL pointer checks that was originally added as patch to the RPM and is now upstream. You can get the RPMs from http://koji.fedoraproject.org/koji/buildinfo?buildID=27997. Please let me know how it goes. with the updated (svn3169) RPM I can now define an OpenVPN connection, and it is added to the list. Immediately after defining it I can highlight it in the list and click Edit: the dialog appears but only the connection name field is populated, all other fields are blank. If I click the Edit button for an OpenVPN connection any other time after the initial creation, no window appears, and the window listing connections closes. Trying to initiate one of these OpenVPN connections triggers a log message: NetworkManager: nm_vpn_connection_activate: assertion `nm_vpn_connection_get_state (connection) == NM_VPN_CONNECTION_STATE_PREPARE' failed NetworkManager: nm-vpn-connection.c.661: NeedSecrets failed: g-exec-error-quark Could not process the request because the VPN connection settings were invalid. In x86_64 the error is the same When I save the connection appears the next error ** (nm-vpn-properties:4282): CRITICAL **: nm_gconf_set_valuehash_helper: assertion `value != NULL' failed *** Bug 426203 has been marked as a duplicate of this bug. *** Casey, Tim... Thanks for your effort in trying to get this working. Unfortunately, the fix doesn't completely fix the problem. While it no longer crashes while defining a new VPN connection, it crashes NetworkManager when I try to use a VPN connection I've defined. I'm on PPC, for what it's worth. Jared: Can you confirm your package versions for NetworkManager, NetworkManger-gnome and NetworkManager-openvpn? Also, can you install the debuginfo versions of the packages and post the debug log here. I've been running with these patches applied for a number of weeks without any problems. *** Bug 426768 has been marked as a duplicate of this bug. *** daves Created attachment 290432 [details]
BugBuddy Report from 2007-12-26 19:37
Created attachment 290446 [details]
nm-applet bug report
Same thing here...
Hi, are any new builds for NM-openvpn approaching? tim, if you need a helping hand for building I could take a little time to become a comaintainer or someting. Today I received updated NM (main) packages (version svn3138) from fedora updates, and together with the (unreleased) NM-openvpn version svn3169.f8 I took from koji it seems to work. I'll test it this evening, or tomorrow. At the moment it seems there are come issues with disconnecting (lots of CPU cycles, for seconds, and then the connection is down BUT the icon still shows a red X (and not a locked padlock, go figure). Updated NM to the latest svn3138 then installed the NM-openvpn svn3169 package. I've successfully tested openvpn using Password Authentication. It finally works! Good work guys! There's one thing I'd like to add. VPN is working great. One thing that bothers me is the route table config. Upon connecting, NM removes my previous default gateway and doesn't set a route for the VPN subnet. This causes me to lose my regular internet without redoing the route table. After fixing my route table I have access to both VPN and regular internet. My VPN is not set for NAT and is not set to redirect-gateway so as far as I know its NM doing this. Am I wrong? Michael: I'm aware of that problem and am hoping to get it fixed. You can work around this by going to the advanced openvpn settings, checking the "only use vpn connection for these addresses" and entering the subnets you want to use the vpn for. There are a few other openvpn issues I hope to address as well, but it'll be a few weeks before I'll have time to start addressing them. As for this particular bug, it sounds like it could be closed out. Any other new issues should be filed as new bugs. See pending update at https://admin.fedoraproject.org/updates/F8/pending/NetworkManager-openvpn-0.7.0-6.svn3169.fc8 NetworkManager-openvpn-0.7.0-6.svn3169.fc8 has been pushed to the Fedora 8 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update NetworkManager-openvpn' With svn3169 adding a connection, editing it etc. works fine for me. However using a non-standard port-number (e.g. 443 instead of 1194) seems to be a problem. I can enter it in the advanced dialog, it even gets exported correctly when I export the VPN-entry. However both upon editing the entry and upon connecting it still uses port 1194. Is there any workaround to at least get it to connect to the correct port? When I change the port on the server to 1194 and try to reconnect I get SIGTERM[hard,init_instance] received, process exiting Does than mean something crashed during connect? I hv the exact same problem with Stefan Neufind Thanks Stefan and Syamsul, I'll take a look when I get back from a couple weeks of traveling. Glancing over the code, it looks like it should be using the port, but testing shows it clearly isn't. Please file a new bug for the port problem. If there are no more comments on this I'll mark the update as stable and close this bug. The updates appear to fix the problems I had initially, thank you, however I can't fully test as I'm getting a SELinux denial when OpenVPN tries to access my X.509 certificate files in /home/dan/vpn_certs/ . I'll open a new bug on that. There is already bug 214556 for this. A good solution has not been implemented, yet. We probably need the blog transmission via dbus as it is done for the WPA Enterprise CA. NetworkManager-openvpn-0.7.0-6.svn3169.fc8 has been pushed to the Fedora 8 stable repository. If problems still persist, please make note of it in this bug report. I still have problems: could not create VPN (with opevpn). These are my packages: NetworkManager-gnome-0.7.0-0.6.7.svn3204.fc8 NetworkManager-vpnc-0.7.0-0.6.3.svn3109.fc8 NetworkManager-0.7.0-0.6.7.svn3204.fc8 NetworkManager-glib-0.7.0-0.6.7.svn3204.fc8 NetworkManager-openvpn-0.7.0-6.svn3169.fc8 Thanks Ezra Hi Ezra, I had the same problem. My solution is uninstalling NetworkManager and openvpn, and install all again. It's work for me Regards Carlos Labarca |