Description of problem: Whenever I connect to an OpenVPN via the NetworkManager menu the system hangs for the time it takes to establish the bond. This _does not happen_ when manually connecting to the same VPNs using the CLI tool. Version-Release number of selected component (if applicable): Version: 1.0.6 Release: 3.fc23 How reproducible: Always. Steps to Reproduce: 1. Add a VPN connection via NetworkManager's GUI 2. Try connecting it 3. Actual results: Whole system will freeze while the duration the connection is established. Expected results: System continue to operate as usual regardless the connection is made or not - at least that was the behavior in F22. Additional info: As I already noted, this doesn't happens with the openvpn CLI tool. Many thanks!
which UI are us using? Popular are: - Gnome3's gnome-control-center - nm-applet (nm-connection-editor) - KDE's plasma-nm (with kde-nm-connection-editor) What exactly freezes? You mean your Graphical interface/Window-manager? Which one are you using? Thank you.
Ahh damn, I feel so ashamed for this... I just tried to reproduce the issue by first *disabling all extensions* and issue is gone... In case you're interested this what I wrote when I realized I missed following a basic debug rule >< **** Hi Thomas, I'm using GNOME Shell so when I enable my VPNs graphically I do it from the Top Bar menu. By the way, in order to have a clear environment I have disabled all my extensions. What is even weirder is the way the GUI freezes: I just reproduced the bug again and took these additional steps I hope can you help debug what's happening here: 1. I enabled an OpenVPN VPN from the integrated VPN menu in GNOME Shell's Top Bar menu; 2. Then the desktop froze: I could move the mouse pointer through the screen but otherwise the desktop is unresponsive; I can't switch windows, launch the Activities overview be it by pushing the mouse to the hot-corner or pressing the designated hotkey (Left Super), open windows don't respond... it's like if what I see is a still picture of my former screen; 3. I can though switch to a text terminal by Ctrl+Alt+Fx _and_ log in. So, the system is functional indeed and the problem seems related to X, right? 4. Well, switching back to tty1 - where the graphical session is running - I have the lock screen that I can lift as usual to then type my password to sign back into my account...; 5. Once signed back the screen continues to be froze as when I left it until the connection is made; 6. Last, all the keys I pressed when the screen froze launch the actions invoked like in blast: overview is shown, Alt-Tab/Super-Tab switches to the other windows and so on. **** I'm closing this ticket so clearly it is an extension (I yet have to find which one) that is somehow messing things up. Damn.