After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 768986 - nm-connection-editor segmentation fault only when editing a WPA2 Enterprise network
nm-connection-editor segmentation fault only when editing a WPA2 Enterprise n...
Status: RESOLVED FIXED
Product: NetworkManager
Classification: Platform
Component: nm-connection-editor
1.2.x
Other Linux
: Normal normal
: ---
Assigned To: NetworkManager maintainer(s)
NetworkManager maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2016-07-20 09:36 UTC by dabiggmoe
Modified: 2016-07-25 17:53 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
segmentation fault dump (9.81 KB, text/plain)
2016-07-20 09:36 UTC, dabiggmoe
Details

Description dabiggmoe 2016-07-20 09:36:25 UTC
Created attachment 331802 [details]
segmentation fault dump

Hi

I've been trying to connect to my work WPA2 Enterprise wifi and I couldn't because every time I try to edit the connection in nm-connection-editor it crashes while filling the "WiFi-Security" tab fields.

`--> pacman -Q nm-connection-editor   
nm-connection-editor 1.2.2-1

`--> uname -a
Linux homebase 4.6.4-1-ARCH #1 SMP PREEMPT Mon Jul 11 19:12:32 CEST 2016 x86_64 GNU/Linux

While checking the journalctl logs, I found out that nm-connection-editor crashes with a segmentation fault.

Attached you can find the log file.
Comment 1 Beniamino Galvani 2016-07-21 08:58:53 UTC
Do you see any messages if you start nm-connection-editor from a terminal? Are you using EAP-TLS with a valid private key?
Comment 2 dabiggmoe 2016-07-21 09:07:05 UTC
Hi Galvani,


nm-connection-editor crashes as soon as I enter the first character of the private key. Below is the log for nm-connection-editor ran from the terminal and the associated journalctl log


