Version-Release number of selected component: gconf-editor-3.0.1-5.fc19 Additional info: reporter: libreport-2.1.6 backtrace_rating: 4 cmdline: gconf-editor crash_function: g_assertion_message executable: /usr/bin/gconf-editor kernel: 3.10.7-200.fc19.x86_64 runlevel: N 5 uid: 1000 var_log_messages: Aug 21 11:55:54 localhost abrt[25510]: Saved core dump of pid 25286 (/usr/bin/gconf-editor) to /var/tmp/abrt/ccpp-2013-08-21-11:55:54-25286 (18890752 bytes) Truncated backtrace: Thread no. 1 (10 frames) #2 g_assertion_message at /lib64/libglib-2.0.so.0 #3 g_assertion_message_expr at /lib64/libglib-2.0.so.0 #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 /lib64/libgobject-2.0.so.0 #8 g_signal_emit_valist at /lib64/libgobject-2.0.so.0 #9 g_signal_emit_by_name at /lib64/libgobject-2.0.so.0 #10 gtk_tree_view_row_deleted at gtktreeview.c:9122 #11 g_closure_invoke at /lib64/libgobject-2.0.so.0
Created attachment 788841 [details] File: backtrace
Created attachment 788842 [details] File: cgroup
Created attachment 788843 [details] File: core_backtrace
Created attachment 788844 [details] File: dso_list
Created attachment 788845 [details] File: environ
Created attachment 788846 [details] File: limits
Created attachment 788847 [details] File: maps
Created attachment 788848 [details] File: open_fds
Created attachment 788849 [details] File: proc_pid_status
Same problem. It can be easily reproduced. Start gconf-editor open up the tree, select an item in the right window, then click on a different path in the tree. This was already reported (with a patch which fixes it) on the gnome bugzilla over a year and a half ago: https://bugzilla.gnome.org/show_bug.cgi?id=670586 Any chance of getting Edward Sheldrake's patch included in the Fedora version? The patch works for me.
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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 19 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.
This bug is still not fixed in Fedora 20 or 21. See, for example, bug 1158754.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.