RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:


Version-Release number of selected component:
gnome-settings-daemon-3.6.3-2.el7

Additional info:
backtrace_rating: 4
cmdline:        /usr/libexec/gnome-settings-daemon
crash_function: g_logv
executable:     /usr/libexec/gnome-settings-daemon
kernel:         3.9.0-0.rc6.51.el7.x86_64
runlevel:       unknown
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #2 g_settings_schema_get_value at /lib64/libgio-2.0.so.0
 #3 g_settings_schema_key_init at /lib64/libgio-2.0.so.0
 #4 g_settings_get_value at /lib64/libgio-2.0.so.0
 #5 g_settings_get_boolean at /lib64/libgio-2.0.so.0
 #6 gnome_bg_load_from_preferences at /lib64/libgnome-desktop-3.so.4
 #7 gsd_background_manager_start at /usr/lib64/gnome-settings-daemon-3.0/libbackground.so
 #8 impl_activate at /usr/lib64/gnome-settings-daemon-3.0/libbackground.so
 #9 gnome_settings_plugin_info_activate
 #10 maybe_activate_plugin
 #11 g_slist_foreach at /lib64/libglib-2.0.so.0

Created attachment 772659 [details]
File: backtrace

Created attachment 772660 [details]
File: cgroup

Created attachment 772661 [details]
File: core_backtrace

Created attachment 772662 [details]
File: dso_list

Created attachment 772663 [details]
File: environ

Created attachment 772664 [details]
File: limits

Created attachment 772665 [details]
File: maps

Created attachment 772666 [details]
File: open_fds

Created attachment 772667 [details]
File: proc_pid_status

Created attachment 772668 [details]
File: var_log_messages

b4ce4e16275347edd3b3b738f5f2f8727fc6e0e4 0xaf69b g_settings_get_boolean /lib64/libgio-2.0.so.0 9a3f88366acb159f486c98c8858b211a1005afdc
8ad9b50c18cba585e1f53a0bc9bcc9ca1bdf2982 0x1394f gnome_bg_load_from_preferences /lib64/libgnome-desktop-3.so.4 f82a48f4a56962b3423a97a3cbe361f46868f600

There's no calls to g_settings_get_boolean in gnome_bg_load_from_preferences in more recent versions of gnome-desktop.

In GNOME 3.6 we did have [1]:
	bg->is_enabled = g_settings_get_boolean (settings, BG_KEY_DRAW_BACKGROUND);
which is likely the cause of the crash.

As this won't happen with the GNOME 3.8 in RHEL7, I'll close this.

[1]: https://git.gnome.org/browse/gnome-desktop/tree/libgnome-desktop/gnome-bg.c?h=gnome-3-6#n340