The original bug as reported was a failure to import certain configuration files using network-mangaer-openvpn. This turned out to be due to the use of inlined key material (comment 24). network-manager- openvpn did not support this as a feature at the time, so was unable to parse this type of configuration file.
Support was since added (comment 46). This has been confirmed to work (comments 49, 63, 67, 68 etc). Therefore, this bug as reported has been fixed, so I'm setting it to Fix Released. It may well be that this doesn't solve configuration imports for all users, as is clear from subsequent comments. But we track one issue per bug, since otherwise statements like "this bug is fixed" and "this bug is not fixed" become meaningless, developers cannot track what they are being asked to do, and users end up with wildly varying expectations that can never be met. Note that a failure to import a configuration can be an entire class of bugs, not just one single bug. This bug's original reporter's problem turned out to be "doesn't work with inlined key material". Clearly that's not the only thing wrong here, as adding inlined key material support solved the problem for some, but not others. Of the remaining users here who still have import problems, there may yet be *multiple* underlying bugs. So please don't all pile on to a different bug thinking you're still all affected by the same issue. If you'd like to see your problem fixed, and you'd like to help, then first please read "How to Report Bugs Effectively" (https://www.chiark.greenend.org.uk/~sgtatham/bugs.html) carefully. Take some time to work out exact steps to reproduce your problem, make sure that they really do reproduce, and then paste exact and detailed instructions on how to reproduce your problem into a new bug report. Don't assume that someone else's import failure problem is due to the same underlying bug as your import failure problem. Do link to bugs that you think may be related (such as this one). Don't worry about filing duplicates; in this kind of case it takes far more effort to untangle reports that turn out to have different root causes then it does to mark duplicate bugs if this becomes clear to developers later. I hope this helps. I can't guarantee what will come next, but by filing actionable reports at least you'll be one step closer to real progress. ** Changed in: network-manager-openvpn (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/606365 Title: unable to import config with inlined ca, cert, key or tls-auth To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager-openvpn/+bug/606365/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
