Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Version-Release number of selected component:
GConf2-3.2.6-8.el7
Additional info:
reporter: libreport-2.1.11.1
backtrace_rating: 4
cmdline: gsettings-data-convert
crash_function: g_settings_schema_get_value
executable: /usr/bin/gsettings-data-convert
global_pid: 27047
kernel: 3.10.0-509.el7.x86_64
pkg_fingerprint: 199E 2F91 FD43 1D51
pkg_vendor: Red Hat, Inc.
reproducible: Not sure how to reproduce the problem
runlevel: N 5
type: CCpp
uid: 1000
Truncated backtrace:
Thread no. 1 (5 frames)
#2 g_settings_schema_get_value at gsettingsschema.c:962
#3 g_settings_schema_key_init at gsettingsschema.c:1241
#4 g_settings_set_value at gsettings.c:1571
#5 g_settings_set at gsettings.c:1677
#6 handle_file
This is a bug in Vino. The SIGTRAP happens when gsettings-data-convert tries to convert Vino's GConf2's settings to gsettings. There is gsetings' key 'enabled' listed in its convert file which doesn't exist since this commit:
https://git.gnome.org/browse/vino/commit/?id=18be3c5546172bce551b65d60ec2c931bc451398
Removing the line 'enabled = /desktop/gnome/remote_access/enabled' from 'common/org.gnome.Vino.convert' fixes this problem for me.
Steps to reproduce:
1. remove ~/.local/share/gsettings-data-convert file
2. run gsettings-data-convert
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2017:2005