Description of problem: Run gconf-editor. Select any boolean key with the mouse (/apps/gnome-terminal/global/confirm_window_close was used to generate this report). Select "/" on top on the left pane. gconf-editor crashes immediately. The problem is reproducible every time. One of the following messages is shown on the terminal where gconf-editor was run: (gconf-editor:2146): GConf-CRITICAL **: gconf_client_key_is_writable: assertion `key != NULL' failed or GConf:ERROR:gconf-client.c:2369:gconf_client_lookup: assertion failed: (last_slash != NULL) I'm running LXDE. gconfd-2 is running. gconf-editor shows "This key is not writable" for all keys. However, the checkboxes for boolean options are enabled (perhaps wrongly). Version-Release number of selected component: gconf-editor-3.0.1-3.fc18 Additional info: reporter: libreport-2.1.4 backtrace_rating: 4 cmdline: gconf-editor crash_function: g_str_hash executable: /usr/bin/gconf-editor gconf_subtree: bookmarks = [] kernel: 3.10.0-rc4+ runlevel: N 5 uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 g_str_hash at ghash.c:1730 #1 g_hash_table_lookup_node at ghash.c:401 #2 g_hash_table_lookup at ghash.c:1074 #3 gconf_client_lookup at gconf-client.c:2359 #4 get at gconf-client.c:1474 #5 gconf_client_get_entry at gconf-client.c:1577 #6 gconf_client_get_schema_for_key at gconf-util.c:87 #7 gconf_editor_window_update_list_selection at gconf-editor-window.c:1136 #8 _g_closure_invoke_va at gclosure.c:840 #10 g_signal_emit_by_name at gsignal.c:3393 Potential duplicate: bug 836271
Created attachment 757952 [details] File: backtrace
Created attachment 757953 [details] File: cgroup
Created attachment 757954 [details] File: core_backtrace
Created attachment 757955 [details] File: dso_list
Created attachment 757956 [details] File: environ
Created attachment 757957 [details] File: limits
Created attachment 757958 [details] File: maps
Created attachment 757959 [details] File: open_fds
Created attachment 757960 [details] File: proc_pid_status
Created attachment 757961 [details] File: var_log_messages
Created attachment 757962 [details] File: xsession_errors
This is essentially a duplicate of bug 807618. I just hit a more rare assertion failure: (gconf-editor:2146): GConf-CRITICAL **: gconf_client_key_is_writable: assertion `key != NULL' failed I would more often get GConf:ERROR:gconf-client.c:2369:gconf_client_lookup: assertion failed: (last_slash != NULL) The later is discussed in bug 807618. The way to trigger both assertions is exactly the same. *** This bug has been marked as a duplicate of bug 807618 ***