Bug 1050175

Summary: [abrt] gnome-shell: g_settings_schema_get_value(): gnome-shell killed by SIGTRAP
Product: [Fedora] Fedora Reporter: Adam Williamson <awilliam>
Component: gnome-shellAssignee: Owen Taylor <otaylor>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: fmuellner, otaylor, samkraju, walters
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/782d2e92650893cfc3793666d41d6ac4540a2535
Whiteboard: abrt_hash:8af41eee285ae3b58639f8e79583202eaad1d75d
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 10:51:42 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

Description Adam Williamson 2014-01-08 19:48:50 UTC 
Description of problem:
Don't recall, cleaning out older abrt reports. May still be valid.

Version-Release number of selected component:
gnome-shell-3.11.2-3.fc21

Additional info:
reporter:       libreport-2.1.10
backtrace_rating: 4
cmdline:        /usr/bin/gnome-shell
crash_function: g_settings_schema_get_value
executable:     /usr/bin/gnome-shell
kernel:         3.13.0-0.rc4.git1.1.fc21.x86_64
runlevel:       N 5
type:           CCpp
uid:            1001

Truncated backtrace:
Thread no. 1 (10 frames)
 #2 g_settings_schema_get_value at gsettingsschema.c:951
 #3 g_settings_schema_key_init at gsettingsschema.c:1148
 #4 g_settings_get_value at gsettings.c:1102
 #5 g_settings_get_strv at gsettings.c:1971
 #6 meta_prefs_add_keybinding at core/prefs.c:2113
 #7 add_keybinding_internal at core/keybindings.c:810
 #8 add_builtin_keybinding at core/keybindings.c:836
 #9 init_builtin_key_bindings at core/keybindings.c:4653
 #10 meta_display_init_keys at core/keybindings.c:4848
 #11 meta_display_open at core/display.c:550

Potential duplicate: bug 907189
Comment 1 Adam Williamson 2014-01-08 19:48:54 UTC 
Created attachment 847324 [details]
File: backtrace
Comment 2 Adam Williamson 2014-01-08 19:48:55 UTC 
Created attachment 847325 [details]
File: cgroup
Comment 3 Adam Williamson 2014-01-08 19:48:57 UTC 
Created attachment 847326 [details]
File: core_backtrace
Comment 4 Adam Williamson 2014-01-08 19:48:58 UTC 
Created attachment 847327 [details]
File: dso_list
Comment 5 Adam Williamson 2014-01-08 19:49:00 UTC 
Created attachment 847328 [details]
File: environ
Comment 6 Adam Williamson 2014-01-08 19:49:01 UTC 
Created attachment 847329 [details]
File: limits
Comment 7 Adam Williamson 2014-01-08 19:49:03 UTC 
Created attachment 847330 [details]
File: maps
Comment 8 Adam Williamson 2014-01-08 19:49:05 UTC 
Created attachment 847331 [details]
File: open_fds
Comment 9 Adam Williamson 2014-01-08 19:49:06 UTC 
Created attachment 847332 [details]
File: proc_pid_status
Comment 10 Adam Williamson 2014-01-08 19:49:08 UTC 
Created attachment 847333 [details]
File: var_log_messages
Comment 11 Jaroslav Reznik 2015-03-03 15:22:43 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
Comment 12 Fedora End Of Life 2016-07-19 10:51:42 UTC 
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.