Bug 377029 - Crash in connection editor when importing openvpn connection
Summary: Crash in connection editor when importing openvpn connection
Status: RESOLVED WORKSFORME
Alias: None
Product: plasma-nm
Classification: Plasma
Component: editor (show other bugs)
Version: 5.9.2
Platform: Slackware Linux
: NOR crash
Target Milestone: ---
Assignee: Jan Grulich
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-02-28 16:58 UTC by Eric Hameleers
Modified: 2019-07-10 12:07 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Eric Hameleers 2017-02-28 16:58:38 UTC 
When using the Plasma 5 connection editor to import an existing openvpn connection, I get consistent crash after selecting the .ovpn file and clicking "OK". Even with gdb I do not get a useful backtrace but when using gdb I noticed that the crash occurs when the "copying certificate" window is drawn. I get the window borders but not the window content.

In the same Plasma 5 desktop session I can however start the GTK-based nm-applet and successfully import that same .ovpn definition file. The resulting OpenVPN entry is also visible in the Plasma 5 widget and can successfully be used. 

System: Slackware-current 64bit (post-14.2) with Plasma 5.9.2, KF 5.31.0 and Qt 5.7.1. Using NetworkManager 1.6.0 and NetworkManager-openvpn 1.2.8.
The OpenVPN .ovpn file I tried to import is any one from https://www.privateinternetaccess.com/openvpn/openvpn.zip
Comment 1 Jan Grulich 2017-03-02 08:43:37 UTC 
I cannot reproduce the crash and without a backtrace I won't be able to do anything about it unfortunately.
Comment 2 Jan Grulich 2017-10-02 09:01:25 UTC 
Ping? Can you please provide requested information?
Comment 3 Eric Hameleers 2017-10-02 12:20:22 UTC 
(In reply to Jan Grulich from comment #2)
> Ping? Can you please provide requested information?

IN my original post I already mentioned "Even with gdb I do not get a useful backtrace".
Comment 4 Jan Grulich 2019-07-10 12:07:55 UTC 
I believe this is no longer a problem. Please re-open if you still can reproduce this issue.