nm-connection-editor goes into infinite loop when trying to change 'Password with Certificates (TLS)' VPN connection

[Paul Koerbitz]

To reproduce:

$ nm-connection-editor

Douple click an existing VPN connection

Authentication Type -> "Password with Certificates"

User Certificate -> click on file chooser -> select a .p12 file

Expected result:

new certificate file is accepted

What happens instead:

nm-connection-manager CPU usage goes to 100% and becomes inresponsive.

This is what I see in the shell:

** (nm-connection-editor:4559): WARNING **: Invalid setting VPN: ca

** (nm-connection-editor:4559): WARNING **: Invalid setting VPN: ca

** (nm-connection-editor:4559): WARNING **: Invalid setting VPN: cert

** (nm-connection-editor:4559): WARNING **: Invalid setting VPN: cert

** (nm-connection-editor:4559): WARNING **: Invalid setting VPN: cert

** (nm-connection-editor:4559): WARNING **: Invalid setting VPN: ca

(nm-connection-editor:4559): Gtk-CRITICAL **: gtk_file_chooser_select_filename: assertion 'filename != NULL' failed
^C
(nm-connection-editor:4559): Gtk-CRITICAL **: gtk_file_chooser_select_filename: assertion 'filename != NULL' failed

This loops over and over suggesting there is some infinite loop.

This is on Ubuntu 13.10, network-manager is version 0.9.8.0-0ubuntu22

[Paul Koerbitz (paul-koerbitz)]

A possible work around is to export an existing VPN setting, to change the filename in the exported config file and then to import it again.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Ronald (ronald-bos-msc)]

Same problem here in 14.04. After selecting the .p12 file, the network manager loops indefinitely. The console shows this:

(nm-connection-editor:8754): Gtk-CRITICAL **: gtk_file_chooser_select_filename: assertion 'filename != NULL' failed

(nm-connection-editor:8754): Gtk-CRITICAL **: gtk_file_chooser_select_filename: assertion 'filename != NULL' failed

** (nm-connection-editor:8754): WARNING **: Invalid setting VPN: remote

** (nm-connection-editor:8754): WARNING **: Invalid setting VPN: remote

** (nm-connection-editor:8754): WARNING **: Invalid setting VPN: remote

** (nm-connection-editor:8754): WARNING **: Invalid setting VPN: remote

** (nm-connection-editor:8754): WARNING **: Invalid setting VPN: remote

** (nm-connection-editor:8754): WARNING **: Invalid setting VPN: remote

(nm-connection-editor:8754): Gtk-CRITICAL **: gtk_file_chooser_select_filename: assertion 'filename != NULL' failed

(nm-connection-editor:8754): Gtk-CRITICAL **: gtk_file_chooser_select_filename: assertion 'filename != NULL' failed

** (nm-connection-editor:8754): WARNING **: Invalid setting VPN: remote

** (nm-connection-editor:8754): WARNING **: Invalid setting VPN: remote

** (nm-connection-editor:8754): WARNING **: Invalid setting VPN: remote

** (nm-connection-editor:8754): WARNING **: Invalid setting VPN: remote

** (nm-connection-editor:8754): WARNING **: Invalid setting VPN: remote

** (nm-connection-editor:8754): WARNING **: Invalid setting VPN: remote

[fralk (fmonte)]

I posted a fix for similar bug #1254220

See post https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1254220/comments/10