Description of problem: happened while browsing recent files while setting up an openvpn vpn in network manager, while looking up for the private key file to be exact. the problem isn't consistant in that I could start the assistant again and create the same vpn with the same steps without experiencing the issue. Version-Release number of selected component: nm-connection-editor-0.9.9.0-7.git20131028.fc20 Additional info: reporter: libreport-2.1.12 backtrace_rating: 4 cmdline: /usr/bin/nm-connection-editor --show --type vpn crash_function: gtk_tree_row_ref_deleted executable: /usr/bin/nm-connection-editor kernel: 3.12.8-300.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 gtk_tree_row_ref_deleted at gtktreemodel.c:2130 #1 gtk_tree_row_reference_deleted at gtktreemodel.c:2509 #2 gtk_tree_view_row_deleted at gtktreeview.c:9048 #7 gtk_tree_model_row_deleted at gtktreemodel.c:1867 #8 emit_row_deleted_for_row at gtkfilesystemmodel.c:331 #9 remove_file at gtkfilesystemmodel.c:1912 #10 gtk_file_system_model_monitor_change at gtkfilesystemmodel.c:1257 #11 ffi_call_unix64 at ../src/x86/unix64.S:76 #12 ffi_call at ../src/x86/ffi64.c:522 #13 g_cclosure_marshal_generic_va at gclosure.c:1550 Potential duplicate: bug 953362
Created attachment 864910 [details] File: backtrace
Created attachment 864911 [details] File: cgroup
Created attachment 864912 [details] File: core_backtrace
Created attachment 864913 [details] File: dso_list
Created attachment 864914 [details] File: environ
Created attachment 864915 [details] File: exploitable
Created attachment 864916 [details] File: limits
Created attachment 864917 [details] File: maps
Created attachment 864918 [details] File: open_fds
Created attachment 864919 [details] File: proc_pid_status
Created attachment 864920 [details] File: var_log_messages
This looks like a GTK3 issue. I've found similar (same) problems with other packages, e.g.: bug 984375 - gedit bug 1059187 - evince bug 1027382 - transmission-gtk bug 979077 - rhythmbox and more Related upstream bug: https://bugzilla.gnome.org/show_bug.cgi?id=699918 Over to gtk3.
I think this was likely fixed