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.
Description of problem:
It seems libgio is not correctly loading 'keyfile' module to provide
key-value configuration file support.
Version-Release number of selected component (if applicable):
glib-2.56.1-el7
How reproducible:
Always
Steps to Reproduce:
$ GSETTINGS_BACKEND=keyfile gsettings set org.gnome.desktop.thumbnail-cache maximum-size 10
(process:7779): GLib-GIO-WARNING **: 17:38:31.640: Can't find module 'keyfile' specified in GSETTINGS_BACKEND
GLib-GIO-Message: 17:38:31.640: Using the 'memory' GSettings backend. Your settings will not be saved or shared with other applications.
Actual results:
keyfile module is not found
Expected results:
configuration should be stored on properly format without any issue.
Additional info:
Upstream report for this issue
https://gitlab.gnome.org/GNOME/glib/issues/1822
Comment 7Michael Catanzaro
2020-11-10 20:01:45 UTC
(In reply to Marco Benatto from comment #0)
> Expected results:
> configuration should be stored on properly format without any issue.
>
> Additional info:
> Upstream report for this issue
>
> https://gitlab.gnome.org/GNOME/glib/issues/1822
I looked into this yesterday. Setting the keyfile backend as the default backend is only supposed to work in glib 2.60 and newer. We have glib 2.56 in RHEL 8, so it's not expected to work.
However, we actually do want to support this in RHEL 8.4, because we want to create RHEL flatpak runtimes, and for that we need glib in the runtime to support the keyfile backend. This is only useful in combination with support for the settings portal. I will try to backport all of the above, and we'll see how it goes.
Comment 9Michael Catanzaro
2020-11-10 21:35:15 UTC
(In reply to Marco Benatto from comment #0)
> Steps to Reproduce:
> $ GSETTINGS_BACKEND=keyfile gsettings set org.gnome.desktop.thumbnail-cache
> maximum-size 10
>
> (process:7779): GLib-GIO-WARNING **: 17:38:31.640: Can't find module
> 'keyfile' specified in GSETTINGS_BACKEND
> GLib-GIO-Message: 17:38:31.640: Using the 'memory' GSettings backend. Your
> settings will not be saved or shared with other applications.
Alternative reproducer that doesn't modify any settings, for QA:
$ GSETTINGS_BACKEND=keyfile gsettings get org.gnome.desktop.thumbnail-cache maximum-size
Comment 13Michael Boisvert
2021-01-26 13:12:02 UTC
Testing glib2-2.56.4-9.el8 using the provided reproducers, I can see that the keyfile module is being properly loaded to provide the key-value configuration.
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 (Moderate: GNOME security, bug fix, and enhancement update), 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/RHSA-2021:1586