`--> nm-connection-editor 
Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
** Message: Cannot save connection due to error: Editor initializing...

(nm-connection-editor:18792): Gtk-WARNING **: Could not load a pixbuf from icon theme.
This may indicate that pixbuf loaders or the mime database could not be found.
** Message: Cannot save connection due to error: Invalid setting Wi-Fi: 802-11-wireless.ssid: property is missing
** Message: Connection validates and can be saved
** Message: Cannot save connection due to error: Invalid setting Wi-Fi Security: missing EAP-TLS identity

(nm-connection-editor:18792): Gtk-WARNING **: Failed to fetch network locations: Timeout was reached

(nm-connection-editor:18792): Gtk-WARNING **: Failed to fetch network locations: Timeout was reached

(nm-connection-editor:18792): Gtk-WARNING **: Failed to fetch network locations: Timeout was reached

(nm-connection-editor:18792): Gtk-WARNING **: Failed to fetch network locations: Timeout was reached

(nm-connection-editor:18792): Gtk-WARNING **: Failed to fetch network locations: Timeout was reached

(nm-connection-editor:18792): Gtk-WARNING **: Failed to fetch network locations: Timeout was reached
** Message: Cannot save connection due to error: Invalid setting Wi-Fi Security: invalid EAP-PEAP CA certificate: no certificate specified
** Message: Cannot save connection due to error: Invalid setting Wi-Fi Security: missing EAP-TLS identity
** Message: Cannot save connection due to error: Invalid setting Wi-Fi Security: invalid EAP-TLS CA certificate: no certificate specified
** Message: Cannot save connection due to error: Invalid setting Wi-Fi Security: missing EAP-TLS identity
** Message: Cannot save connection due to error: Invalid setting Wi-Fi Security: invalid EAP-TLS CA certificate: no certificate specified
** Message: Cannot save connection due to error: Invalid setting Wi-Fi Security: invalid EAP-TLS password: missing
zsh: segmentation fault (core dumped)  nm-connection-editor



`--> journalctl -xe
-- The start-up result is done.
Jul 21 12:02:28 homebase systemd-coredump[19008]: Process 18792 (nm-connection-e) of user 1000 dumped core.
                                                  
                                                  Stack trace of thread 18792:
                                                  #0  0x0000000000442802 n/a (nm-connection-editor)
                                                  #1  0x0000000000440cc7 eap_method_validate (nm-connection-editor)
                                                  #2  0x000000000043d70f ws_802_1x_validate (nm-connection-editor)
                                                  #3  0x000000000043ce9e wireless_security_validate (nm-connection-editor)
                                                  #4  0x00000000004206d2 n/a (nm-connection-editor)
                                                  #5  0x000000000041aa1a ce_page_validate (nm-connection-editor)
                                                  #6  0x0000000000415b3b n/a (nm-connection-editor)
                                                  #7  0x00007f89a52e81d4 n/a (libgobject-2.0.so.0)
                                                  #8  0x00007f89a530290d g_signal_emit_valist (libgobject-2.0.so.0)
                                                  #9  0x00007f89a5302fff g_signal_emit (libgobject-2.0.so.0)
                                                  #10 0x00007f89a52e7fa5 g_closure_invoke (libgobject-2.0.so.0)
                                                  #11 0x00007f89a52f9fb2 n/a (libgobject-2.0.so.0)
                                                  #12 0x00007f89a5302c1c g_signal_emit_valist (libgobject-2.0.so.0)
                                                  #13 0x00007f89a53034ab g_signal_emit_by_name (libgobject-2.0.so.0)
                                                  #14 0x00007f89a6097e69 n/a (libgtk-3.so.0)
                                                  #15 0x00007f89a609ad25 n/a (libgtk-3.so.0)
                                                  #16 0x00007f89a52e7fa5 g_closure_invoke (libgobject-2.0.so.0)
                                                  #17 0x00007f89a52fa3ad n/a (libgobject-2.0.so.0)
                                                  #18 0x00007f89a5302c1c g_signal_emit_valist (libgobject-2.0.so.0)
                                                  #19 0x00007f89a53034ab g_signal_emit_by_name (libgobject-2.0.so.0)
                                                  #20 0x00007f89a6095855 n/a (libgtk-3.so.0)
                                                  #21 0x00007f89a609e4c4 n/a (libgtk-3.so.0)
                                                  #22 0x00007f89a52eaa14 g_cclosure_marshal_VOID__STRINGv (libgobject-2.0.so.0)
                                                  #23 0x00007f89a52e81d4 n/a (libgobject-2.0.so.0)
                                                  #24 0x00007f89a530290d g_signal_emit_valist (libgobject-2.0.so.0)
                                                  #25 0x00007f89a53034ab g_signal_emit_by_name (libgobject-2.0.so.0)
                                                  #26 0x00007f89a52eaa14 g_cclosure_marshal_VOID__STRINGv (libgobject-2.0.so.0)
                                                  #33 0x00007f89a609a74c n/a (libgtk-3.so.0)
                                                  #34 0x00007f89a6120821 n/a (libgtk-3.so.0)
                                                  #35 0x00007f89a52e8122 n/a (libgobject-2.0.so.0)
                                                  #36 0x00007f89a53023e1 g_signal_emit_valist (libgobject-2.0.so.0)
                                                  #37 0x00007f89a5302fff g_signal_emit (libgobject-2.0.so.0)
                                                  #38 0x00007f89a62627bc n/a (libgtk-3.so.0)
                                                  #39 0x00007f89a628293b gtk_window_propagate_key_event (libgtk-3.so.0)
                                                  #40 0x00007f89a62863ab n/a (libgtk-3.so.0)
                                                  #41 0x00007f89a6120821 n/a (libgtk-3.so.0)
                                                  #42 0x00007f89a52e81d4 n/a (libgobject-2.0.so.0)
                                                  #43 0x00007f89a53023e1 g_signal_emit_valist (libgobject-2.0.so.0)
                                                  #44 0x00007f89a5302fff g_signal_emit (libgobject-2.0.so.0)
                                                  #45 0x00007f89a62627bc n/a (libgtk-3.so.0)
                                                  #46 0x00007f89a611da89 n/a (libgtk-3.so.0)
                                                  #47 0x00007f89a611f8d2 gtk_main_do_event (libgtk-3.so.0)
                                                  #48 0x00007f89a5c56735 n/a (libgdk-3.so.0)
                                                  #49 0x00007f89a5c836a2 n/a (libgdk-3.so.0)
                                                  #50 0x00007f89a5012dd7 g_main_context_dispatch (libglib-2.0.so.0)
                                                  #51 0x00007f89a5013040 n/a (libglib-2.0.so.0)
                                                  #52 0x00007f89a5013362 g_main_loop_run (libglib-2.0.so.0)
                                                  #53 0x00000000004151b8 main (nm-connection-editor)
                                                  #54 0x00007f89a4727741 __libc_start_main (libc.so.6)
                                                  #55 0x0000000000415349 _start (nm-connection-editor)
                                                  
                                                  Stack trace of thread 18794:
                                                  #0  0x00007f89a47e56cd poll (libc.so.6)
                                                  #1  0x00007f89a5012fd6 n/a (libglib-2.0.so.0)
                                                  #2  0x00007f89a5013362 g_main_loop_run (libglib-2.0.so.0)
                                                  #3  0x00007f89a560e726 n/a (libgio-2.0.so.0)
                                                  #4  0x00007f89a50392b5 n/a (libglib-2.0.so.0)
                                                  #5  0x00007f89a4aaf484 start_thread (libpthread.so.0)
                                                  #6  0x00007f89a47ee6dd __clone (libc.so.6)
                                                  
                                                  Stack trace of thread 18793:
                                                  #0  0x00007f89a47e56cd poll (libc.so.6)
                                                  #1  0x00007f89a5012fd6 n/a (libglib-2.0.so.0)
                                                  #2  0x00007f89a50130ec g_main_context_iteration (libglib-2.0.so.0)
                                                  #3  0x00007f89a5013131 n/a (libglib-2.0.so.0)
                                                  #4  0x00007f89a50392b5 n/a (libglib-2.0.so.0)
                                                  #5  0x00007f89a4aaf484 start_thread (libpthread.so.0)
                                                  #6  0x00007f89a47ee6dd __clone (libc.so.6)
-- Subject: Process 18792 (nm-connection-e) dumped core
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: man:core(5)
-- 
-- Process 18792 (nm-connection-e) crashed and dumped core.
-- 
-- This usually indicates a programming error in the crashing program and
-- should be reported to its vendor as a bug.
Comment 3 Beniamino Galvani 2016-07-23 08:45:43 UTC
This should be already fixed in master and nma-1-2 (after 1.2.2) branches:

https://git.gnome.org/browse/network-manager-applet/commit/?h=nma-1-2&id=786b115068db8d2e9fb7188a0260c6b9f15c62d2
Comment 4 dabiggmoe 2016-07-25 17:53:24 UTC
That's great news. Thanks a lot :)