Bug 1091145 - NetworkManager hangs when I try reconfigure ovpn connection
Summary: NetworkManager hangs when I try reconfigure ovpn connection
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 22
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Lubomir Rintel
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-04-25 03:23 UTC by Mikhail
Modified: 2017-04-17 11:35 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-07-19 11:24:31 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
backtrace (8.83 KB, text/plain)
2014-04-25 03:23 UTC, Mikhail
no flags Details
yet another backtrace (8.83 KB, text/plain)
2014-04-25 03:27 UTC, Mikhail
no flags Details

Description Mikhail 2014-04-25 03:23:59 UTC
Created attachment 889516 [details]
backtrace

Description of problem:
NetworkManager hangs when I try reconfigure ovpn connection

Demonstration: https://drive.google.com/file/d/0B0nwzlfiB4aQMGFhdnRRZlpWZTQ/edit?usp=sharing

$ rpm -qa | grep NetworkManager
NetworkManager-vpnc-gnome-0.9.8.2-2.fc20.x86_64
NetworkManager-openvpn-gnome-0.9.9.0-0.1.git20140128.fc20.x86_64
NetworkManager-0.9.9.1-4.git20140319.fc20.x86_64
NetworkManager-vpnc-0.9.8.2-2.fc20.x86_64
NetworkManager-pptp-gnome-0.9.8.2-3.fc20.x86_64
NetworkManager-openvpn-0.9.9.0-0.1.git20140128.fc20.x86_64
NetworkManager-pptp-0.9.8.2-3.fc20.x86_64
NetworkManager-openconnect-0.9.8.0-2.fc20.x86_64
NetworkManager-glib-0.9.9.1-4.git20140319.fc20.x86_64
NetworkManager-l2tp-0.9.8.6-1.fc20.x86_64

Comment 1 Mikhail 2014-04-25 03:27:17 UTC
Created attachment 889517 [details]
yet another backtrace

Comment 2 Jirka Klimes 2014-04-29 07:47:41 UTC
It is the gnome-control-center that fails to open VPN configuration.
Are you able to reproduce the problem? (It works fine for me.)

Can you try to open your VPN configuration in nm-connection-editor?
$ rpm -q control-center

Comment 3 Mikhail 2014-05-03 12:10:09 UTC
>Are you able to reproduce the problem?
Yes, for reproduce this switch off LZO comresssion and recreate tunnel.
After it when I try change VPN settings occurs hangs.

$ rpm -q control-center
control-center-3.12.1-1.fc20.x86_64

Comment 4 Jaroslav Reznik 2015-03-03 15:43:55 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22

Comment 5 Jirka Klimes 2015-07-13 16:27:24 UTC
Is this still an issue? If so, can you please run gnome-control-center in a terminal to see possible errors?
Are you able to edit the VPN connection in nm-connection editor?

Comment 6 Marcel Ziswiler 2015-08-18 06:06:57 UTC
I definitely do get the same behaviour with stock F22. Something with NetworkManager and/or OpenVPN got seriously broken lately.

Comment 7 Jirka Klimes 2015-08-18 13:13:05 UTC
(In reply to Marcel Ziswiler from comment #6)
> I definitely do get the same behaviour with stock F22. Something with
> NetworkManager and/or OpenVPN got seriously broken lately.

Can you open a terminal and do
$ gnome-control-center
and reproduce the issue

or even better install gdb and
$ gdb gnome-control-center
(gdb) run
reproduce the issue
and then if it crashed type "bt" in (gdb) prompt

or Ctrl-C when there is a hang, and again type "bt" at (gdb) prompt

Thanks.

Comment 8 Fedora Admin XMLRPC Client 2015-08-18 14:59:41 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 9 Fedora End Of Life 2016-07-19 11:24:31 UTC
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.