Bug 1365663
| Summary: | Openvpn wont connect nm-openvpn[1963]: Bad LZO decompression header byte: 42 | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Randy Barlow <randy> |
| Component: | plasma-nm | Assignee: | Jan Grulich <jgrulich> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 24 | CC: | asn, jgrulich, kde-sig, ncross, rdieter, thaller |
| Target Milestone: | --- | Keywords: | Patch, Triaged |
| Target Release: | --- | Flags: | thaller:
needinfo-
|
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | plasma-nm-5.7.3-2.fc24 plasma-nm-5.7.3-2.fc25 plasma-nm-5.7.3-2.fc23 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-08-13 20:21:35 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1355688 | ||
|
Description
Randy Barlow
2016-08-09 19:19:02 UTC
Looks like the upstream commit landed only in master/ branch (to become 5.8) not 5.7 branch. The fix (may?) involve UI changes, which may explain it. Though, having to wait till Oct 18 for plasma-5.8.0 seems unfortunate too. I'll let Jan decide what's best to do here. It's in master only because the change has UI changes, but it can be simply backported. I'll do that. plasma-nm-5.7.3-2.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2016-9a6a58a5c9 plasma-nm-5.7.3-2.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2016-36b6ce9444 plasma-nm-5.7.3-2.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2016-d538a49f7b plasma-nm-5.7.3-2.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-d538a49f7b plasma-nm-5.7.3-2.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-36b6ce9444 plasma-nm-5.7.3-2.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-9a6a58a5c9 the fix in plasma-nm is not sufficient, because existing connections are still broken. The change in behavior how comp-lzo is interpreted has also issues for a user who downgrades to an older plasma-nm version. I think that should be avoided. Thus I reverted how nm-openvpn treats "comp-lzo=no", see https://bugzilla.gnome.org/show_bug.cgi?id=769177#c7 With this change, the "No" option in plasma-nm's comp-lzo combo-box is broken again. plasma-nm should be fixed to set "no-by-default" instead of "no". (In reply to Thomas Haller from comment #10) @Jan, never mind, I opened upstream KDE bug https://bugs.kde.org/show_bug.cgi?id=366640 with this issue. This follow up issue doesn't have high priority for Fedora as it only results in the "No" option to be treated wrongly. I noted this in Bodhi, but I'll repeat here too: Thomas is correct that existing connections are still broken after upgrading to this patch. However, in my case I was able to edit the connection and uncheck the LZO checkbox, save the connection, and get going again. I decided to give the update positive karma because it did get my VPN working again (without having to downgrade NetworkManager-openvpn!) despite also requiring manual intervention from me. If there is a way to avoid the manual intervention that you can think of, I encourage you to consider that option. I'm happy to keep testing for you, and I'm personally happy that I have a working VPN connection again in the meantime ☺ (In reply to Randy Barlow from comment #12) > If there is a way to avoid the manual intervention that you can think of, I > encourage you to consider that option. I'm happy to keep testing for you, > and I'm personally happy that I have a working VPN connection again in the > meantime ☺ Hi Randy, avoiding manual interaction can only be done in network-manager-openvpn package (not plasma-nm), by treating such connections the way it used to do. That is already done upstream and will be fixed with bug 1355688, which already/soon has updated packages in testing (see there). Best, Thomas plasma-nm-5.7.3-2.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report. plasma-nm-5.7.3-2.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report. plasma-nm-5.7.3-2.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report. |