Bug 971622

Summary: [abrt] gconf-editor-3.0.1-3.fc18: g_str_hash: Process /usr/bin/gconf-editor was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Pavel Roskin <plroskin>
Component: gconf-editorAssignee: Ray Strode [halfline] <rstrode>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: rstrode
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:a916fe6c7990f68bef1ac3c11575a55f2869a1f5
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-06-07 13:33:37 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages
none
File: xsession_errors none

Description Pavel Roskin 2013-06-07 00:24:20 UTC 
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
Comment 1 Pavel Roskin 2013-06-07 00:24:23 UTC 
Created attachment 757952 [details]
File: backtrace
Comment 2 Pavel Roskin 2013-06-07 00:24:26 UTC 
Created attachment 757953 [details]
File: cgroup
Comment 3 Pavel Roskin 2013-06-07 00:24:28 UTC 
Created attachment 757954 [details]
File: core_backtrace
Comment 4 Pavel Roskin 2013-06-07 00:24:31 UTC 
Created attachment 757955 [details]
File: dso_list
Comment 5 Pavel Roskin 2013-06-07 00:24:34 UTC 
Created attachment 757956 [details]
File: environ
Comment 6 Pavel Roskin 2013-06-07 00:24:36 UTC 
Created attachment 757957 [details]
File: limits
Comment 7 Pavel Roskin 2013-06-07 00:24:39 UTC 
Created attachment 757958 [details]
File: maps
Comment 8 Pavel Roskin 2013-06-07 00:24:42 UTC 
Created attachment 757959 [details]
File: open_fds
Comment 9 Pavel Roskin 2013-06-07 00:24:44 UTC 
Created attachment 757960 [details]
File: proc_pid_status
Comment 10 Pavel Roskin 2013-06-07 00:24:47 UTC 
Created attachment 757961 [details]
File: var_log_messages
Comment 11 Pavel Roskin 2013-06-07 00:24:50 UTC 
Created attachment 757962 [details]
File: xsession_errors
Comment 12 Pavel Roskin 2013-06-07 13:33:37 UTC 
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 ***