Version-Release number of selected component: nm-connection-editor-1.4.0-1.fc25 Additional info: reporter: libreport-2.8.0 backtrace_rating: 4 cmdline: nm-connection-editor --edit a5727146-65f0-47ec-b5d8-be231334d404 crash_function: g_malloc0 executable: /usr/bin/nm-connection-editor global_pid: 8950 kernel: 4.9.5-200.fc25.x86_64 pkg_fingerprint: 4089 D8F2 FDB1 9C98 pkg_vendor: Fedora Project runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #3 g_malloc0 at gmem.c:124 #4 _gtk_css_lookup_new at gtkcsslookup.c:32 #5 gtk_css_static_style_new_compute at gtkcssstaticstyle.c:183 #6 gtk_css_node_create_style at gtkcssnode.c:371 #7 gtk_css_node_real_update_style at gtkcssnode.c:425 #8 gtk_css_node_ensure_style at gtkcssnode.c:1003 #10 gtk_css_node_validate_internal at gtkcssnode.c:1380 #21 gtk_container_idle_sizer at gtkcontainer.c:2053 #26 _gdk_frame_clock_emit_layout at gdkframeclock.c:634 #27 gdk_frame_clock_paint_idle at gdkframeclockidle.c:408
Created attachment 1246440 [details] File: backtrace
Created attachment 1246441 [details] File: cgroup
Created attachment 1246442 [details] File: core_backtrace
Created attachment 1246443 [details] File: dso_list
Created attachment 1246444 [details] File: environ
Created attachment 1246445 [details] File: exploitable
Created attachment 1246446 [details] File: limits
Created attachment 1246447 [details] File: maps
Created attachment 1246448 [details] File: mountinfo
Created attachment 1246449 [details] File: namespaces
Created attachment 1246450 [details] File: open_fds
Created attachment 1246451 [details] File: proc_pid_status
Created attachment 1246452 [details] File: var_log_messages
looks like either a bug in GTK or some memory corruption. Any indication what you did precisely that leads to the crash? It may be especially useful to run nm-c-e with valgrind
This seems very similar to another crash I encountered, reported as 1409934. That report has some valgrind traces and steps to reproduce. *** This bug has been marked as a duplicate of bug 1409934 ***
*** Bug 1458221 has been marked as a duplicate of this bug. ***