Version-Release number of selected component: gconf-editor-3.0.1-9.fc23 Additional info: reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: gconf-editor /apps/mail-notification crash_function: gconf_client_lookup executable: /usr/bin/gconf-editor global_pid: 10936 kernel: 4.2.5-300.fc23.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #4 gconf_client_lookup at gconf-client.c:2369 #5 gconf_client_key_is_writable at gconf-client.c:1415 #6 gconf_editor_window_update_list_selection at gconf-editor-window.c:1131 #7 _g_closure_invoke_va at gclosure.c:864 #10 _gtk_tree_selection_internal_select_node at gtktreeselection.c:1593 #11 gtk_tree_view_real_set_cursor at gtktreeview.c:13295 #12 gtk_tree_view_row_deleted at gtktreeview.c:9344 #17 gtk_tree_model_row_deleted at gtktreemodel.c:1899 #18 gtk_tree_model_sort_row_deleted at gtktreemodelsort.c:1083 #23 gtk_tree_model_row_deleted at gtktreemodel.c:1899 Potential duplicate: bug 1207825
Created attachment 1093840 [details] File: backtrace
Created attachment 1093841 [details] File: cgroup
Created attachment 1093842 [details] File: core_backtrace
Created attachment 1093843 [details] File: dso_list
Created attachment 1093844 [details] File: environ
Created attachment 1093845 [details] File: limits
Created attachment 1093846 [details] File: maps
Created attachment 1093847 [details] File: mountinfo
Created attachment 1093848 [details] File: namespaces
Created attachment 1093849 [details] File: open_fds
Created attachment 1093850 [details] File: proc_pid_status
Created attachment 1093851 [details] File: var_log_messages
Another user experienced a similar problem: I was editting a configuration option for Docky and it crashed when changing to another key. reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: gconf-editor crash_function: gconf_client_lookup executable: /usr/bin/gconf-editor global_pid: 3496 kernel: 4.2.8-300.fc23.x86_64 package: gconf-editor-3.0.1-9.fc23 reason: gconf-editor killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
This is an old bug, which, for some inexplicable reason, they won't fix, even though there's been a patch on the gnome bugzilla since April 2012 (https://bugzilla.gnome.org/show_bug.cgi?id=670586)! https://bugzilla.redhat.com/show_bug.cgi?id=999500 Edward Sheldrake's patch from nearly four years ago works for me with the Fedora 23 version.
Similar problem has been detected: just randomly crashed multiple times while interacting with reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: gconf-editor crash_function: gconf_client_lookup executable: /usr/bin/gconf-editor global_pid: 22433 kernel: 4.4.3-300.fc23.x86_64 package: gconf-editor-3.0.1-9.fc23 reason: gconf-editor killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
*** Bug 1338065 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Trying to close the window. reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: gconf-editor crash_function: gconf_client_lookup executable: /usr/bin/gconf-editor global_pid: 2998 kernel: 4.5.5-201.fc23.x86_64 package: gconf-editor-3.0.1-9.fc23 reason: gconf-editor killed by SIGABRT runlevel: N 5 type: CCpp uid: 1810
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '23'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.