Bug 693979

Summary: [abrt] glib2-2.28.5-2.fc15: g_settings_schema_new: Process /usr/bin/gsettings was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Peter Hjalmarsson <kanelxake>
Component: glib2Assignee: Matthias Clasen <mclasen>
Status: CLOSED UPSTREAM QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 15CC: clydekunkel7734, mclasen
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:0d36a974cec3c55cf21afbfa291f31469669c072
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-04-14 21:07:43 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: event_log
none
File: maps
none
File: smaps
none
File: dsos
none
File: backtrace none

Description Peter Hjalmarsson 2011-04-06 07:27:14 UTC 
abrt version: 2.0.0
executable: /usr/bin/gsettings
cmdline: gsettings list-recursively org.gnome.desktop.default-applications
component: glib2
crash_function: g_settings_schema_new
kernel: 2.6.38.2-9.fc15.x86_64
reason: Process /usr/bin/gsettings was killed by signal 6 (SIGABRT)
package: glib2-2.28.5-2.fc15
architecture: x86_64
username: xake
uid: 500
rating: 4
time: 1302074719
os_release: Fedora release 15 (Lovelock)

Text file: event_log, 2782 bytes
Text file: maps, 7105 bytes
Text file: smaps, 35133 bytes
Binary file: coredump, 8978432 bytes
Text file: dsos, 4811 bytes
Text file: backtrace, 8335 bytes
Comment 1 Peter Hjalmarsson 2011-04-06 07:27:16 UTC 
Created attachment 490164 [details]
File: event_log
Comment 2 Peter Hjalmarsson 2011-04-06 07:27:18 UTC 
Created attachment 490165 [details]
File: maps
Comment 3 Peter Hjalmarsson 2011-04-06 07:27:20 UTC 
Created attachment 490166 [details]
File: smaps
Comment 4 Peter Hjalmarsson 2011-04-06 07:27:22 UTC 
Created attachment 490167 [details]
File: dsos
Comment 5 Peter Hjalmarsson 2011-04-06 07:27:24 UTC 
Created attachment 490168 [details]
File: backtrace
Comment 6 Matthias Clasen 2011-04-07 03:46:59 UTC 
Upstream bug about issues of this kind: https://bugzilla.gnome.org/show_bug.cgi?id=646039
Comment 7 Clyde E. Kunkel 2011-04-09 18:29:15 UTC 
Package: glib2-2.28.5-2.fc15
Architecture: x86_64
OS Release: Fedora release 16 (Rawhide)


How to reproduce
-----
1. ran a local shell script that displays all gnome schemas and their keys and values
2.
3.


Comment
-----
run the shell script.
$ cat /data/schema-keys.sh
#!/bin/bash
shopt -s -o nounset
# Global Declarations
declare -rx SCRIPT=${0##*/}		# SCRIPT is the name of this script
declare -rx DATA_FILE="temp.txt"	# this is raw data for tune2s
declare -rx KEY_FILE="keys.txt"
declare  DEVS				# this variable is used in tune2fs
declare  KEYS

gsettings list-schemas > $DATA_FILE

if test ! -r "$DATA_FILE" ; then
printf "$SCRIPT: the report file is missing—aborting\n" >&2
exit 192
fi

{ while read DEVS ; do
  printf "%s\n" "$DEVS"
  gsettings list-recursively $DEVS > $KEY_FILE
  { while read KEYS ; do
    printf "%s\n" "     $KEYS"
    done } < $KEY_FILE
done } < $DATA_FILE
exit 0
Comment 8 d. johnson 2011-04-13 19:04:14 UTC 
Package: glib2-2.28.5-2.fc15
Architecture: x86_64
OS Release: Fedora release 15 (Lovelock)


Comment
-----
Use "gsettings list-recursively" to find key names.
Comment 9 Matthias Clasen 2011-04-14 21:07:43 UTC 
This is not going to get fixed in glib 2.28.x, since it has some compatibility concerns. Strictly speaking, it is not gsettings' fault. The installed schemas are inconsistent, since some of them refer to nonexisting child schemas.

Better handling of this situation will have to wait until 2.30 in F16. See the upstream bug for more information.