Version-Release number of selected component: gconf-editor-3.0.1-2.fc17 Additional info: libreport version: 2.0.13 abrt_version: 2.0.12 backtrace_rating: 4 cmdline: gconf-editor crash_function: gconf_client_lookup kernel: 3.5.3-1.fc17.x86_64 truncated backtrace: :Thread no. 1 (10 frames) : #4 gconf_client_lookup at gconf-client.c : #5 gconf_client_key_is_writable at gconf-client.c : #6 gconf_editor_window_update_list_selection at gconf-editor-window.c : #7 _g_closure_invoke_va at gclosure.c : #9 g_signal_emit_by_name at gsignal.c : #10 gtk_tree_view_row_deleted at gtktreeview.c : #15 gtk_tree_model_row_deleted at gtktreemodel.c : #16 gtk_tree_model_sort_row_deleted at gtktreemodelsort.c : #21 gtk_tree_model_row_deleted at gtktreemodel.c : #22 gconf_list_model_set_root_path at gconf-list-model.c
Created attachment 611462 [details] File: core_backtrace
Created attachment 611463 [details] File: environ
Created attachment 611464 [details] File: limits
Created attachment 611465 [details] File: backtrace
Created attachment 611466 [details] File: cgroup
Created attachment 611467 [details] File: maps
Created attachment 611468 [details] File: dso_list
Created attachment 611469 [details] File: var_log_messages
Created attachment 611470 [details] File: open_fds
While wading around looking for the workspace names field, started at the bottom expanding the buttons. When I got to the thrid or so from the bottom, and saw the workspace_names, clicking on that field is when it aborted. backtrace_rating: 4 Package: gconf-editor-3.0.1-2.fc17 OS Release: Fedora release 17 (Beefy Miracle)
I just started using the configuration tool for the first time and as I was setting a parameter, the tool aborted backtrace_rating: 4 Package: gconf-editor-3.0.1-2.fc17 Architecture: i686 OS Release: Fedora release 17 (Beefy Miracle)
browsing the desktop/ subtree. backtrace_rating: 4 Package: gconf-editor-3.0.1-2.fc17 OS Release: Fedora release 17 (Beefy Miracle)
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 WONTFIX if it remains open with a Fedora 'version' of '17'. 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 prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 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 to Fedora 17's end of life. 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.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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. Thank you for reporting this bug and we are sorry it could not be fixed.