Bug 356703

Summary: Plasmashell crash when is pressed "connect" on a configured VPN
Product: [Plasma] plasma-nm Reporter: Ezio Vergine <virgolus>
Component: generalAssignee: Lukáš Tinkl <lukas>
Status: RESOLVED DUPLICATE    
Severity: grave CC: diego.ml, jgrulich, rdieter
Priority: NOR    
Version: 5.5.0   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Ezio Vergine 2015-12-14 22:41:50 UTC
Before the upgrade to KDE Frameworks 5.16.0, everything works fine and I've no problem with VPN connection.

After the upgrade, when i click "connect" on a VPN trough the nm-applet, plasma crash and I'm unable to connect to openconnet VPN (that works fine before the upgrade)

Reproducible: Always
Comment 1 Jan Grulich 2015-12-15 07:35:45 UTC
Any backtrace? I cannot reproduce this.
Comment 2 Ezio Vergine 2015-12-16 15:16:18 UTC
Sorry for my response delay.
I've no backtrace at this time, in the weekend I will try install debug symbols for give you a decent backtrace.

With today plasma 5.5.1 upgrade, now I'm able to connect trough openconnect VPN but plasma still crash
Comment 3 Jan Grulich 2015-12-21 07:31:28 UTC
Could be a duplicate of bug 346118.
Comment 4 Diego 2016-03-23 15:45:24 UTC
(In reply to Jan Grulich from comment #1)
> Any backtrace? I cannot reproduce this.

I have quite a similar problem which is always reproducible. The only real difference I have from the original description is that VPN connects successfully after the crash.

So:
- open Plasma Network Manager;
- click "Connect" on a configured VPN connection;
- Plasma crashes;
- VPN connects correctly;
- click "Disconnect" doesn't trigger the crash
- clicking again "Connect" triggers the problem.

Backtrace is here:
https://retrace.fedoraproject.org/faf/reports/1038440/
which is linked to problem:
https://retrace.fedoraproject.org/faf/problems/1857705/
which is linked to several bugs, but the most relevant seems to be:
https://bugzilla.redhat.com/show_bug.cgi?id=1259472
Comment 5 Jan Grulich 2016-03-24 11:49:31 UTC

*** This bug has been marked as a duplicate of bug 346118 ***